LogoLogo
System Status
  • Digital River API
  • Getting started
  • Using our services
    • Local pricing
    • Item classification
    • Subscriptions
    • e-Invoicing
  • Integration options
    • Low-code checkouts
      • Implementing a Prebuilt Checkout
      • Implementing a Components checkout
      • Offering local pricing
      • Using a shipping endpoint
      • Processing subscription acquisitions
      • Adding custom fields
      • Offering store credit
      • Displaying policies and getting consent
      • Collecting e-invoice information
      • Handling completed checkout-sessions
    • Direct integrations
      • Standard flow
      • Building checkouts
        • Checking out guest and registered customers
        • Describing line items
          • Setting the price of an item
          • Managing items with shared SKU identifiers
        • Providing address information
        • Handling shipping choice
        • Tax identifiers
        • Applying a discount
        • Setting the customer type
        • Providing the IP address
        • Selecting a currency
        • Initiating a charge
        • Setting the purchase location
        • Configuring taxes
        • Accessing regulatory fee information
        • Localizing invoices and credit memos
        • Providing an upstream identifier
        • Applying store credit
        • Handling e-invoicing requirements
        • Landed cost
        • Tax calculation inputs
        • Selling entities
        • Payment sessions
        • Applying store credit (legacy)
        • Country specs
      • Building payment workflows
        • Handling redirect payment methods
        • Handling delayed payment methods
      • Subscription acquisitions
        • Handling subscription acquisitions
        • Handling external subscription acquisitions
        • Subscription information
      • Digital River coordinated fulfillments
        • Checking inventory levels
        • Using shipping quotes
        • Reserving inventory items
        • Managing a fulfillment order
        • Cancelling a fulfillment order
    • Connectors
  • Order management
    • Processing orders
    • Handling a rejected order
    • Accessing invoices and credit memos
    • Fulfilling goods and services
    • Capturing and cancelling charges
    • Payment reauthorizations
    • Handling reversals
      • Return basics
        • Digital River coordinated returns
        • Third party coordinated returns
      • Refund basics
        • Issuing refunds
        • Refunding asynchronous payment methods
      • Disputes and chargebacks
    • Customer notifications
    • Responding to events
      • Events
        • Key event types
        • All event types
      • Webhooks
        • Creating a webhook
        • Digital River API safelist
        • Digital River signature
      • Expanding events
      • Preventing webhooks from getting disabled
    • Distributor model
  • Subscription Management
    • Managing a subscription
    • Managing an external subscription
  • Payments
    • Payment solutions
      • Drop-in payments
        • How Drop-in payments work
        • Drop-in payments integration guide
      • DigitalRiver.js with Elements
        • Elements integration guide
        • Configuring payment methods
          • Configuring Afterpay
          • Configuring Alipay+ (cross-border)
          • Configuring Alipay (domestic)
          • Configuring Amazon Pay
          • Configuring Apple Pay
          • Configuring Bancontact
          • Configuring BNP Paribas
          • Configuring BLIK
          • Configuring CCAvenue
          • Configuring Clearpay
          • Configuring Credit Cards
          • Configuring FPX Online Banking
          • Configuring Google Pay
          • Configuring iDEAL
          • Configuring Klarna
          • Configuring Konbini
          • Configuring Online Banking (IBP)
          • Configuring Online Banking (Korea Bank Transfer)
          • Configuring PayCo
          • Configuring PayPal
          • Configuring SEPA Direct Debit
          • Configuring Trustly
          • Configuring Wire Transfer
          • Common payment sources
          • Common payment objects
    • Supported payment methods
      • Afterpay
      • Alipay (domestic)
      • Alipay+ (cross-border)
      • Amazon Pay
      • Apple Pay
      • Bancontact
      • BNP Paribas
      • BLIK
      • CCAvenue
      • Clearpay
      • Credit Cards
      • FPX Online Banking
      • Google Pay
      • iDEAL
      • Klarna
      • Konbini
      • Korea Bank Transfer (Online Banking)
      • Online Banking (IBP)
      • Pay with Installments France
      • PayCo
      • PayPal
      • PayPal Billing Agreement
      • PayPal Credit
      • PayPal Pay in 3
      • PayPal Pay in 4
      • PayPal RatenZahlung (Installment Payment)
      • SEPA Direct Debit
      • Trustly
      • Wire Transfer
    • Source basics
      • Managing sources
      • Handling credit card sources
      • Retrieving sources
    • Authorization declines
    • PSD2 and SCA
      • How to ensure SCA compliance
    • Payment testing scenarios
  • Product management
    • Product basics
    • Managing SKUs
    • Using product details
    • Grouping SKUs
    • SKU-inventory item pairs
    • Managing inventory items
    • Regulatory fees
      • What are regulatory fees?
        • Fees terminology
        • Regulatory fee management
        • European regulatory fees
        • Compliance obligations
        • WEEE directive requirements
        • Copyright directive requirements
        • Compliance challenges
      • Managing regulatory fees
  • Customer management
    • Customer basics
    • Creating and updating customers
    • Setting up tax exemptions
    • Recording a customer's request to be forgotten
  • Financial reporting
    • Financials basics
    • Sales transactions
      • Returning a list of sales transactions
      • Getting a sales transaction by ID
    • Sales summaries
      • Returning a list of sales summaries
      • Getting a sales summary by ID
    • Payouts
      • Returning a list of payouts
      • Getting a payout by ID
      • Get a list of transactions included in payout by ID
  • Developer resources
    • Digital River API reference
    • DigitalRiver.js reference
      • Including DigitalRiver.js
      • Initializing DigitalRiver.js
      • DigitalRiver object
      • Elements
        • Amazon Pay element
        • Apple Pay elements
        • Google Pay elements
        • IBAN element
        • iDEAL element
        • Konbini elements
        • Compliance element
        • Offline Refund elements
        • Online Banking elements
        • Tax Identifier element
        • Invoice attribute element
        • Delayed Payment Instructions element
        • PayPal elements
      • Guidelines for capturing payment details
      • Security
      • Digital River payment objects
      • Error types, codes, and objects
    • DigitalRiverCheckout.js reference
      • Including DigitalRiverCheckout.js
      • Initializing DigitalRiverCheckout.js
        • DigitalRiverCheckout configuration object
      • DigitalRiverCheckout object
        • Configuring Prebuilt Checkout
          • Performing actions
          • Defining experience
        • Components
          • Configuring components
          • Address component
          • Shipping component
          • Tax identifier component
          • Invoice component
          • Wallet component
          • Payment component
          • Compliance component
          • Order summary component
          • Thank you component
        • Rendering a checkout button
          • Performing actions on the checkout button
        • Determining the checkout's status
      • Accessing country and currency
    • DynamicPricing.js reference
    • Postman collection
  • administration
    • Sign in
    • Digital River Dashboard
      • Digital River Dashboard quick start guide
      • Key features
      • Reset your password
      • Test and production environments
      • Account
        • Adding an account
        • Switching accounts
        • Account access
      • Profile settings
        • Viewing your personal information
        • Changing your password
        • Updating your phone number
        • Enabling multi-factor authentication
      • Finance
        • Payouts
          • Viewing your payout details
          • Filtering your payouts
          • Exporting your payouts
        • Sales summaries
          • Viewing your sales summaries details
          • Filtering your sales summaries
          • Exporting your sales summaries
          • Exporting your sales summary details
        • Transactions
          • Viewing your transaction details
          • Filtering your transactions
          • Exporting your transactions
      • Order management
        • Orders
          • Searching for orders
          • Filtering your orders
          • Viewing the order details
          • Cancelling items
          • Fulfilling items
          • Downloading an invoice
          • Downloading a credit memo
          • Creating shipping labels
          • Recording a customer's request to be forgotten
          • Viewing returns and refunds
          • Creating a return
          • Accepting a return
          • Creating a refund
          • Viewing the order's timeline
        • Checkouts
          • Searching for checkouts
          • Filtering your checkouts
          • Viewing the checkout details
        • Prebuilt Checkout links
          • Generate Prebuilt Checkout links
          • View and work with Prebuilt Checkout link details
          • Add a customer during Prebuilt Checkout
          • Add a product during Prebuilt Checkout
      • Customers
        • Viewing customer details
        • Searching for customers
        • Filtering your customers
        • Editing account information
        • Adding a customer
        • Tax IDs and certificates
          • Adding a tax certificate
          • Adding a tax ID
          • Deleting a tax ID
        • Metadata
          • Adding metadata
          • Editing metadata
        • Manage subscriptions from the Customer Details page
        • Disabling a customer
        • Recording a customer's request to be forgotten
        • Deleting a customer
      • Catalog
        • SKUs
          • Viewing the SKU details
          • Searching for SKUs
          • Filtering your SKUs
          • Adding a SKU
          • Editing a SKU
          • Deleting a SKU
          • Adding a fee to a SKU
          • Editing a fee
          • Deleting a fee
          • Viewing product tariff codes
        • Managing customer subscriptions from Digital River Dashboard
      • Developers
        • API keys
          • Updating your API version
          • Getting your API keys
          • Changing the API version for your key
          • Creating a restricted key
          • Editing a restricted key
          • Deleting a restricted key
          • Rotating keys
        • Webhooks
          • Creating a webhook
          • Editing a webhook
          • Deleting a webhook
          • Rotating a webhook's secret
        • API logs
          • Filtering the API log
          • Viewing the API log details
        • Event logs
          • Filtering the events log
          • Viewing the event details
      • Settings
        • Users and roles
          • Roles
          • Searching for a user by name or email
          • Filtering your users and roles
          • Adding a user
          • Editing a user
          • Deleting a user
        • Prebuilt Checkout
        • Payment methods
          • Viewing your payment methods
          • Viewing payment method details
            • Enabling currencies
            • Managing countries
          • Enabling or disabling a payment method
  • General Resources
    • eCompass
    • eCompass documentation
    • Release notes
      • 2024
      • 2023
      • 2022
      • 2021
      • 2020
      • 2019
    • Standards and certifications
      • Certification process
      • Compliance requirements
      • Documentation requirements
      • Integration checklists
        • Admin portal
        • Products and SKUs
        • Customers and tax exemptions
        • Checkouts, payment sources, and orders
        • Disclosures, compliance statements, and emails
        • Fulfillments and cancellations
        • Customer portal
        • Order refund synchronization
        • Reversals
        • Error handling
      • Test and use cases
    • Commerce infrastructure
    • Versioning
    • Glossary
