What 3-D Secure data does Cashflows need from my business?

Who is this article for?

This information is intended for merchants and developers who use their own 3-D Secure solution and send authentication data to Cashflows through an API.

What data may be required?

Depending on your 3-D Secure version and integration, the payment request may need to include:

• The 3-D Secure transaction identifier, such as the DS Transaction ID or another version-specific transaction ID.
• The authentication value returned after the cardholder authentication process, such as CAVV or an equivalent scheme value.
• The Electronic Commerce Indicator (ECI).
• The 3-D Secure protocol version used for the authentication.
• Any other fields required by the Cashflows API or the relevant card scheme.
• What 3-D Secure data do I need to include in payment requests?
• Payments API integration guide.
• Remote authentication integration guide.
• Remote API integration guide.

How do I obtain the data?

Your 3-D Secure provider or EMV 3-D Secure server performs the authentication and returns the data required for the payment request. Your developer must map that data to the correct Cashflows API fields.

Information for your developer

Share the relevant integration guidance with your developer:

Need help?

For implementation support, contact the Cashflows Implementations team implementations@cashflows.com