Card charge status and refunds

Use these endpoints to follow a card charge after it has been created through the AgentSnap card API. Keep the charge id returned by creation; all reads and refunds are scoped to the account owning your API key.

1. Retrieve the charge for its current status, original receipt, and refund history.
2. Subscribe to webhooks with event IDs 7 and 8 to receive charge and refund status changes.
3. Refund the charge in full or in part. A refund request being accepted does not mean it has completed.

📘

Authentication and availability

Send your API key as the Authorization header value, following Starting with the AgentSnap API. Keep this key on your server. Use the API host for the environment your key belongs to; do not mix test, staging, and production credentials. Card events must be available in that environment's GET /api/v1/webhooks/events response before you subscribe.

Card refunds return funds to the original card. They are different from policyholder refunds, which send a separate payment that the recipient can cash out.

The examples use a $1 charge without a surcharge. A nonzero surcharge requires separate account enablement; these examples do not imply that surcharging is enabled for your account.