Powered by GitBook
On this page
  • Key settings and methods
  • Common Drop-in payments steps
  • Elements prerequisites
  • Purchase flows
  • One-off
  • Subscription
  • Mail order/telephone order
  • Account management flows
  • Saving a credit card for future use
  • Updating a credit card's expiration date or billing address
  1. Integration options
  2. Direct integrations

Building payment workflows

Learn how to create SCA-compliant workflows using Drop-in payments or Elements.

PreviousCountry specsNextHandling redirect payment methods

Last updated 2 months ago

Using or , you can create compliant workflows for and .

Whatever payment solution you use, all SCA requirements are managed by Digital River. Two-factor authentication is handled by our . Our card acquirers use the protocol to communicate with issuing banks. This protocol operates "behind the scenes" and requires no developer interaction.

Key settings and methods

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 in which customers , you should set the checkout's to customer_initiated. If you're using , use the method's to set to checkout and to convenience. With , use the method's configuration object to set futureUse to true and to convenience.

  • When customers are , and decide to , set the checkout's chargeType to customer_initiated and to true. In this flow type, is not supported. Instead, you'll need to use the method.

Common Drop-in payments steps

Elements prerequisites

Purchase flows

One-off

Customers enter their payment information

SCA required?
Drop-in payments supported?
Elements supported?

