LogoLogo
System Status
  • Commerce API
    • Test and use cases
    • Roles and permissions
    • Sending API calls
  • Shopper APIs
    • Shopper basics
      • Common use cases
        • Creating a customer
        • Applying store credit
        • Private store workflow
        • Guest checkout
    • OAuth
      • Authentication
      • OAuth 2.0 APIs
      • Token
      • Access tokens
      • Session-aware access tokens
      • Authorizing a shopper
    • Shoppers
      • Managing shoppers
        • User management
        • Single sign-on (SSO)
        • Data validation
        • Bulk user management
        • Bulk user account export
      • Managing a shopper's account
      • Managing a shopper's address
      • Managing payment options
    • Product discovery
      • Categories
      • Products
      • Product variations
      • Pricing
      • Inventory status
      • Financing
      • Offers
        • Understanding offers
        • How to use point of promotions (POPs)
          • Retrieving all point of promotion offers for a specific product
          • Retrieving all offers for a specific point of promotion
        • How to use offers
      • Private stores
        • Managing private stores
        • Submitting an order for a private store
        • Useful APIs
      • Fulfillment
        • Electronic Fulfillment Service (OFI)
        • Digital rights
        • Digital rights revocation
        • Physical fulfillment
          • EDI X12 832 definition data elements
          • EDI X12 846 definition data elements
          • EDI X12 850 definition data elements
          • EDI X12 855 definition data elements
          • EDI X12 856 definition data elements
          • EDI X12 180-1 definition data elements
          • EDI X12 180-2 definition of data elements
          • EDI X12 180-3 definition of data elements
    • Cart
      • Applying a shopper to a cart
      • Getting the current cart
      • Creating or updating a cart
        • Adding a product to a cart
          • Gifting
        • Capturing the customer's IP address
        • Providing address information
        • Managing the shipping or billing address
        • Providing subscription information
        • Managing payment methods
        • Capturing the Terms of Sale (TOS) acceptance
      • Managing offers in a cart
        • Applying an offer
        • Applying a coupon or promo code
        • Getting all applied offers
        • Removing an applied offer
        • Removing eligible offers
        • Reconciling conflicting offers
        • Dynamic offers/personalization
          • Skipping Global Commerce merchandising offer arbitration
          • Triggering a promotional URL offer
          • Overriding a promotional URL offer discount
      • Pricing
        • Landed cost
          • Mixed cart support
          • Tax-included pretty price
      • Redirecting to a Digital River-hosted cart
      • Configuring taxes
        • Managing tax identifiers
      • Managing shipping options
        • Getting shipping options
        • Providing a shipping discount
      • Managing line items
      • Applying a price override
      • Managing payment sessions
      • Managing web checkout
      • Submitting a cart
        • Initiating a charge
        • Authorization declines
      • Resuming cart submission
      • HGOP2
    • Orders
      • Getting orders
      • Selling entities
      • Retrieving addresses from an order
      • Retrieving line items from an order
      • Order lookup
      • Returns
        • Initiate an authenticated session
        • Setting up returns in Global Commerce
        • Managing returns
    • Subscriptions
      • Retrieve the subscription
        • Getting all orders for a subscription
        • Getting a subscription's pending actions
        • Getting all subscriptions for a shopper
        • Getting a subscription by identifier
      • Update subscription at the next renewal
        • Changing the subscription renewal type
        • Changing the subscription renewal quantity
        • Adding or updating a perpetual unit price
        • Changing the subscription's payment option
        • Changing the subscription's payment source
      • Immediately change the subscription
        • Updating the subscription's shipping address
        • Updating a subscription's billing and shipping email address
        • Cancelling a subscription
      • Immediately apply a midterm subscription change
        • Reducing the subscription renewal quantity
  • Admin APIs
    • Admin basics
      • Available Admin API calls
    • Order management
      • Getting the order's details
      • Downloading the invoice
    • Offer management
    • Refund management
      • Authorization
      • Refund reason codes
      • Creating a satisfaction refund
      • Getting the available refunds for a specific order
      • Getting refunds for a specific order
      • Getting refunds available for a shopper's order
      • Getting the JSON schema for an order refund
      • Managing a refund for a delayed payment method
      • Refund error scenarios
    • Subscription management
      • Retrieve the subscription
        • Getting all orders for a subscription
        • Getting a subscription's pending actions
        • Getting all subscriptions for a shopper
        • Getting a subscription by identifier
      • Update the subscription at the next renewal
        • Changing the subscription renewal type
        • Changing the subscription renewal product
        • Changing the subscription renewal price
        • Changing the subscription renewal quantity
        • Adding or updating a perpetual unit price
        • Changing the subscription's payment option
        • Changing the subscription's payment source
      • Immediately change the subscription
        • Activating a subscription
        • Changing the subscription's external reference identifier
        • Updating a subscription's billing and shipping email address
        • Cancelling a subscription
        • Updating the subscription's expiration date
      • Immediately apply a midterm subscription change
        • Applying a midterm change with price override
        • Reducing the subscription renewal quantity
      • Subscription notifications
        • Updating the subscriber's email address
        • Card Account Updater
        • Sending a payment information change notification
        • Sending an expired credit card notification
        • Sending an invalid payment account notification
        • Sending a payment failure notification
        • Sending a subscription renewal reminder notification
        • Setting up subscription renewal reminders
        • Setting up trial subscription renewal reminders
        • Setting up marketing reminders
      • Using the Expired Card Optimizer
    • Customer management
      • Retrieving customer details
      • Requesting PII removal for a customer
    • Site management
      • Configuring authorized shipping and billing countries
      • Getting a site's authorized billing countries
      • Getting a site's authorized shipping countries
    • Product management
      • Getting started
      • Manage products (asynchronous API)
        • Creating or updating a product
        • Adding or updating a product variation
        • Deploying a product
        • Applying live changes
        • Retiring a product
        • Deleting a product variation
        • Deleting a base or individual product's locale
      • Retrieve products (synchronous API)
        • Getting a product by locale
        • Getting a product variation
        • Getting a product variation by locale
      • Get the task status for a product (synchronous API)
        • Getting the latest information on a product task
        • Retrieving the tasks for a specific product
        • Retrieving the tasks for products
      • Bulk operation
        • Asynchronous bulk operations
          • Creating products in bulk
          • Updating products in bulk
          • Deploying products in bulk
          • Deleting product variations in bulk
        • Bulk product upload (BPU)
        • Bulk Product Export (BPE)
          • Line-item level satisfaction refund
          • Order-level satisfaction refund
          • Auto-created line-item level return product
          • Line-item level return product
    • File management
      • Downloading a file
  • Payments
    • Payments 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 BLIK
          • Configuring Boleto
          • 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
      • BLIK
      • Boleto
      • CCAvenue
      • Clearpay
      • Credit Cards
      • FPX Online Banking
      • Google Pay
      • iDEAL
      • Klarna
      • Konbini
      • Korea Bank Transfer (Online Banking)
      • Online Banking (IBP)
      • 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
    • Building payment workflows
      • Flows by payment type
      • Handling redirect payment methods
    • PSD2 and SCA
    • Payment testing scenarios
      • Testing standard payment methods
      • Testing redirect payment methods
      • Testing receiver payment methods
      • Testing the CCAvenue payment method
  • Events
    • Events overview
    • Responding to events
    • Event types
      • Delayed payment event types
        • Delayed payment expired event
          • Boleto
          • Konbini
          • Wire Transfer
        • Delayed payment reminder event
          • Boleto
          • Konbini
          • Wire Transfer
      • Subscription event types
        • Subscription created event
        • Subscription updated event
        • Subscription action processed event
        • Subscription cancelled event
        • Subscription credit card expired event
        • Subscription payment information changed event
        • Subscription renewal reminder event
        • Subscription renewed event
        • Subscription trial converted event
        • Subscription trial renewal reminder event
        • Subscription payment failed event
      • Post-order event types
        • Invoice created event
        • Refund credit memo event
      • Inventory event types
        • Inventory out of stock event
        • Inventory source and management
        • Inventory self-managed updated event
        • Inventory fulfiller-managed updated event
      • Post-order Notification Integration Guide
    • Webhooks
      • Commerce API safelist
      • Searching for a webhook
      • Creating a webhook
      • Using webhooks
      • Editing a webhook
      • Turning webhooks on or off
      • Revealing a webhook's secret
      • Rotating a webhook's secret
      • Viewing the webhook details
      • Deleting a webhook
  • Developer Resources
    • Postman collection
    • Commerce API references
    • Shopper APIs reference
    • Admin APIs 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 element
        • Online Banking elements
        • Tax Identifier element
        • Delayed payment instructions element
        • PayPal elements
      • Guidelines for capturing payment details
      • Security
      • Digital River payment objects
      • Error types, codes, and objects
  • General resources
    • Global Commerce
    • Global Commerce
      • Company hierarchy
      • Categories
        • Getting a list of categories
      • Products
        • Product scenarios
        • Individual products
          • Creating an individual product
        • Base product with variants
          • Creating a base product with variants
        • Bundle offers
          • Creating a prorated bundle offer with a subscription
        • Product combination
          • Creating a product combination
        • Gifting
        • Inventory status
      • Customer service
        • Log a shopper's request to remove PII
      • Customers
        • Creating a customer
        • Digital River-maintained customer login
        • Client-maintained customer login
      • Transparent Commerce purchase flow
    • eCompass
    • eCompass documentation
    • Release notes
      • 2024
      • 2024 latest
      • 2023
      • 2022
      • 2021
      • 2020
