How to ensure SCA compliance
Determine your approach to implementing SCA.
For your integration to access our Strong Customer Authentication (SCA) solution, you must be using payment sessions. These are embedded in both Drop-in and DigitalRiver.js with Elements.
Use the following flowchart to find your appropriate SCA integration scenario:
.png?alt=media&token=20fb3db1-f186-4a12-a3ca-052276f6fb56)
Integration scenario | Next steps |
|---|---|
I'm using Drop-in Payments | You're already using our recommended, out of the box solution for complying with SCA.
To make sure you're using the tool correctly, review the Drop-in Payments documentation, and then build your workflow. |
I'm using payment sessions with elements | You're currently using DigitalRiver.js in a way that gives you access to SCA flow handling. Your next steps involve building your SCA workflow. |
I need to migrate to payment sessions | In order to access SCA handling and compliance, you'll need to be using payment sessions.
Drop-in Payments are is the preferred method for performing this migration, but you can also migrate directly to payment sessions using DigitalRiver.js. Once you're done with the migration, you'll need to build your SCA workflow. |
Last modified 3mo ago