Send a receipt
Emails a receipt for a past transaction. No active terminal session or online terminal is required: the receipt is generated from stored transaction data, so its content matches a receipt emailed at charge time.
This endpoint is under /api/v1/, not /api/terminal/.
Authentication
AuthorizationBearer
Use a Payments API key as the bearer token: Authorization: Bearer <api_key>.
Get a fresh key from Refresh API Keys.
Request
This endpoint expects an object.
email
Recipient email address. Always required; there's no fallback to an email on file.
mid
Merchant ID. Resolves and authorizes the acting account.
trans_id
Transaction to generate the receipt for. Lookup by order_id isn't supported.
custom_message
Message to include in the receipt email.
Response
Receipt sent
success
message
Errors
400
Bad Request Error
401
Unauthorized Error
422
Unprocessable Entity Error
429
Too Many Requests Error
500
Internal Server Error