Get Authorization

Determine if a card order requires two-factor authentication

The need for confirmation codes may differ with each order. You will need to confirm only codes that are requested. If the Authentication codes are not provided within the expiration time, the order will expire - the current expiration time is 10 minutes. When building your UI, you need to make it a real-time experience.

This request is only available until codes are still valid. After that, if you try to get authorization information in this endpoint we throw an error, check Card Exceptions. The current limit of attempts to specify the code is 5 times. After this, you will receive back an error and the order will expire.

If smsNeeded or card2faNeeded are true, you must provide the codes back in the Submit Authorization endpoint.

When 3DS is requested, CARD2FA and SMS will never be requested.

📘

Using 3D Secure

When 3DS is requested, CARD2FA and SMS will never be requested.

When the Get Authorization Details call above returns authorization3dsUrl with a valid URL, you should open a Web-View from the exact same device that sent the Wallet Order creation request, and let the user solve the 3DS challenge. Do not change the Web-View size or inject any kind of script or the 3DS challenge and order will immediately fail. The device IP address where the challenge is solved must be the same as the parameter ipAddress in the wallet order creation.

To receive the 3DS authentication keep polling Get Wallet Order until the status is PROCESSING or FAILED. Do not close the Web-View before the Wallet Order status is PROCESSING or FAILED.

🚧

Testing Note

In testwyre, you need to provide card2fa only once every 2 minutes since you submitted your last order using the same card and same billing. After 2 minutes you will need to provide the card2fa again.

Language
Authentication
Bearer
URL
Click Try It! to start a request and see the response here!