Refunding asynchronous payment methods
Learn how to refund transactions that use delayed payment methods
Last updated
Learn how to refund transactions that use delayed payment methods
Last updated
payment providers must usually collect additional customer information before issuing a refund on an , such as , , and .
After you apply a to these types of payment methods, Digital River typically moves the state to pending_information, which triggers the creation of a event.
The data.object contains tokenInformation. Within this data structure is a token and an expiresTime. The expiresTime of the token is 90 days after the event's createdTime.
Handle refund.pending_information events by passing tokenInformation and expiresTime to your front-end.
Once you receive either the refund.complete or refund.failed event, send the appropriate notification to customers.
On your page dedicated to collecting bank information during refunds, use token to set refundToken in the configuration object. Once invoked, this method sends the token to Digital River's payment services, requesting a schema that defines the data fields customers must complete.
On the same page, and inform customers that they must enter and submit the requested information by expiresTime. The designated container displays a form with the required fields for customers and triggers the .
Digital River sends a once customers follow these instructions and the data is accepted. Handle it by redirecting customers to a page that notifies them the refund request has been successfully submitted. You can also use either or to remove the offline refund element from the data collection page.