Yes

Yes

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        flow: "checkout",
        usage: "convenience"
    }
    ...
}
let dropin = digitalriver.createDropin(configuration);

Step four: Drop-in payments are rendered in the designated container on your checkout page.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
let payload = {
    "sessionId": "ea03bf6f-84ef-4993-b1e7-b7d5ecf71d1f",
    "futureUse": false,
    "usage": "convenience",
    ...
}

digitalriver.createSource(payload).then(function(result) {
    if(result.state === "chargeable") {
        sendToBackEnd(result);
    } else {
        doErrorScenario();
    }
});

Customers save their payment information

SCA required?
Drop-in payments supported?
Elements supported?

Yes

Yes

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        "flow": "checkout",
        "showSavePaymentAgreement": true,
        "usage": "convenience"
    },
    ...
}
let dropin = digitalriver.createDropIn(configuration);

Step four: Drop-in payments are rendered in the designated container on your checkout page.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
var payload = {
    "type": "creditCard",
    "sessionId": "ea03bf6f-84ef-4993-b1e7-b7d5ecf71d1f",
    "futureUse": true,
    "usage": "convenience",
    ...
    "mandate": {
        "terms": "Yes, please save this account and payment information for future purchases."
    }
}

digitalriver.createSource(payload).then(function(result) {
    if (result.error) {
        //handle errors
    } else {
        var source = result.source;
        //send source to back end
        sendToBackend(source);
    }
});