Powered by GitBook
On this page
  • Limitations and constraints
  • Common Drop-in payment steps
  • Elements prerequisites
  • Purchase Flows
  • One-off
  • Subscription
  • Mail order/telephone order
  • Account management flows
  • Saving a credit card
  • Updating a credit card's expiration date or billing address

Was this helpful?

  1. Payments

Building payment workflows

Learn how to create SCA-compliant workflows using Drop-in payments and DigitalRiver.js with elements.

PreviousRetrieving sourcesNextFlows by payment type

Last updated 2 months ago

Was this helpful?

You can create Strong Customer Authentication (SCA) compliant workflows for and .

When building workflows that use Drop-in payments, you'll need to perform some before proceeding to the workflow's specific steps.‌ For workflows using , you must also complete some .

Each purchase and account management workflow has some .

Whether you are using Drop-in payments or , Digital River automatically manages any SCA requirements. Our authenticate source method handles two-factor authentication. Our card acquirers use the protocol to communicate with issuing banks. This protocol operates "behind the scenes" and requires no developer interaction.

Limitations and constraints

Note the following limitations and constraints when building your payments workflow.

  • Do not change the currency when a secondary source is in the cart. Specify the correct currency when creating a . Do not change the currency after you to the cart. If you change the currency when calling /v1/shoppers, a response contains specific information about what triggered the failure. In this instance, one of the currencies in the cart is not supported.

