Adyen defaults to immediately capturing an authorize request, but this is customizeable to delayed or manual capture in your Adyen Merchant Account. Change your capture setting to manual if you intend to use authorize separately from captures.

If using Manual or Dynamic 3D Secure, your capture setting must be manual in order to use authorize or purchase requests. If you prefer to use immediate or delayed auto-capture, making an authorize request will complete in a capture.

For most gateways, a successful response from a capture or credit (refund) request indicates that the request to perform these actions has successfully been received by the gateway, not that the transaction has been successfully processed. At the card network level, these actions are queued up and performed in batches at certain intervals. If you would like to receive confirmation that the action has been successfully performed through the card network, you may set up notifications from Adyen by following the directions in the Adyen Customer Area.

* Be sure to set the attempt_3dsecure flag to true in the transaction request if you are using Adyen for gateway specific 3DS authentication. If you forget to include this field on your request, you may see the following error message: 'Received unexpected 3DS authentication response, but a 3DS initiation flag was not included in the request.'

Please reach out to Adyen Support (support@adyen.com) to have them enable the API PCI Payments Role for you. This is a requirement that must be completed before you can start testing payments with Adyen.

Spreedly recommends generating and using a US specific live URL prefix to point traffic to a US datacenter in order to reduce latency with the Adyen gateway. See Specifying a merchant subdomain below.

Adyen requires country to be provided as a request parameter. If no country is stored with the payment method token or included in the transaction billing_address, Spreedly will supply ZZ as the country code for the transaction, per Adyen’s specifications.

‍