Simulate an APPROVED transaction
- In the request, do not include a
transaction_idvalue. The endpoint will create a newAPPROVEDtransaction and return the correspondingtransaction_idandevent_id
Simulate a VOIDED transaction
-
You can void an
APPROVEDtransaction - The example voids an approved authorization.
Simulate an UPDATED transaction
-
The request must include an existing
transaction_idthat will be updated -
Below, the example updates an
APPROVEDtransaction amount from $50.00 to $35.46
Simulate a CAPTURED transaction
-
In the request, you can create one or multiple captures against the same
transaction_idinAPPROVEDorUPDATEDstatus. - The example creates a $4 capture linked to a previous $4 approved authorization.
-
Alternatively, you can create a standalone capture (e.g., “force capture”) by omitting
transaction_idfrom the request. - The example creates a standalone $4 capture.
Simulate a REFUNDED transaction
-
In the request, you can create one or multiple refunds against the same transaction in
CAPTUREDstatus. You will need to provide theevent_idof the related capture. The API will return an error if the refunded amount exceeds the captured amount for the transaction. - The example creates a $4 refund linked to a previous $4 capture.
-
Alternatively, you can create a standalone refund (e.g., “blind return”) by omitting
transaction_idfrom the request. - The example creates a standalone $5 refund.