text: After you apply a refund request to these types of payment methods, Digital River typically moves the refund's state
  , which triggers the creation of a refund.pending_information
  The event's data.object
  . Within this data structure is a token
  and an expiresTime
  . The expiresTime
  of the token
  is 90 days after the event's createdTime
  events by passing tokenInformation
  to your front-end.
  On your page dedicated to collecting bank information during refunds, use token
  to set refundToken
  in the create offline refund element's 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, mount the element 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 on ready event.
  Make sure you display the expiration time in a more human-readable form.
  Digital River sends a change event 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 unmount()
  to remove the offline refund element from the data collection page.
  Once you receive either the refund.complete
  event, send the appropriate notification to customers.