Learn about the integrated risk screening flows.
A Session ID is generated and device data is collected.
The customer enters their payment details and initiates the transaction.
You call PXP's Transactions API passing the Session ID (from the device data collection process) and other transaction data.
PXP performs the following checks before proceeding:
- Confirms the merchant's subscription to the transaction risk screening service.
- Validates that the assessment mode is set to
pre-authorisation
.
If the transaction qualifies, it's sent to the third-party provider for risk assessment.
The provider returns a risk decision:
- If the outcome is
Accept
, PXP proceeds with the authorisation request to the issuer and then relays the final authorisation status (Approved
orRefused
) back to you. - If the outcome is
Reject
, PXP returns aRefused
status to you, preventing further processing.
A feedback call is made to the provider to update transaction outcome data.
A Session ID is generated and device data is collected.
The customer enters their payment details and initiates the transaction.
You send an authorisation request to PXP using the standard Transactions API.
If the transaction is declined by the issuer, the flow ends and PXP returns a Refused
status to you. No further action is taken.
If the transaction is authorised, PXP proceeds with risk evaluation.
PXP performs the following checks before proceeding:
- Confirms your subscription to the transaction risk screening service.
- Validates that the assessment mode is set to
post-authorisation
.
If the transaction qualifies, it's sent to the third-party provider for risk assessment.
The provider returns a risk decision:
- If the outcome is
Accept
, PXP returns the authorisation statusApproved
to you and captures the transaction. - If the outcome is
Reject
, PXP returns aRefused
status to you and cancels the transaction.
A feedback call is made to the provider to update transaction outcome data.