Learn about the standalone risk screening flows.
The transaction risk screening service is available as a standalone API, allowing you to use Kount's advanced fraud prevention capabilities without integrating with PXP's payment processing workflow. In this mode, the risk assessment operates independently, giving you complete control over how and when the service is invoked.
In this decoupled setup, PXP provides a dedicated API that you can call directly whenever you want to perform a risk evaluation. Since it operates separately from the payment authorisation process, you decide:
- Whether a transaction qualifies for risk screening.
- When to trigger the risk screening (e.g., before authorisation or after authorisation).
- How to use the returned risk score and recommendation to guide business decisions.
- Whether to proceed with or block a transaction before sending the authorisation request to the payment processor.
This gives you full flexibility to embed fraud screening in the exact stage of your workflow where it provides the most value.
- Independent from payment gateway: The service works as a standalone fraud prevention layer. You can adopt it even if you use multiple processors or don't use PXP's payment gateway at all.
- Merchant-controlled decisioning flow: By calling the standalone API, you can perform a risk assessment upfront and decide, based on rules and risk thresholds, whether to continue with an authorisation request or stop the flow entirely.
- Ideal for multi-workflow environments: Perfect for marketplaces, platforms, and large enterprises that handle diverse payment journeys and require a centralised fraud decisioning system that isn't tied to a single payment provider.
In the pre-authorisation flow, the transaction is evaluated for fraud before the payment authorisation request is initiated. You collect device and transaction data, then call the provider's Risk screening API. If the transaction is deemed low-risk, you proceed with payment authorisation. Otherwise, the transaction is blocked before it reaches the issuer.
Key benefits:
- Prevents high-risk transactions from being authorised.
- Saves processing and chargeback costs.
- Reduces fraud at the entry point.
A session ID is generated and device data is collected.
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.
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.
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.
A feedback call is made to the provider to update the transaction outcome data.
In the post-authorisation flow, the risk screening takes place after the payment has been authorised by the issuer. Once approved, you trigger the Risk screening API. Based on the risk outcome, the transaction can either be captured or voided.
Key benefits:
- Useful when immediate authorisation is required.
- Adds a fraud check layer before final settlement.
- Allows you to reverse transactions that are deemed risky.
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 PXP returns a Refused status to you. No further action is taken.
If the transaction is authorised, you proceed with risk screening.
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.
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 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.
A feedback call is made to the third-party provider to update the transaction outcome data.