Menu

Developer Resources

ChargePaymentFraudRequest

Conditional.

Use the ChargePaymentFraudRequest API to connect to our Payment Protect product. This API will support both preauthorization and postauthorization implementations based on whether you include authorization result parameters.

ChargePaymentFraudRequest evaluates the risk associated with a transaction and responds with a risk score plus up to five insights into that score when you are enrolled in Payment Protect.

Note: This API may also be used for a single-step Payment Guarantee integration in postauthorization (authorization result parameters are required for this case).

Use the ChargePaymentFraudRequest API if you have already authorized the transaction with your gateway/acquirer and received the authorization results. Otherwise, use the ChargePaymentRequest API.

ChargePaymentFraudRequest determines the risk associated with the transaction and checks if it can be guaranteed before deciding to settle or cancel the transaction.

Note: This API acts as a combination of the ChargePaymentRequest and AuthResult APIs. Authorization results from your gateway/acquirer must be provided to use this API.

 

Request Parameters

Expand/Collapse All

Use the following request parameters when integrating to ChargePaymentFraudRequest:

Response Parameters

ChargePaymentFraudRequest returns the following response parameters:

Response Codes

Each API call returns a numeric response code. If the response code is zero, the API transaction completed successfully without errors; however, the status of the transaction may not be complete. If the response code is non-zero, an error message is included with the response code.

Note: When non-zero response codes are returned, the response fields might not be returned correctly. Review the error messages associated with non-zero response codes and take appropriate steps to resolve the error conditions. Most of the non-zero response codes indicate a system configuration or integration issue. Before production deployment, you should resolve these issues during the testing phase.