Compliance
Attach evidence, manage review states, and operate corridor-specific controls.
Compliance requirements vary by corridor, destination type, transaction amount, and counterparty risk profile.
Counterparty evidence
Collect and attach the minimum required evidence before creating live transactions.
| Evidence | Typical use |
|---|---|
| Business registration | KYB verification for merchants and platforms |
| Identity document | KYC verification for individuals |
| Proof of address | Enhanced review and local rail requirements |
| Source of funds | High-value or elevated-risk transactions |
Review outcomes
| Outcome | Integration behavior |
|---|---|
approved | Continue the transaction. |
needs_information | Pause and collect requested evidence. |
rejected | Do not retry without correcting the underlying issue. |
escalated | Wait for manual review or contact your M2Square account team. |
Sentra workflow
Sentra gives operations teams a queue for review, escalation, notes, and audit evidence. API events and Sentra actions share the same transaction timeline.