Drop-in
Drop-in is our all-in-one solution for accepting payments and ensuring compliance. Use this solution for a quick way to start accepting payments with ease.
Use Drop-in as your payment method solution if you want:
To receive newly supported payment methods automatically without deploying code
Out of the box support for PSD2; including Strong Customer Authentication (SCA)
To ensure compliance for transactions and payment method collection/usage
Drop-in references the DigitalRiver.js library and provides a default look and feel that offers levels of customization. Drop-in automatically displays supported payments based on data collected during the cart session. Adding a new payment method does not require any additional implementation effort, but may require additional configuration steps.
If you want to customize the look and feel of Drop-in, see Configuring payment methods within Drop-in for more information.
The following table lists the payment methods that Drop-in supports and indicates whether they can be used in initial purchases, subscription renewals, or both.
Payment method | One-off purchases | Recurring payments | Authentication flow | Test environment status |
Alipay | X | |
| Supported |
X | |
| In progress | |
bPay | X | |
| In progress |
X | X |
| Supported | |
X | X |
| Supported | |
X | |
| Supported | |
Klarna | X | X |
| Supported |
Konbini | X | |
| In progress |
X | |
| In progress | |
X | |
| Supported | |
PayCo | X | |
| In progress |
PayPal | X | |
| Supported |
X | X |
| Supported | |
X | |
| Supported | |
TreviPay | X | X |
| Supported |
X | |
| Supported |
When the client goes to checkout, the client-server sends a create cart request to Digital River and Digital River returns the cart. The client-server then sends a request to provide the payment session ID to the client's front end. The client front end instantiates Drop-in with the payment session ID and configurations, and Drop-in displays the payment methods. When the customer selects a payment method and provides their payment details, the client front end triggers an onSuccess event and sends the source ID to the client-server. The client-server uses the source with the cart or shopper.
You can choose how you want to embed Drop-in based on how you want to use it. The following table shows your options.
How do you want to use Drop-in? | Do you need to store payment methods? | Instructions | Example |
I want to use Drop-in to collect payment as part of my checkout flow. | I do not need to store payment methods. | ||
| I want to offer my customer the ability to store payment methods. | See Allowing the customer to save their payment credentials. | Drop-in that allows saving payment methods within a checkout flow |
I want to use Drop-in to collect payment data from a page where my customer manages or adds payment methods to their account. | I want to use a mode configured specifically for storing customer payment methods. | See Using Drop-in to collect payment details on a My Account page. | Drop-in that allows adding payment methods on a My Account page |
Digital River helps you get up and running quickly. Follow the instructions in the Drop-in integration guide to discover how easily you can integrate Digital River payment methods into your app or website.