Customers retrieve their payment information

SCA required?
Drop-in payments supported?
Elements supported?

Yes

No

Yes

...
digitalriver.authenticateSource({
    "sessionId": "65b1e2c2-632c-4240-8897-195ca22ce108",
    "sourceId": "ee90c07c-5549-4a6b-aa5f-aabe29b1e97a",
    "sourceClientSecret": "ee90c07c-5549-4a6b-aa5f-aabe29b1e97a_51afe818-0e7f-46d7-8257-b209b20f4d8",
    "returnUrl": "https://returnurl.com"
}).then(function(data) {

});
...

Subscription

Customers enter and save their payment information during a subscription acquisition

In this flow, customers save payment information to their account and use that payment source to acquire an auto-renewing subscription.

SCA required?
Drop-in payments supported?
Elements supported?

Yes

Yes

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        "flow": "checkout",
        "showTermsOfSaleDisclosure": true,
        "usage": "subscription"
    },    
    ...
}
let dropin = digitalriver.createDropIn(configuration);

Step four: Drop-in payments are rendered in the designated container on your checkout page.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
var payload = {
    "type": "creditCard",
    "sessionId": "ea03bf6f-84ef-4993-b1e7-b7d5ecf71d1f",
    "futureUse": true,
    "usage": "subscription",
    ...
    "mandate": {
        "terms": "Yes, please save this account and payment information for future purchases."
    }
}

digitalriver.createSource(payload).then(function(result) {
    if (result.error) {
        //handle errors
    } else {
        var source = result.source;
        //send source to back end
        sendToBackend(source);
    }
});

Customers retrieve saved payments during a subscription acquisition

In this flow, customers select a credit card they previously saved to their account and use it to acquire an auto-renewing subscription.

SCA required?
Drop-in payments supported?
Elements supported?

Yes

No

Yes

...
digitalriver.authenticateSource({
    "sessionId": "65b1e2c2-632c-4240-8897-195ca22ce108",
    "sourceId": "ee90c07c-5549-4a6b-aa5f-aabe29b1e97a",
    "sourceClientSecret": "ee90c07c-5549-4a6b-aa5f-aabe29b1e97a_51afe818-0e7f-46d7-8257-b209b20f4d8",
    "returnUrl": "https://returnurl.com"
}).then(function(data) {

});
...

