Refund
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose refund event overview and guidance on when to send the event audience developers implementing refund or reversal workflows applies to integrations evaluating refund activity for identity risk does not apply to payment authorization or non financial identity events the refund call is intended to retrieve a recommendation code when a user attempts to request a refund for goods or services on your website timing the api call should come to the after a user sends a request for a refund requests include item not recieved, item damaged, refund, and reship after they pass error handling, and you retrieve their ip address, and user agent before you send the result of their request flow refund flow diagram user arrives on site and logs in user initiates a refund request client processes frontend validation to ensure all fields are filled in properly client processes backend validation (invalid routing number, verification failed, and so forth client retrieves account information, ip, and user agent client's backend server calls consolidates data and responds with a score client determines appropriate action for the refund request see also refund fields https //atlas accertify com/public apis/refund fields