Secure Transaction Processing

When sending or receiving transactions, one might wonder how Aurixpay manages to offer a fully secure closed-loop system without any hiccups or missing transactions, while also providing robust fraud protection.

For this level of control, we offer extensive parameterization aligned with compliance rules for every transaction, ensuring full transparency throughout your operations.

Deposits (Inbound Payments) For incoming funds, we apply compliance rules that determine whether a transaction will be accepted or not.

Whenever a transaction violates compliance rules, Aurixpay automatically receives the funds and immediately returns them to the sender's account. A rejected transaction generates a failed event notification, allowing you to manage the user experience and communicate appropriately with your customers.

Here are the deposit-related compliance rules available for virtual accounts:

Compliance Rule	Editable?	Possible Scenario
Unidentified deposits	Yes	Blocks payments made directly via bank account or PIX key to ensure sender identification.
Duplicate QR code payments	Yes	Prevents multiple payments to the same QR code, ensuring each payment is processed separately.
Amount mismatch in dynamic QR codes	Yes	Rejects payments with amounts differing from the QR code specification. We recommend keeping this parameter always enabled.
Tax ID (CPF) mismatch in dynamic QR codes	Yes	Blocks payments from CPFs not registered during QR code creation.
Bank account mismatch in dynamic QR codesisted in the QR code.	Yes	Rejects payments from bank accounts not whitel
Corporate entity (CNPJ) deposits	Yes	Flags payments originating from legal entities rather than individuals.
Unauthorized institution deposits	Yes	Blocks payments from financial institutions not authorized by the Central Bank of Brazil.

Complete implementation guide: Pay-ins via QR Code.

Payouts (Outbound Transfers) For outgoing transfers, we enforce compliance rules to protect our client base:

Compliance Rule	Editable?	Possible Scenario
Corporate payee blocking	Yes	Prevents transfers to CNPJ (corporate) accounts.
Tax ID (CPF) mismatch blocking	Yes	Rejects transfers to CPFs not matching the reference_tax_number field.
Bank account mismatch blocking	Yes	Blocks transfers to accounts not listed in reference_bank_accounts.

Complete guide: Payouts via PIX Key.

---