How Drop-in payments work

Learn how Drop-in payments works

When customers initiate checkout, the client-server sends a create checkout request to Digital River and Digital River returns a checkout. The client-server then sends the payment session identifier to the client's front end. The client front end uses this payment session identifier, along with other configuration settings, to instantiate Drop-in payments. Once instantiated, transaction applicable payment methods are displayed in a modal window. When customers select a payment method and provide their payment details, an onSuccess event is triggered and the source identifier is sent to the client-server. The client-server uses that identifier to associate the source with checkouts and/or customers.

To get a better understanding of how the process works, check out the interactive Drop-in builder.

Drop-in payments flows

The following table is meant to help you better understand your Drop-in payments embed options:

Collect payment as part of a checkout flow	No	See Using Drop-in payments within your checkout flow.
Offer customers the ability to store payment methods	Yes	See Allowing the customer to save their payment credentials.
Collect payment data from a page where customers manage or add payment methods to their accounts	Yes	See Using Drop-in to collect payment details on a My Account page.