Skip to main content

​
What is CPF Mismatch?

CPF Mismatch is a feature that rejects transactions when the CPF of the user’s making a deposit or receiving a prize does not match the CPF of the account holder. This measure ensures that only the authorized holder can make payments and withdrawals, preventing fraud and ensuring compliance with local regulations, such as Ordinance 1330 of 26/10/2023, which prohibits third-party deposits in bettors’ accounts.

​
How does it work?

​
Payin (Deposits)

When receiving a payment via a WE QR Code, the system checks whether the payer’s CPF matches the CPF associated with the original request. If the information does not match, the transaction is rejected and the merchant receives a notification with the error code RESTRICTION_PAYER_DIVERGENCE.
Optional Feature: This functionality is configurable. It is required for specific segments—such as betting—but if you want it enabled for your business, please let us know.

​
Payout (Withdrawals)

This validation also applies to the withdrawal (payout) flow. Before completing the payment to the beneficiary, the system verifies whether the CPF matches the registered account holder. If it does not, the transaction is canceled with the reason BENEFICIARY_DIVERGENT.
Default Feature: This is a default functionality and does not require any configuration.
These controls ensure that only the legitimate account owner can perform financial transactions, increasing security for both the operator and the end user.

​
Key Benefits

Fraud Prevention

Prevents unauthorized transactions by verifying CPF ownership

Regulatory Compliance

Complies with Ordinance 1330 of 26/10/2023

Real-time Validation

Instant verification before transaction completion

Customer Protection

Protects both operators and end customers

​
Transaction Flow

​
Deposits (QR Code Payments)

1

QR Code Generation

WEPayments generates a QR code for the payment request
2

User Scans QR Code

User scans the QR code to make the payment
3

CPF Verification

System checks if payer’s CPF matches the registered account holder’s CPF
4

Transaction Result

If CPF matches: Payment is processed If CPF doesn’t match: Transaction is rejected with error code

​
Withdrawals (Payouts)

1

Withdrawal Request

User requests a withdrawal to their registered account
2

CPF Verification

System verifies if the beneficiary’s CPF matches the registered holder
3

Transaction Result

If CPF matches: Payment is completed If CPF doesn’t match: Transaction is canceled

​
Error Codes

Error CodeTypeDescription
RESTRICTION_PAYER_DIVERGENCEDepositThe payer’s CPF does not match the account holder’s CPF
BENEFICIARY_DIVERGENTWithdrawalThe beneficiary’s CPF does not match the registered holder’s CPF

​
Use Cases

Ensures compliance with regulations that prohibit third-party deposits in bettors’ accounts, as mandated by Ordinance 1330.
Prevents money laundering and fraud by ensuring only the account owner can perform transactions.
Protects merchants and customers by verifying the identity of the person making payments or receiving refunds.
Ensures sellers receive payments only to their registered accounts, preventing fraud.

​
Best Practices

User Registration: Ensure users register their correct CPF during account creation to avoid transaction rejections.
Third-Party Payments: Transactions from third-party accounts will be automatically rejected to comply with regulations.
Error Handling: Implement proper error handling in your application to inform users when a CPF mismatch occurs.

​
Regulatory Compliance

This feature helps you comply with:
  • Ordinance 1330 of 26/10/2023: Prohibits third-party deposits in bettors’ accounts
  • Anti-Money Laundering (AML) regulations
  • Know Your Customer (KYC) requirements

KYC Verification

Know Your Customer verification

Create Charge

Create payment charges

Create Payment

Create payout payments