Create 3DS Authentication
POST/v1/payin/three-ds/authentications
<b>Tag</b>: api-payments-gateway-post-payin
<b>3DS Authentication Flow:</b>
1. <b>Initial Request:</b> Send card and transaction details to this endpoint.
2. <b>Status Response:</b> You'll receive one of these authentication status:
- PENDING: Authentication is being processed.
- WAITING_AUTHENTICATION: Internal processing, no user action needed.
- WAITING_CHALLENGE: User needs to complete additional authentication.
- ACCEPTED: Authentication successful.
- REJECTED: Authentication rejected.
- FAILED: Process error.
<b>Authentication Scenarios:</b>
- <b>Frictionless:</b> When status is ACCEPTED, don't require further user action. Proceed with payment (POST: v1/payments).
- <b>Challenge:</b> When status is WAITING_CHALLENGE, redirect user to the provided challenge URL for additional verification.
- You need to send a POST request with the Challenge URL, Authentication ID, and iframe data. The response will return the HTML content that should be rendered inside an iframe.
Request
Header Parameters
Sender Wallet UUID (if empty, your default Wallet UUID will be settled)
The transaction ID is a UUID (v7) used to uniquely identify the object that will be created. All objects must have an identifier.
The nonce ID is a UUID (v4) used to uniquely identify the request. All requests must have an identifier.
Possible values: [pt-BR, en-US]
Indicates the preferred language. Defaults to Brazilian Portuguese if unspecified.
The product ID is a UUID (v4) used to identify the Z.ro product configuration.
The product target user ID is a UUID (v4) used to identify what user account this request must be executed. Require: x-product-uuid.
- application/json
Body
required
Country code for the payment.
Possible values: [DEBIT_CARD]
Payment method used in the transaction.
Payment amount in cents. Min value is 1000 cents.
Possible values: [BRL, USD]
Payment currency tag.
Third Part name. It must contain at least first name and last name.
Third Part email address.
Third Part phone number.
User Address Zip Code.
User Address Street.
User Address number.
User Address City.
User Address Federative Unit.
User Address Country.
User Address Neighborhood.
User Address Complement.
Browser language.
Java enabled status.
Color depth in bits.
Screen height in pixels.
Screen width in pixels.
Time difference in minutes.
User agent string.
HTTP Accept content.
Merchant URL.
Possible values: [SMALL, MEDIUM, LARGE, XLARGE, FULL_PAGE]
Merchant Challenge Window Size.
Possible values: [ECOMMERCE, MOBILE, TABLET]
Merchant Transaction Mode.
Possible values: [SDK, BROWSER]
Device channel.
payment_card objectrequired
Card number.
Card CVV.
Card Holder Name.
Card Expiry Date in MM-YYYY format.
Responses
- 200
- 400
- 401
- 422
3DS Authentication created successfully.
- application/json
- Schema
- Example (from schema)
Schema
Three DS authentication ID.
Possible values: [PENDING, WAITING_AUTHENTICATION, WAITING_CHALLENGE, ACCEPTED, REJECTED, FAILED, ERROR]
Three DS authentication status.
Three DS authentication creation date.
Three DS authentication last update date.
{
"id": "0197b169-da6b-7ba2-b053-ce413ae39afd",
"status": "FAILED",
"created_at": "2025-10-22T15:30:01.717Z",
"updated_at": "2025-10-22T15:30:01.717Z"
}
If any required params are missing or has invalid format or type.
User authentication failed.
If any required params are missing or has invalid format or type.