Handling delayed payment methods
In Direct Integrations, gain a better understanding of how to handle transactions funded with a delayed payment method
Last updated
In Direct Integrations, gain a better understanding of how to handle transactions funded with a delayed payment method
Last updated
If customers opt to fund a transaction with a payment method whose resulting has a flow of receiver, such as Konbini or Wire Transfer, they must be given instructions on how to push the funds to the payment provider.
This page applies only to those who build their checkout experience using the Direct Integrations approach. If you implement a low-code checkout option, Digital River displays the delayed payment instructions to customers.
To provide customers with these instructions, first submit the create order request. If you get back a 201 Created and is pending_payment, then check the value of payment.session.nextAction.action.
If action is show_payment_instructions, then retrieve sourceId and sourceClientSecret from nextAction.data and use them to configure the create delayed payment instructions element method.
Next call mount() to display the element on your order confirmation page. Alternatively, you may want to include a link on the order confirmation page that redirects customers to another page and displays the element there.
When on ready executes, the instructions are displayed to customers.
Once the instructions are loaded in the designated container, they usually contain the number of days that customers have to push payment.
If an state is pending_payment and action is redirect, refer to Handling redirect payment methods.
If customers follow the instructions and payment is successfully authorized, you'll need to handle the with a type of order.accepted. Otherwise, if they don't make payment within the allotted time, make sure you're set up to handle order.cancelled.
