Analyzing a transaction at ACI Worldwide

post

https://risksandbox.braspag.com.br/analysis/v2/

Analyzes the fraud risk of a transaction with the ACI Worldwide provider.

Environment	Method	Endpoint
Sandbox	d> p	`https://risksandbox.braspag.com.br/analysis/v2/`
Production	ion td> d>	`https://risk.braspag.com.br/analysis/v2/`

ℹ️
Learn more about this feature in the documentation.

ℹ️
Important
When your antifraud provider is ACI Worldwide, send the value "RedShield" in the Provider field.

ℹ️
Alphanumeric CNPJs will be implemented by the Brazilian Federal Revenue Service in July 2026
This change applies only to new registrations. There will be no changes to existing CNPJs.
The alphanumeric CNPJ is already supported by Cielo, with no changes required to your integration.
We recommend checking whether adjustments are needed in your merchant’s own checkout systems.

⚠️
Warning
This call is used only for integrations that consume fraud analysis in a standalone manner.
If you use Antifraude integrated with the Gateway de Pagamento, this reference does not apply. See the specific documentation for the product used:

Antifraude integrated with the Gateway de Pagamento.

Body Params

MerchantOrderId

string

required

Order number.

TotalOrderAmount

int64

required

Total order amount in cents.
Example: 123456 = R$ 1.234,56

TransactionAmount

int64

required

Financial transaction amount in cents.
Example: 150000 = R$ 1.500,00

Currency

string

enum

Currency. More information in ISO 4217 Currency Codes

Allowed:

Provider

string

enum

Anti-fraud solution provider.
Table 1 - Provider

Allowed:

OrderDate

date

Order date
Eg: 2016-12-09 19:16:38.155
Note: If not informed, a date will be generated by Braspag

BraspagTransactionId

string

Transaction ID on Braspag Pagador.

Tid

string

Id of the transaction at the acquirer
Note: If you do not have an integration with Pagador Braspag, you will not be able to send the BraspagTransactionId field, so it is necessary to send the fields Nsu, AuthorizationCode and SaleDate , in addition to this one.

Nsu

string

Unique sequential number of the transaction in the acquirer
Note: If you do not have an integration with Pagador Braspag, you will not be able to send the BraspagTransactionId field, so it is necessary to send the fields Tid, AuthorizationCode and SaleDate, other than this one in question

AuthorizationCode

string

Acquirer transaction authorization code
Note: If you do not have integration with Pagador Braspag, you will not be able to send the BraspagTransactionId field, so it is necessary to send the fields Tid, Nsu and SaleDate, other than this one.

SaleDate

date

Date of authorization of the transaction at the acquirer
Note: If you do not have an integration with Pagador Braspag, you will not be able to send the BraspagTransactionId field, so it is necessary to send the fields Tid, Nsu and AuthorizationCode, besides this one.

SplitingPaymentMethod

string

enum

Identifies whether the transaction is authorized with one or more cards or with more than one payment method.
Table 2 - SplitingPaymentMethod

Allowed:

IsRetryTransaction

boolean

Retry of an analysis, must be sent with a value equal to TRUE when the return code in the first attempt is equal to BP900.

Card

object

Billing

object

Shipping

object

Customer

object

CartItem

object

Airline

object

CustomConfiguration

object

MerchantDefinedData

object

Headers

Authorization

string

required

Bearer {access_token}

MerchantId

string

required

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

RequestId

string

required

nnnnnnnn-nnnn-nnnn-nnnn-nnnnnnnnnnnn

Response

Important

Alphanumeric CNPJs will be implemented by the Brazilian Federal Revenue Service in July 2026

Warning

200200