Merchant-initiated auto-renewals

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.

SCA required?
Drop-in payments supported?
Elements supported?

No

N/A

N/A

Mail order/telephone order

SCA required?
Drop-in payments supported?
Elements supported?

No

Yes

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        flow: "checkout",
        usage: "convenience"
    }
    ...
}
let dropin = digitalriver.createDropin(configuration);

Step four: Drop-in payments are rendered in the designated container on your checkout page.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
let payload = {
    "sessionId": "ea03bf6f-84ef-4993-b1e7-b7d5ecf71d1f",
    "futureUse": false,
    "usage": "convenience",
    ...
}

digitalriver.createSource(payload).then(function(result) {
    if(result.state === "chargeable") {
        sendToBackEnd(result);
    } else {
        doErrorScenario();
    }
});

Account management flows

Saving a credit card for future use

Customers use their account portal to save payment information for future transactions in this flow.

SCA required?
Drop-in payments supported?
Elements supported?

Yes

Yes

Yes

let dropin = digitalriver.createDropIn(configuration);

Step four: Drop-in payments are rendered in the designated container on your checkout page.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
var payload = {
    "type": "creditCard",
    "futureUse": true,
    "usage": "subscription",
    ...
    "mandate": {
        "terms": "Yes, please save this account and payment information for future purchases."
    }
}

digitalriver.createSource(payload).then(function(result) {
    if (result.error) {
        //handle errors
    } else {
        var source = result.source;
        //send source to back end
        sendToBackend(source);
    }
});

Updating a credit card's expiration date or billing address

In this flow, customers use their account portal to update their saved credit card's expiration date or billing address.

SCA required?
Drop-in payments supported?
Elements supported?

No

No

Yes

The customer selects the payment method to update.

For any workflow that uses , whether it's intended to handle or , you first need to perform the following steps:

​.

​.

​.

​.

If you're using to build workflows, . We assume you are familiar with and .

For almost all , , and transactions, Digital River supports workflows using or .‌

‌One-off workflows allow customers to , , and their payment information while making one-time purchases.

‌In this flow, customers supply their payment information but don't save it to their account.

Prerequisites: Perform the .

Step one: with all tax, shipping, duty, and fee amounts in a final state and a that is customer_initiated.

Step two: Retrieve the checkout's , and use it to set in the. In options, set to checkout and to convenience.

Step three: Pass the configuration object to the .

Customers enter their payment information and click the pay now button.

If customers complete any that may be required, returns a .

Step five: .

Step six: .

Prerequisites: Refer to the section.

Step one: with all tax, shipping, duty, and fee amounts in a final state and a that is customer_initiated.

Step two: Retrieve the and assign it to sessionId in the method's configuration object. You should also set futureUse to false and to convenience.

After the method is called and customers complete any required SCA, a unique is returned.

Step three: .

Step four: .

In this flow, customers enter payment information and save it to their account.

Prerequisites: Perform the .

Step one: with a and all tax, shipping, duty and fee amounts in a final state. The should be customer_initiated.

Step two: Retrieve the checkout's and use it to set in the . You should also use options to set to checkout, to convenience, and to true.

Step three: Pass the configuration object to the .

Customers enter their credit card information, actively accept the save payment agreement and click the pay now button.

If customers complete any that may be required, returns a that is .

Step five: .

Step six: .

Step seven: .

Prerequisites: Refer to the section. Your flow also needs to display the storage terms and allow customers to save their payment information.

Step one: with a and all tax, shipping, duty and fee amounts in a final state. The should be customer_initiated.

Step two: Retrieve the and assign it to sessionId in the method's configuration object. You should also set futureUse to true and to convenience. Use mandate.terms to pass the save payment agreement that the customer accepts.