Error
{
    "errors": {
        "error": [
            {
                "relation": "https://developers.digitalriver.com/v1/shoppers/ShoppersResource",
                "code": "invalid-request",
                "description": "One or more sources in the cart does not support locale {Locale} and currency {Currency}."
            }
        ]
    }

}
  • You can't use the store credit to buy subscription products, pre-order products, or products on backorder. Additionally, you can't link more than one store credit source to an order, as multiple secondary sources are not currently supported.

Common Drop-in payment steps

Elements prerequisites

Purchase Flows

One-off

Customers enter their credit card information

‌In this flow, customers supply their credit card information during a one-off transaction but don't save it to their accounts.

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);

Drop-in payments render in the specified container.

...
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 credit card information

In this flow, customers enter credit card information and save it to their account during a one-off transaction.

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

Yes

Yes

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        "showSavePaymentAgreement": true,
        "usage": "subscription"
    },
    ...
}

let dropin = digitalriver.createDropIn(configuration);
let dropin = digitalriver.createDropIn(configuration);

The modal renders in the specified container.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...

Step five: Attach the source to the shopper.

Step six: Attach the shopper to the cart.

Step seven: Create the order by submitting the cart.

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);
    }
});

Once the method is called and the customer provides the required SCA, a unique Source in a chargeable source is returned.

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

Shopper 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);

Drop-in renders in the specified container.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...
var payload = {
    "type": "creditCard",
    "sessionId": "ea03bf6f-84ef-4993-b1e7-b7d5ecf71d1f",
    "futureUse": true,
    "usage": "subscription",
    ...
    "mandate": {
        "terms": "Yes, 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 the source to back end
        sendToBackend(source);
    }
});

Shoppers retrieve saved payment during a subscription acquisition

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

SCA required?

Drop-in 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 flow, you initiate a subscription auto-renewal for the shopper. Although this flow type does not require SCA, you should ensure you're properly managing subscriptions, setting up auto-renewals, and initiating the charge type during the checkout process.

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

No

Yes

let configuration = {
    sessionId: "d3941a36-6821-4d93-be23-6190226ae5f7",
    options: {
        flow: "checkout",
        usage: "convenience"
    }
    ...
}

