How to ensure the closed loop?
When sending or receiving transactions, one might ask oneself how Trio manages to offer a fully secure closed loop, without any hiccuping or missing transactions, whilst also providing protection against frauds.
For this sort of control, we offer plentiful parameterization aligned with compliance rules when making any movement, so you know exactly what happened throughout your operation.
Deposits
Regarding money coming in, we apply some compliance rules that decide whether money from a single transaction will be received or not.
Whenever a compliance rule is being infringed in a transaction, we take it upon ourselves to receive the money and automatically refuse it back to the sender's account. A refused transaction will generate a failed event, so you can handle the experience and show the information to your users.
Here you can see the pay-in related compliance rules that can be enabled for a virtual account:
Unidentified deposits
Yes
When a payment is done via the bank account directly or via the bank account's pix key, we block the payment so you can know exactly who the money came from.
Deposits from duplicated QR code payments
Yes
When a payment is done twice to the same QR Code, we block the payment, so each payment can be received separately in order to avoid confusion.
Deposits with value different from dynamic QR code
Yes
When a payment is done with an amount different from the initially stated in the QR Code. Useful for controlling the exact amount of transactions, and avoiding the need to create two QR Codes for the same transaction. We tend to recommend clients to always leave this parameter on.
Deposits with tax number different from dynamic QR code
Yes
When a payment is done by an individual with a tax number different from the tax number initially set in the QR Code creation.
Deposits with bank accounts different from dynamic QR code
Yes
When a payment is done by a bank account different from the bank accounts initially set in the QR Code creation.
Deposits from legal entities
Yes
When a payment is not done by an individual with a natural person tax number (CPF in Brazil), but from a legal entity with a legal tax number (CNPJ in Brazil).
Deposits from unauthorized participants
Yes
When payment is done by an institution that is not authorized by the Central Bank of Brazil
A complete guide of implementation can be found here: Pay-in using a QR Code.
Payout
Regarding money going out, we also apply some compliance rules and control cash out processes that decide whether a payment will be transferred, only as a form of protecting our client base.
Here you can see the payout related compliance rules that are enabled for a virtual account:
Block payouts to legal entities
Yes
When attempting to make a payment to an account that belongs to a legal entity represented by a legal tax number (CNPJ in Brasil).
Block payouts to different tax number
Yes
When attempting to pay out an account that not belongs to the tax number informed on the payload field: reference_tax_number
Block payouts to different bank accounts
Yes
When attempting to pay out an account that not informed on the payload field: reference_bank_accounts
A complete guide of implementation can be found here: Payout using a pix key.
Last updated
Was this helpful?