Withdrawal
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose withdrawal event overview and guidance on when to send the event audience developers implementing fund withdrawal workflows applies to integrations evaluating withdrawal activity for identity risk does not apply to gaming withdrawals or non financial identity events the withdrawal call is intended to retrieve an score when a producer attempts to withdraw funds on your website timing the api call should come to the after a user initiates a withdrawal request after they pass error handling, and you retrieve their account details, ip address, and user agent before you send the result of their request flow withdrawal flow diagram withdrawal flow account protection user arrives on site and logs in user initiates a withdrawal 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 back end server calls consolidates data and responds with a score client determines appropriate action for the withdrawal request see also withdrawal fields https //atlas accertify com/public apis/withdrawal fields