Payment
4 min
\<font color="#b6c7cb">\</font> topic type concept purpose payment event overview and guidance on when to send the event audience developers implementing checkout or payment workflows applies to integrations evaluating payments from an identity risk perspective does not apply to withdrawals, transfers, or non payment identity events the payment call is intended to retrieve an score when a user attempts to pay for goods or services on your website timing the api call should come to the after a user submits an order after they pass error handling, and you retrieve their account details, ip address, and user agent before you send the result of their request \<font color="#386b84">note\</font> if you already use the for payment fraud screening and send all payments there, can call this event on your behalf, so you don't have to code this event flow payment flow diagram user chooses a product, checks out, enters details, and submits order client processes front end validation to ensure all fields are filled in properly client retrieves account information, ip, and user agent client's backend server calls whether the payment was successful or a failure consolidates data and returns a score client determines to process the transaction or not see also payment fields https //atlas accertify com/public apis/payment fields