Charge a card
Reads the card, optionally captures a signature, charges the card, and optionally prints and emails a receipt, all in one call.
Returns an interaction_id immediately. Get the result with Get charge status or over WebSocket.
Requesting a step the terminal can’t perform (for example, print_receipt on an Ingenico device) never fails the transaction.
The charge completes and the skipped step is listed in stage_errors on the status response.
charge-card interactions can’t be cancelled through the API.
Authentication
Use a Payments API key as the bearer token: Authorization: Bearer <api_key>.
Get a fresh key from Refresh API Keys.
Path parameters
Hardware Serial Number (HSN) of the terminal, provided by your Integration Delivery lead.
Query parameters
Merchant ID. Required when your bearer token is an ISV token acting on behalf of a merchant. If the mid can't be resolved to an authorized account, the request returns 400.
Request
Capture a signature during the read stage. Checked against capabilities.signature before the read starts.
Signature image size as "width,height". Each value is up to three digits (max 999).
Email a receipt after the charge. Independent of print_receipt.
Recipient email address when send_receipt is true.
Order ID for the transaction. If omitted, one is generated in the format <4-digit random><yymmddHHMMSS>.
Response
Interaction accepted. Use the interaction_id to poll for status or subscribe over WebSocket.