Pre-authorization
Pre-authorization fraud checks involve verifying the validity of the payment method, checking the customer’s identity, and assessing the risk associated with the transaction before it is authorized. This helps prevent fraudulent transactions from being approved in the first place and, in cases where 3DS is mandatory or recommended, this creates a flow without 3DS for low-risk customers, ensuring they can complete their order with minimal friction.Post-authorization
Post-authorization fraud checks involve monitoring transactions after they have been authorized to identify any suspicious activity. This can include analyzing transaction data for patterns indicating fraud or conducting manual reviews of transactions flagged as potentially fraudulent.Fraud checks within Primer
Primer has integrations with 3rd party fraud detection providers, enabling you to easily configure pre-authorization and/or post-authorization fraud checks as part of your payment flow with your preferred fraud detection provider. Fraud checks are embedded into the authorization flow and you have flexibility over the business logic. Similarly to processing payments, Primer has simplified the setup of fraud checks through its unified framework.Not all fraud detection providers support all payment methods. You can check payment method compatibility with your chosen fraud detection provider in the Fraud Detection Providers section of the docs.
Pre-authorization fraud checks
Pre-authorization fraud checks can have the following outcomes:
You can determine how to handle all outcomes within the “Authorize Payment” action in Workflows.
Post-authorization fraud checks
Post-authorization fraud checks have the following outcomes:
Primer simplifies the configuration for post-authorization fraud checks by always canceling the payment for the
Reject outcome.
See our Get Started guide for how to configure your pre-authorization and/or post-authorization fraud checks on Primer.