Credit card onboarding
Last updated
Was this helpful?
Last updated
Was this helpful?
Your API requests are authenticated using an access token. Any request that does not include a valid access token will return an error.
You can learn more about how to generate an access token here.
If the validations determine that biometric capture is not necessary, the response will have a different status, and no capture link will be generated, as shown below:
To view all possible statuses, refer to the Enumerated section.
To optimize your application's performance, you can also implement our Webhook to know when to check the transaction status.
Didn't find something or still need help? If you're already a client or partner, you can reach out through our Help Center.
Endpoint to validate a credit card.
/wallet/transactions/pre-approved
A valid access token. The value must be sent in the format Bearer {token}.
Order number associated with the transaction. It will be used as an index in the portal and as a foreign key between your system and Unico IDPay.
123456
Company ID responsible for the transaction. This field is provided by Unico.
7873959b-f7b2-4b81-8b0e-4ce178e64daf
URL to redirect the user after completing the transaction. Possible values include an HTTPS URL for web pages or a URL Schema for native mobile app redirection.
https://example.com/redirect
Phone number for notifications (optional). If provided, it will be used for WhatsApp notifications.
+5511999999999
Email address for notifications (optional). If provided, it will be used for email notifications.
user@example.com
User identification details.
Card details used in the transaction.
Endpoint to check the current status of a specific transaction.
/wallet/transactions/{transaction_id}
ID of the transaction to be queried.
6ab1771e-dfab-4e47-8316-2452268e5481
A valid access token. The value must be sent in the format Bearer {token}.