After the method is called and customers complete any required SCA, a unique is returned.

Step three: .

Step four: .

Step five: .

In this , customers select a payment method they previously saved to their account. The key step is to call the .

do not currently support retrieving saved payment methods. To handle this flow, use .

Prerequisites: Refer to the section.

Step one: with a and all tax, shipping, duty and fee amounts in a final state. The should be customer_initiated.

Step two: and display them during checkout.

Step three: If the customer uses a saved payment method, you must determine whether SCA is required. To do this, configure and call the method. For details, refer to on the page.

Step four: .

Step five: .

You can create workflows that allow customers to or a during subscription acquisitions and set up workflows for .

SCA is required for but not auto-renewals.

Prerequisites: Perform the .

Step one: with a and all tax, shipping, duty and fee amounts in a final state. Set to customer_initiated and autoRenewal to true.

Step two: Retrieve the checkout's , and use it to set in the . In , set to checkout, to subscription, and to true.

Step three: Pass the configuration object to the .

Customers must enter their payment information, actively accept the terms and click the pay now button.

If customers complete any that may be required, returns a that is .

Step five: .

Step six: .

Step seven: .

Prerequisites: Refer to the section. At some point during the flow, you also need to display the subscription's terms, save the payment agreement, and acquire the customer's active acceptance of them.

Step one: with a and all tax, shipping, duty and fee amounts in a final state. Set to customer_initiated and autoRenewal to true.

Step two: Once the customer selects the option to save the payment method and agrees to the displayed terms, retrieve the and assign it to sessionId in the method's configuration object. You should also set futureUse to true and to subscription. Use mandate.terms to pass the save payment agreement that the customer accepts.

After the method is called and customers complete any required SCA, a unique is returned.

Step three: .

Step four: .

Step five: .

‌The key step is to call the .

does not currently support retrieving stored payment methods. To handle this flow, use .

Prerequisites: Refer to the section.

Step one: with a and all tax, shipping, duty and fee amounts in a final state. Set to customer_initiated and autoRenewal to true.

Step two: and display them to the customer during the checkout process.

Step three: Configure and call the method if the customer uses a saved payment method. For details, refer to on the page.

Step four: .

Step five: .

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 (MOTO) transactions.

Prerequisites: Perform the .

Step one: with a of 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 , and use it to set in the . In options, set to checkout and to convenience.

Step three: Pass the configuration object to the .

The merchant's representative enters the customer's credit card information and clicks the pay now button. If the payment is authorized, then returns a unique in a .

Step five: .

Step six: .

Prerequisites: Refer to the section.

Step one: with a of moto and all tax, shipping, duty, and fee amounts in a final state.

Step two: Retrieve the and assign it to sessionId in the method's configuration object. You should also set futureUse to false and to convenience.

After the method is called and customers complete any required SCA, a unique is returned.

Step three: .

Step four: .

You can create flows that allow customers to manage through their account portal.

In these account management flows, you only need to adhere to when . 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 .

Prerequisites: Perform the .

Step one: On the page where customers manage their payment methods, use the to set to managePaymentMethods and specify a value for 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 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 to reference, you shouldn't provide a . As a result, you'll need to pass the billing information you collect from customers in .\

Step three: Pass the configuration object to the .

Customers enter their payment information, select the save payment agreement option and click the add payment method button.

If customers complete any that may be required, returns a that is .

Step five: .

Prerequisites: Refer to the section. You must display the save payment agreement and acquire the customer's acceptance.

Step one: Once a customer selects the option to save a payment method and agrees to the displayed terms, use the method's configuration object to set futureUse to true.

Make sure you also assign a value to that identifies the future use of the payment source and passes the mandate.terms that the customer agreed to on your storefront.

Once the customer provides the required SCA, a Source in a is returned.

Step two: .

do not support interacting directly with saved payment methods‌

Prerequisites: Refer to the section.

Step one: and display them to the customer.