Step three: Use the configuration object to instantiate Drop-in payments.

let dropin = digitalriver.createDropin(configuration);

The modal window renders in the specified container.

...
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

C, customers can use their account portal to save credit card information for future transactions.

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

Yes

Yes

Yes

Step one: Go to a page in your integration where customers manage their payment methods.

let configuration = {
    options: {
        "flow": "managePaymentMethods",
        "usage": "subscription"
    },
    ...
}
  
let dropin = digitalriverpayments.createDropIn(configuration);

The modal window renders in the specified container.

...
onSuccess: function (data) { doSometingWithTheSource(data) },
...

Step six: Attach the source to the shopper.

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

Customers use their account portal to update their saved credit card's expiration date or billing address in this flow.

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

No

No

Yes

You must perform the following steps for any workflow that uses Drop-in payments, whether built for or .‌

​.

​.

.

.

Once you've completed these initial steps, you can perform those specific to your desired or scenario.

You need to use payment sessions when using to build workflows. So ensure you've . We assume you are familiar with and .

Once you've completed these prerequisites, you can perform the steps specific to your desired or scenario.

For almost all , , and transactions, Digital River supports workflows using Drop-in payments or .‌

‌You can develop workflows that allow customers to , , and their payment information while making one-off purchases.

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 cart's , and use it to set the sessionId in the Drop-in payments' . In , set flow to checkout and to convenience, and (to prompt Drop-in payments to display the save payment option) to true.

Step three: Use the configuration object to .

Step four: Specify on your cart page.

Customers enter their credit card information and click the Pay Now button.

If the customer completes the , then the d is called, and Digital River returns a unique source in 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 from the cart, and use it to configure the method. The configuration object should also set futureUse to false and to convenience.

A unique Source in a is returned once the method is called and the shopper provides the required SCA.

Step three: .

Step four: .

Prerequisites: Perform the .

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

Step two: Retrieve the cart's , and use it to set the sessionId in the configuration object. In the configuration , set flow to checkout and to convenience. To prompt Drop-in payments to display the save payment option, set showSavePaymentAgreement to true.

You should also configure the usage parameter. Doing so identifies the .

Step three: Use the configuration object to .

Step four: on your cart page.

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

If the customer completes the SCA steps necessary to make the source chargeable, then the d is called, and Digital River returns a unique Source in a .

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

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

Step two: Retrieve the and use it to configure the method. The configuration object should also set futureUse to true and to convenience. Use mandate.terms to pass the save payment agreement that the customer accepts.

Step three: .

Step four: .

Step five: .

In this one-off purchase flow, the customers select a credit card they previously saved to their account. The key step is to call the .

Drop-in payments do not currently support retrieving stored payment methods. To handle this flow, use .

Prerequisites: Refer to the section.

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

Step two: and display them to the shopper during checkout.

Step three: If the shopper selects a saved payment method, you must determine whether SCA is required. To do this, configure and call the method. For details, refer to Authenticating sources on the DigitalRiver object

Step four:.

Step five: .

You can create workflows allowing customers to or a during subscription acquisitions. You can also set up workflows for .

Prerequisites: Perform the .

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

Step two: Retrieve the from the cart, and use it to set the sessionId in the .

In , set flow to checkout and to convenience, and (to prompt Drop-in payments to display the save payment option) to true.

Step three: Use the configuration object to .

Step four: Specify on your cart page.

Shoppers must enter their credit card information and click the Pay Now button.

If the shopper completes the necessary steps, then the is called an,d Digital River returns a unique source in a that is .

Step five: .

Step six: .

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 an authenticated customer, and all tax, shipping, duty, and fee amounts are in a final state. Set chargeType to 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 use it to configure the method. The configuration object should also set futureUse to true and to subscription. Use mandate.terms to pass the save payment agreement that the customer accepts.

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

Step three: .

Step four:

Step five: .

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

Prerequisites: Refer to the section.

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

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

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

Step four: .

Step five: .

is not required for transactions where shoppers provide payment details by mail, fax, or telephone. But both 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 payment session identifier, and use it to set sessionId in the . In options, set to checkout and to convenience.

Step four: Specify on your checkout page.

The merchant's representative enters the customer's credit card information and clicks the Pay Now button. If the payment is authorized, then the is called, and Digital River returns a unique source 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 payment session identifier, and use it to configure the method. The configuration object should also set futureUse to false and to convenience.

