Skip to content

About standalone flows

Learn about the standalone risk screening flows.

Pre-authorisation

Step 1: Session initialisation

A session ID is generated and device data is collected.

Step 2: Risk screening request

You use the PXP Standalone Risk Screening API to initiate fraud screening.

The API request includes the session ID (from the device data collection) and transaction data fields.

Step 3: Evaluation process

PXP performs the following checks before proceeding:

  • Confirms your 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.

Step 4: Decisioning

The provider returns a risk decision.

Based on the outcome, you decide whether to:

  • Proceed with authorisation: You call the PXP Transactions API.
  • Abort the transaction: The authorisation request isn't triggered.

Step 5: Feedback loop

A feedback call is made to the provider to update the transaction outcome data.

Post-authorisation

Step 1: Session initialisation

A session ID is generated and device data is collected.

Step 2: Transaction initiation

The customer enters their payment details and initiates the transaction.

Step 3: Authorisation request

You send an authorisation request to PXP using the standard Transactions API.

Step 4: Authorisation outcome

If the transaction is declined by the issuer, the flow ends PXP returns a Refused status to you. No further action is taken.

If the transaction is authorised, you proceed with risk screening.

Step 5: Risk screening request

You call the PXP Standalone Risk Screening API to initiate post-authorisation fraud screening.

The API request includes the session ID (from the device data collection) and relevant transaction data fields.

Step 6: Evaluation process

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.

Step 7: Decisioning

The third-party provider returns a risk decision.

Based on the outcome, you decide whether to:

  • Proceed with authorisation: You call PXP's Capture API.
  • Reject the transaction: You call PXP's Cancel or Void API.

Step 8: Feedback loop

A feedback call is made to the third-party provider to update the transaction outcome data.