Step two: Capture the customer's updated expiration date or billing address and pass it to the .

Build a checkout
chargeType
Build a checkout
chargeType
source
source
Drop-in payments
Elements
source
Drop-in payments
Elements
Build a checkout
charge type
source
recurring payment methods
Drop-in payments
Drop-in payments
purchases
account management
SCA-compliant
Drop-in payments
Elements
one-off
subscription
mail-order/telephone-order (MOTO)
enter
save
retrieve
one-off
common Drop-in payments steps
Elements prerequisites
one-off
common Drop-in payments steps
Elements prerequisites
Elements prerequisites
SCA-compliant
recurring payment method
save
retrieve
merchant-initiated autorenewals
common drop-in steps
Elements prerequisites
Elements prerequisites
common Drop-in payments steps
Elements prerequisites
SCA regulations
saving a customer's credit card for future use
updating a credit card's expiration date or billing address
common drop-in steps
Elements prerequisites
Elements prerequisites
Drop-in payments
Elements
Strong Customer Authentication (SCA)
3-D Secure
chargeType
Drop-in payments
DigitalRiver.js with elements
Drop-in payments
purchase transactions
account management
one-off purchase flows
save a new payment source to their account
acquiring an auto-renewing subscription
retrieve a payment source saved to their account
Elements
creating and styling elements
capturing payment details
purchase
SCA
source
Build a checkout
chargeType
SCA
Build a checkout
chargeType
Build a checkout
chargeType
DigitalRiver object
Build a checkout
chargeType
SCA
Build a checkout
chargeType
Build a checkout
chargeType
DigitalRiver object
SCA
Build a checkout
chargeType
payment session
SCA
source
one-off purchase flow
complete the necessary migration to payment sessions
create Drop-in method
create Drop-in method
authenticate source method
authenticateSource()
Authenticating sources
create Drop-in method
authenticate source method
authenticateSource()
Authenticating sources
create Drop-in method
create Drop-in method
createSource()
usage
update source method
Include DigitalRiver.js on your page
Include the Drop-in CSS file
Initialize DigitalRiver.js with your public key
Create a container for Drop-in payments
configurable
onSuccess
configurable
configurable
configuration object's
options
flow
usage
showTermsofSaleDisclosure
sessionId
billingAddress
configurable
onSuccess
readyForStorage
subscription acquisitions
merchant-initiated
mail order and telephone order
moto
registered customer
registered customer
registered customer
registered customer
registered customer
registered customer
Retrieve the customer's payment sources
Retrieve the customer's payment sources
Retrieve the customer's payment sources
Attach the Source to the Checkout
Attach the Source to the Checkout
Attach the Source to the Customer
Attach the Source to the Checkout
Attach the Source to the Customer
Attach the Source to the Checkout
Attach the Source to the Checkout
Attach the Source to the Customer
Attach the Source to the Checkout
Attach the Source to the Customer
Attach the Source to the Checkout
Attach the Source to the Checkout
Attach the Source to the Checkout
Attach the Source to a Checkout
Attach the Source to the Customer
Attach the Source to the Customer
autoRenewal
authenticate source method
createDropIn()
createSource()
usage
authenticateSource()
configurable options
flow
usage
createSource()
usage
createSource()
usage
createSource()
usage
createSource()
usage
sessionId
configuration object
flow
usage
sessionId
Drop-in payments' configuration object
flow
usage
showSavePaymentAgreement
onSuccess
readyForStorage
sessionId
configuration object
options
flow
usage
showTermsOfSaleDisclosure
onSuccess
readyForStorage
sessionId
Drop-in payments' configuration object
flow
usage
configurable
onSuccess
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
Convert the Checkout to an Order
chargeable state
source
source
chargeable state
source
payment session identifier
payment session identifier
payment session identifier
payment session identifier
payment session identifier
payment session identifier
payment session identifier
payment session identifier
Click to enlarge image