Once the method is invoked and payment is authorized, a unique Source is returned in a .

Step four: .

Step five: .

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, make sure you identify the future use of the source. This increases the probability that future transactions will be approved.

You're not required to provide SCA when .

Drop-in paymentsPrerequisites: Perform the .

Step two: In the , set flow to managePaymentMethods and specify a value for that identifies the potential future use of the payment source.

Step three: Use the configuration object to .

Step four: Specify on the account management page.

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

If the shopper completes the necessary steps, then the is called, and Digital River returns a unique source in a that is .

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

Step one: If a customer selects the option to save a payment method and agrees to the displayed terms, the configuration object should set futureUse to true, configure to identify the future use of the payment source and provide the mandate.terms that the customer agreed to on your storefront.

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

Step three: .

do not support interacting directly with saved payment methods.‌

Prerequisites: Refer to the section.

Step one: and display them to the shopper. The shopper selects the payment method to update.

Step two: Capture the updated expiration date from the shopper and pass it to the .

Create a cart
chargeType
Create the order by submitting the cart
Create the order by submitting the cart
Create a cart
chargeType
Create the order by submitting the cart
Elements
Create a cart
chargeType
Attach the source to the cart
Create the order by submitting the cart
Create the order by submitting the cart
Create the order by submitting the cart
Drop-in payments
Elements
Create the order by submitting the cart
Create the order by submitting the cart
Create the order by submitting the cart
recurring payment methods
purchases
account management
purchase
account management
purchase
account management
enter
save
retrieve
common Drop-in payments steps
Elements prerequisites
common Drop-in payments steps
Elements prerequisites
Elements prerequisites
SCA-compliant
recurring payment method
save
retrieve
merchant-initiated autorenewals
common Drop-in payments 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 payments steps
Elements prerequisites
Drop-in payments
Elements prerequisites
DigitalRiver.js with elements
DigitalRiver.js with elements
3-D Secure
purchase transactions
account management
common initial steps
prerequisites
key settings and methods
DigitalRiver.js with elements
creating and styling elements
SCA-compliant
DigitalRiver.js elements
one-off
subscription
SCA
chargeType
Drop-in payments
payment session identifier
chargeType
customer_initiate
SCA
customer_initiate
chargeType
customer_initiate
DigitalRiver object
SCA
Drop-in payments
chargeType
charge type
SCA
flow
mail-order/telephone-order (MOTO)
mail order and telephone order
moto
completed the necessary migration
payment session identifier
payment session identifier
payment session identifier
payment session identifier
payment session identifier
Attach the source to a cart
Attach the source to the customer
Attach the source to the cart
secondary payment source
apply the secondary source
capturing payment details
createSource()
usage
createSource()
usage
authenticateSource()
authenticateSource()
Authenticating sources
createSource()
usage
update source method
createSource()
authenticate source method
Retrieve the customer's payment sources
Retrieve the shopper's payment sources
Retrieve the shopper's payment sources
Attach the source to the cart
chargeable state
Attach the source to the shopper
chargeable state
Attach the source to the shopper
Attach the shopper to the cart.
Attach the source to a cart
Attach the source to the cart
chargeable state
Attach the source to a cart
chargeable state
Attach the source to the shopper
409 Conflict
chargeable state
chargeable state
chargeable state
chargeable state
chargeable state
authenticated customer
authenticated customer
Create a cart
Create a cart
Create a cart
Create a cart
Create a cart
Create a cart
Create a cart
Include DigitalRiver.js on your page
Include the Drop-in payments CSS file
​Initialize DigitalRiver.js with your public key
​Create a container for Drop-in payments
configuration object
options
usage
showSavePaymentAgreement
instantiate Drop-in Payments
a container to place Drop-in payments
configurable
onSuccess metho
options
usage
future use of the payment source
instantiate Drop-in payments
Specify a container to place Drop-in payments
configurable
onSuccess metho
Drop-in payments configuration object
options
usage
showTermsOfSaleDisclosure
instantiate Drop-in payments
a container to place Drop-in payments
configurable
onSucess method
readyForStorage
usage
Drop-in payments' configuration object
usage
a container to place Drop-in payments
configurable
onSuccess method
configuration object's options
usage
instantiate Drop-in payments
a container to place Drop-in payments
configurable
onSucess method
readyForStorage
usage