3D Secure Information

Refer to this page if you are enrolled in 3D Secure as a merchant

In order to process a transaction using 3D Secure, you must follow the following protocol as outlined on this page.

POST Request to {Endpoint}/pay/submit3DTransaction

Step 1: Configure Webhooks

Using 3D Secure requires that you are set up to receive webhook notifications. This is because requests to authorize a transaction will return a PENDING state - the initial request will not have information on whether the transaction was approved or refused.

Webhooks must be enabled because when using 3D Secure, any valid Authorize Transaction request is returned with the PENDING state, and the response body will include a paymentUrl field. See the following example:

{
    "success": true,
    "data": {
        "paymentStatus": "PENDING",
        "nftStatus": "PENDING",
        "txID": 221740,
        "orderTotal": 11.5,
        "paymentUrl": "https://aquilapayments.net/wpayment/process/e0db5e61-f04f-4c76-af06-8fd85688dca2",
        "mintHash": "",
        "mintDate": ""
    }
}

Step 2: Configuring Requests

When interacting with this API, requests only require one additional field in the Authorize Transaction request to utilize 3D Secure. Request to get a quote are identical to standard protocol and do not require modification.

As outlined on the Authorize Transaction page, 3D Secure requests must include the 3D object field with the redirectURL field nested inside. See below:

...
        "redirecturl": "https://merchantpage.com/redirect"
...

Important things to note:

Any 3D transaction will not be submitted until the 3DSecureURL a webpage is opened on the client's device.

See the successful response in Receiving and Acknowledging webhooks.