[
{
"title":"Testing",
"link":"https://docs.solidgate.com/payments/testing/",
"text":"Simulate payments to test your integration before launching in production.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-customizable.svg"
}
,
{
"title":"Create your payment form",
"link":"https://docs.solidgate.com/payments/integrate/payment-form/create-your-payment-form/",
"text":"Understand how to integrate the payment form into your product.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-payments.svg"
}
,
{
"title":"Subscriptions",
"link":"https://docs.solidgate.com/subscriptions/",
"text":"Create and maintain a stable and healthy business subscription model.",
"imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-global.svg"
}
]
Solidgate provides 3D Secure support for payments, enhancing security measures for both merchants and customers. To process a payment as a
Guide
This process ensures secure, reliable payment processing using 3D Secure authentication to prevent fraud.
3D Secure
payment, pass the force3ds parameter as a boolean
true
value.
When implementing 3D Secure payments, be prepared to display the 3D Secure bank page (ACS URL) to the customer after initiating a recurring request with a verify_url. The request process for recurring 3D Secure transactions is identical to the standard recurring methods, ensuring a seamless integration experience.
Furthermore, to handle 3D Secure transactions, make sure to set up success and fail URLs for browser redirects after a 3D Secure payment, either successful or unsuccessful payment. Provide necessary information for the frictionless flow of 3D Secure 2.0, such as browser details, time zone offset, and user-agent.
3D Secure verification can be triggered either from Solidgate or the processor's side.
To get additional information on the 3D Secure flow, use:
You can retrieve a three_ds object that provides the following details:
eci represents the Electronic Commerce Indicator (
Guide
ECI value represents authentication, affects authorization and liability protection.
ECI
) security level used to authorize the payment.
flow specifies the customer involvement in the 3D Secure flow:
frictionless
- authentication completed without customer input.
challenge
- customer was prompted for additional verification.
none
- authentication was attempted, but the issuer either does not support 3D Secure or did not respond.
unspecified
- unclear if the customer was involved in 3D Secure.
If the flow is null, it indicates that 3D Secure authentication was not initiated for the transaction. The eci value varies depending on the payment network, impacting the authentication, authorization, and liability protection level.