Backoffice Operations
Last updated
Last updated
You can perform different types of backoffice operations using our Server-to-Server REST API.
Note: Backoffice operations can be performed against initial payments that were generated using COPYandPAY or Server-to-Server. The referencedPaymentId
is the value return in the id
JSON field.
A capture is used to request clearing for previously authorized funds. A capture request is performed against a previous preauthorization (PA) payment by referencing its payment.id and sending a POST request over HTTPS to the /v1/payments/{id} endpoint. Captures can be for full or partial amounts. Note that a capture is a one-time event. Once a capture (even partial) has been performed, the preauthorization is not valid anymore for future captures.
A refund is performed against a previous payment, referencing its payment.id
by sending a POST request over HTTPS to the /v1/payments/{id} endpoint. A refund can be performed against debit (DB) or captured preauthorization (PA->CP) payment types. Where supported, the amount field can be used to process a partial or full amount.
Allowed Refund timelines
Country
Refund timeline (days after purchase)
Argentina
90 days.
Brazil
90 days.
Chile
11 months.
Colombia
120 days.
México
90 days.
Perú
6 months.
A reversal is performed against a previous payment, referencing its payment.id
by sending a POST request over HTTPS to the /v1/payments/{id} endpoint. A reversal can be sent against debit (DB) or preauthorization (PA) payment types. When reversing a card payment and if sent within 72 hours of the original request, a reversal causes an authorization reversal request to be sent the card issuer to clear the funds held against the authorization.