Building payment workflows
Learn how to create SCA-compliant workflows using Drop-in payments or Elements.
Last updated
Learn how to create SCA-compliant workflows using Drop-in payments or Elements.
Last updated
Using Drop-in payments or Elements, you can create Strong Customer Authentication (SCA) compliant workflows for purchase transactions and account management.
Whatever payment solution you use, all SCA requirements are managed by Digital River. Two-factor authentication is handled by our authenticate source method. Our card acquirers use the 3-D Secure protocol to communicate with issuing banks. This protocol operates "behind the scenes" and requires no developer interaction.
The following chart lists key settings and methods for building purchase and account management flows. It's meant to be read from left-to-right and top-to-bottom. For example:
In one-off purchase flows in which customers save a new payment source to their account, you should set the checkout's chargeType to customer_initiated. If you're using Drop-in payments, use the createDropIn() method's configurable options to set flow to checkout and usage to convenience. With DigitalRiver.js with elements, use the createSource() method's configuration object to set futureUse to true and usage to convenience.
When customers are acquiring an auto-renewing subscription, and decide to retrieve a payment source saved to their account, set the checkout's chargeType to customer_initiated and autoRenewal to true. In this flow type, Drop-in payments is not supported. Instead, you'll need to use the authenticateSource() method.
For any workflow that uses Drop-in payments, whether it's intended to handle purchases or account management, you first need to perform the following steps:
If you're using Elements to build purchase workflows, complete the necessary migration to payment sessions. We assume you are familiar with creating and styling elements and capturing payment details.
For almost all one-off, subscription, and mail-order/telephone-order (MOTO) transactions, Digital River supports SCA-compliant workflows using Drop-in payments or Elements.‌
‌One-off workflows allow customers to enter, save, and retrieve their payment information while making one-time purchases.
‌In this one-off flow, customers supply their payment information but don't save it to their account.
Yes
Yes
Yes
Prerequisites: Perform the common Drop-in payments steps.
Step one: Build a checkout with all tax, shipping, duty, and fee amounts in a final state and a chargeType that is customer_initiated.
Step two: Retrieve the checkout's payment session identifier, and use it to set sessionId in the configuration object. In options, set flow to checkout and usage to convenience.
Step three: Pass the configuration object to the create Drop-in method.
Step four: Drop-in payments are rendered in the designated container on your checkout page.
Customers enter their payment information and click the configurable pay now button.
If customers complete any SCA that may be required, onSuccess returns a source.
Step five: Attach the Source to the Checkout.
Step six: Convert the Checkout to an Order.
In this one-off flow, customers enter payment information and save it to their account.
Yes
Yes
Yes
Prerequisites: Perform the common Drop-in payments steps.
Step one: Build a checkout with a registered customer and all tax, shipping, duty and fee amounts in a final state. The chargeType should be customer_initiated.
Step two: Retrieve the checkout's payment session identifier and use it to set sessionId in the Drop-in payments' configuration object. You should also use options to set flow to checkout, usage to convenience, and showSavePaymentAgreement to true.
Step three: Pass the configuration object to the create Drop-in method.
Step four: Drop-in payments are rendered in the designated container on your checkout page.
Customers enter their credit card information, actively accept the save payment agreement and click the configurable pay now button.
Step five: Attach the Source to the Customer.
Step six: Attach the Source to the Checkout.
Step seven: Convert the Checkout to an Order.
In this one-off purchase flow, customers select a payment method they previously saved to their account. The key step is to call the authenticate source method.
Yes
No
Yes
Drop-in payments do not currently support retrieving saved payment methods. To handle this flow, use Elements.
You can create SCA-compliant workflows that allow customers to save or retrieve a recurring payment method during subscription acquisitions and set up workflows for merchant-initiated autorenewals.
SCA is required for subscription acquisitions but not merchant-initiated auto-renewals.
In this flow, customers save payment information to their account and use that payment source to acquire an auto-renewing subscription.
Yes
Yes
Yes
Prerequisites: Perform the common drop-in steps.
Step one: Build a checkout with a registered customer and all tax, shipping, duty and fee amounts in a final state. Set chargeType to customer_initiated and autoRenewal to true.
Step two: Retrieve the checkout's payment session identifier, and use it to set sessionId in the configuration object. In options, set flow to checkout, usage to subscription, and showTermsOfSaleDisclosure to true.
Step three: Pass the configuration object to the create Drop-in method.
Step four: Drop-in payments are rendered in the designated container on your checkout page.
Customers must enter their payment information, actively accept the terms and click the configurable pay now button.
Step five: Attach the Source to the Customer.
Step six: Attach the Source to the Checkout.
Step seven: Convert the Checkout to an Order.
In this flow, customers select a credit card they previously saved to their account and use it to acquire an auto-renewing subscription.
‌The key step is to call the authenticate source method.
Yes
No
Yes
Drop-in payments does not currently support retrieving stored payment methods. To handle this flow, use Elements.
In this workflow, a merchant initiates a subscription's auto-renewal. Although this type of workflow doesn't require SCA, you should ensure you correctly handle auto-renewing subscriptions.
No
N/A
N/A
SCA is not required for transactions where customers provide payment details by mail, fax, or telephone. However, both Drop-in payments and Elements support building workflows for mail order and telephone order (MOTO) transactions.
No
Yes
Yes
Prerequisites: Perform the common Drop-in payments steps.
Step one: Build a checkout with a chargeType of moto and all tax, shipping, duty and fee amounts in a final state. This configures Drop-in payments to display only payment methods supported in MOTO transactions.
Step two: Retrieve the checkout's payment session identifier, and use it to set sessionId in the Drop-in payments' configuration object. In options, set flow to checkout and usage to convenience.
Step three: Pass the configuration object to the create Drop-in method.
Step four: Drop-in payments are rendered in the designated container on your checkout page.
Step five: Attach the Source to the Checkout.
Step six: Convert the Checkout to an Order.
You can create flows that allow customers to manage recurring payment methods through their account portal.
In these account management flows, you only need to adhere to SCA regulations when saving a customer's credit card for future use. While storing a card, attempt to identify the intended use of the source. This increases the probability that future transactions will be approved.
You're not required to do SCA when updating a credit card's expiration date or billing address.
Customers use their account portal to save payment information for future transactions in this flow.
Yes
Yes
Yes
Prerequisites: Perform the common drop-in steps.
Step one: On the page where customers manage their payment methods, use the configuration object's options to set flow to managePaymentMethods and specify a value for usage that identifies the likely future use of the payment.
If customers are replacing an active subscription's recurring billing instrument, make sure you set usage to subscription and showTermsofSaleDisclosure to true. This prompts Drop-in payments to display a recurring billing agreement and forces customers to accept it.
Because this is a managePaymentMethods flow, and there's no payment session to reference, you shouldn't provide a sessionId. As a result, you'll need to pass the billing information you collect from customers in billingAddress.\
Step three: Pass the configuration object to the create Drop-in method.
Step four: Drop-in payments are rendered in the designated container on your checkout page.
Customers enter their payment information, select the save payment agreement option and click the configurable add payment method button.
If customers complete any SCA that may be required, onSuccess returns a source that is readyForStorage.
Step five: Attach the Source to the Customer.
In this flow, customers use their account portal to update their saved credit card's expiration date or billing address.
No
No
Yes
Drop-in payments do not support interacting directly with saved payment methods‌
If customers complete any SCA that may be required, onSuccess returns a that is readyForStorage.
If customers complete any SCA that may be required, onSuccess returns a that is readyForStorage.
The merchant's representative enters the customer's credit card information and clicks the configurable pay now button. If the payment is authorized, then onSuccess returns a unique in a chargeable state.
