Resume charge after managed 3DS authentication
Called by the 3DS micro-frontend (or your own integration) after the buyer completes the managed 3DS authentication. Processes the charge using the provided 3DS result and fires postback/webhook events.
The charge must be in authentication_required status.
Authentication: Uses the merchant’s public/publishable key (pk_...).
Authorizations
HTTP Basic authentication. Use your secret key as the username and an empty string as password. The API key should be base64 encoded in the format 'username:' when sending the Authorization header.
Path Parameters
Charge ID
"2vorkDcXyvzifL63YX09S9VqcnI"
Body
3D Secure authentication data for BYO-3DS (Bring Your Own) flow. Obtain this object from the FastPay Security SDK or from POST /v1/three-ds/challenge-result after the challenge completes.
Response
Charge resumed and processed
The unique identifier of the created charge
"2vorkDcXyvzifL63YX09S9VqcnI"
The status of the charge
paid, pending, refused, failed "pending"
Additional payment details specific to the payment method
- Credit Card
- Rapipago
- Khipu
- Pix
- QRCode
The reason for charge status (especially for refused charges)
"Insufficient funds"