The settlement sequence
Onboard and verify
Before any funds move, every client must be verified through our KYC (individual) or KYB (business) process. Pythas cannot initiate or receive transfers on behalf of a client whose verification is not approved.
Register bank account and wallet
Once verified, the client registers the instruments that will be used as the source or destination of a transfer. A bank account is required for fiat legs. A Fireblocks-managed wallet address is assigned by Pythas for the stablecoin leg.
Key concepts
| Concept | Description |
|---|---|
| Customer | An individual or business on whose behalf transfers are executed. Must be KYC/KYB verified before any transaction. |
| Bank account | A fiat bank account registered to the customer for sending or receiving USD, EUR, BRL, or MXN. |
| Wallet | A blockchain wallet address assigned to the customer for sending or receiving USDC or USDT. |
| Transfer | A single money movement event between a bank account and a wallet — on-ramp or off-ramp. |
What Pythas handles for you
Identity verification
KYC and KYB orchestration via MetaMap — individuals and businesses.
Compliance screening
OFAC, sanctions, PEP checks, and blockchain KYT via Elliptic on every transaction.
Fiat-stablecoin conversion
All conversions executed by our regulated OTC Liquidity Provider. Pythas bears no FX risk.
Custodial infrastructure
Client-dedicated wallets via Fireblocks. No private key handling required by the client.
Settlement and payout
Via regulated banking partners and Local Rail Partner across USD, BRL, MXN, and EUR.
Fund segregation
Client funds never commingled with Pythas operating capital at any point.
Regulatory reporting
SAR and CTR filing obligations under BSA / FinCEN handled by Pythas compliance team.
Full audit trail
Every transaction is traceable and available upon regulatory request.