Tradeics Pay simplifies B2B payments for buyers and suppliers with flexible rails and visibility across every transaction.
Payment methods
Integrations should assume method diversity:
- Cards
- Bank transfers
- Local payment gateways
- In-platform wallets
Your middleware should treat method as metadata on a payment attempt, not as separate business processes, so finance posting stays consistent.
Product capabilities that matter to developers
| Capability | Meaning for integrations |
|---|---|
| Unified documentation surface | One place for payment and connection contracts as APIs ship |
| Smart synchronization | Keep connected platforms aligned on balances, statuses, and invoices |
| Advanced permissions | Grant conditional access to connected platforms by business need |
Design guidance
- Capture
payment_id,method,currency,amount,status, and timestamps on your side. - Never store full card PANs or sensitive gateway secrets in your application database — use the PSP / Tradeics tokenization model.
- Map payment status to ERP postings only on terminal states (
succeeded,failed,cancelled,refunded) to avoid duplicate books. - When permissions are scoped per connected platform, fail closed if a token lacks entitlement for a payout or refund action.