Compliance Rules

Compliance Verification

To ensure that all operations within our platform comply with legal and regulatory requirements, transactions go through a set of validations. These checks can occur before or after the transaction, depending on the nature of the verification.

Before transaction

Before a transaction is processed, we run automated checks through our internal bureau and external data providers.

These validations include:

• Document Verification – Confirms that the document is valid, the individual is of legal age, and the person is alive.
• PEP Screening – Checks if the individual is a Politically Exposed Person.
• Sanctions Screening – Verifies if the individual appears on sanctions lists related to terrorism, money laundering, corruption, and other illicit activities.
• Government Benefit Check – Identifies whether the individual receives governmental benefits.

Outcome handling:

• Age Verification Failure – Transaction is immediately blocked.
• Sanctions Match – Transaction is immediately blocked.
• PEP Match – The transaction is allowed, but our Compliance team may initiate a targeted investigation.

In our transaction object, you will be able to identify the compliance error:

"error": {
  "type": "ERROR_COMPLIANCE",
  "code": 1,
  "message": "CPF is not regular.",
  "meta": {
    "risk": {
      "transaction_risk": "LOW",
      "transaction_acumulated_risk": "PROCESSING",
      "customer_risk": "PROCESSING",
      "evaluation": "PROCESSING",
      "block": true,
      "reason": "CPF is not regular."
    },
    "customer": {
      "document": "123",
      "name": "Aziul Otaffum",
      "email": "[email protected]",
      "phone": null,
      "revalidated_at": "2025-07-22T13:24:09.452160+00:00",
      "birth_date": null,
      "mothers_name": null,
      "document_status": "UNKNOWN",
      "id": "123-456-789",
      "created_at": "2025-07-22T13:14:37.037702+00:00",
      "risk_ratio": 0,
      "risk_status": "NONE",
      "blocked_date": null,
      "blocked_reason": null,
      "is_pep": false,
      "is_sanctioned": false,
      "is_sanctioned_unblocked": null
    }
  }

After transaction

Some validations occur after the transaction request is received.

For example:

• Third-Party Deposits – If a transaction is funded by a third party, we:

  1. Return the funds to the original payer’s account.
  2. Mark the transaction as failed in our system.
  3. Send a failure webhook to the merchant for operational awareness.

In our transaction object, you will be able to identify the compliance error:

"error": {
  "type": "ERROR_COMPLIANCE",
  "code": 1,
  "message": "Third party payments are not allowed",
  "meta": []
}

Flexible Compliance Models

In markets where certain validations are not mandatory, we offer the flexibility to disable specific bureau checks. Our Compliance team will work with you to determine the model that best fits your operational needs while ensuring regulatory safety.