Skip to navigation
GuidesPaymentsCard Present

Signatures & Receipts

Capture cardholder signatures and deliver printed or emailed receipts.

Signature capture

Set include_signature: true on read-card or charge-card to capture the cardholder’s signature during the same customer interaction as the card read — no separate call. Optional formatting fields:

FieldValues
signature_formatBMP, JPEG, or PNG
signature_image_typebinary or rgb
signature_dimensionsTwo numbers, each up to 3 digits (max 999), formatted as "width,height" (e.g. "100,50")
signature_gziptrue or false

When supported, the image is returned as result.signature. When the device doesn’t support signatures, the interaction still succeeds and tokenization is unaffected, but the signal differs by endpoint:

EndpointUnsupported-signature signal
read-cardresult.error: "signature not supported"
charge-cardresult.signature: null and result.stage_errors.signature: "not supported"

Receipts

Print — POST /api/terminal/{device_id}/print-receiptEmail — POST /api/v1/send_receipt
Inline with chargeprint_receipt: truesend_receipt: true and email
Needs the device onlineYes (auto-connects a session)No — generated from stored transaction data
Required fieldstrans_idemail, mid, trans_id
Optional fieldsdelay, extra_receiptcustom_message
Device supportOnly where capabilities.printer is trueAll
Response200200 { "success": true, "message": "Receipt sent successfully" }
  • Reprints are limited to the latest transaction in an order. print-receipt looks up the transaction by your merchant + trans_id; it must be the most recent transaction within its order.
  • Only Clover Flex and Clover Mini can print. All other devices, including every Ingenico model, return 400 Not supported on print-receipt. Hide reprint options when capabilities.printer is false.
  • send_receipt has no fallback email — email is always required. Emailed receipts are identical whether sent at charge time or afterward.

See Print receipt error messages for the errors you can match on.