A valid request URL is required to generate request examplesPrint a refund receipt on a Terminal
Prints a receipt for one succeeded card-present Refund on a Terminal
assigned to your account. Sales, PIN-debit returns, and voids that run on
the Terminal print there automatically. Other card-present Refunds and
Voids run without the card: when automatic refund receipts are on for
your account, one that included terminal_id prints automatically on that
Terminal, and any other prints when you call this route. A request for a
refund that already printed prints another copy.
The receipt can go to any ready Terminal in the same account and mode,
not only the one that took the sale. A Terminal runs one command at a
time: a busy Terminal returns TERMINAL_BUSY and prints nothing.
HTTP 200 reports the outcome in status: printed when the Terminal
confirmed the print, failed when it did not. Retry a failed print
with a new Idempotency-Key; reusing a key returns the first result.
A valid request URL is required to generate request examplesAuthorizations
Merchant secret key, or a Platform secret key with delegation.
Headers
Merchant ID when an authorized Platform acts for a connected Merchant. Omit when authenticating directly as that Merchant.
^mer_Unique checkout-attempt key. Reuse the same value only when retrying the same request body and route.
1 - 255Path Parameters
Terminal to print on.
^tmr_Body
A succeeded Refund of a payment taken on a Terminal.
^rf_"rf_01JEXAMPLE4R7T2W9K3M8P5Q"
Response
The print ran; status reports whether the Terminal confirmed it.
terminal_print Terminal the receipt was sent to.
Refund the receipt is for.
printed when the Terminal confirmed the print, failed when it did not.
printed, failed