configurationobject. The object contains both required and optional values.
showSavePaymentAgreementoption when configuring Drop-in Payments.
onSuccessevent returns the
sessionIdin your configuration object. Instead, you should provide a flow variable that tells Drop-in Payments you are collecting details for future use.
onSuccessevent will return this information with a
disableAutomaticRedirectsattribute if you do not want Drop-in Payments to redirect your customer to the payment provider. Use this setting in your checkout flow if you do not want to create the order from Drop-in Payments. In this scenario, you can allow your customer to choose their payment method, review and then authorize it later by redirecting the customer to the
redirect.returnUrlwhen the customer has reviewed the order totals and is ready to create their order.
localeyou used when initializing DigitalRiver.js.
usagevalue you select should be the one that most closely corresponds to your business model. The available options are subscription, convenience, and unscheduled.
subscriptionwhen you create sources that are used primarily for recurring transactions, made at regular intervals for a product or a service.
conveniencesetting applies mainly to saved payment sources that are used for one-off transactions. These are sources where customers are typically present during the checkout flow and want to quickly access their payment information. Select this option if you don't offer subscriptions or don't have unscheduled merchant initiated transactions
unscheduledwhen you create sources for unscheduled merchant initiated transactions. These are contracts that occur on a non-fixed schedule using saved card information. Automatic top-ups are an example of one such transaction. They occur whenever a customer's balance drops below a pre-defined amount.
"paymentMethodTypes"array of the available payment methods.