Availability and integration
The implementation provides TRON USDT partner REST mechanics. Availability depends on the enabled deployment, custody signer, deposit scanner, workers and funded network sponsorship. A published OpenAPI path, a test-key response or basic TRON readiness does not prove that a complete escrow can settle. Ask Rach for the enabled base URL, deployed version and observed deposit, release and refund transaction evidence. There is no escrow SDK or hosted widget in the current delivery. The partner can build its own screens and call Rach from its backend. Both participants need provisioned and tenant-linked TRON wallets. Test-key simulations are stateless and do not replace a settlement rehearsal. The separate Rach P2P trading interface is not the partner API; its features or operating policies cannot be assumed to apply here.Custody and responsibilities
Before contracting, obtain written answers covering:- The contracting entity, registration, operating jurisdictions and applicable authorization for the proposed activity.
- The legal custodian and technical signing arrangement, key/IAM operators, approval controls, recovery arrangements and fund-segregation terms.
- Who may authorize ordinary release/refund, who decides disputes and who executes decisions. Holding no keys does not remove the partner’s API authorization role.
- Customer terms, disclosures, consent records, data processing, retention, complaints, incident response and any applicable reporting duties.
KYC/KYB, AML and sanctions
Agree compliance services and responsibilities explicitly. Wallet provisioning, phone validation and wallet membership are not KYC. Existing account suspension or freeze controls are not a substitute for participant screening and ongoing monitoring. Agree a responsibility matrix for partner KYB, consumer KYC, beneficial ownership, sanctions/AML screening, transaction monitoring, escalation, reporting and records. Specify the partner’s continuing risk, consent, disclosure and customer-support duties. Rach must confirm whether and under what terms the partner can integrate without becoming the custody or escrow operator; the API reference cannot make that determination.Permitted use and countries
No supported/restricted-country list for consumer goods/services escrow is established by this release. CIS, EU, LATAM and Southeast Asia are not blanket approvals. Provide individual launch countries, participant locations and goods/services categories. Obtain an explicit answer for each, including prohibited categories, amount limits and any residency or business restrictions, before onboarding customers.Disputes, evidence and appeals
The technical interface records a dispute reason and permits authorized Rach staff to choose full release or full refund. It does not deliver a complete managed dispute service. Agree the following before pilot funding:- How parties submit evidence, what evidence is accepted, deadlines and retention.
- Who owns each case, the decision standard and authority, and how conflicts are handled.
- Whether an appeal is available, its deadline and decision maker, and how this relates to an irreversible completed payout.
- Acknowledgment and resolution targets, operating hours, escalation and notification.
Charges to agree in writing
Published EVM transfer pricing is not an escrow quote. Network sponsorship does not
mean the overall service is free, and the API moving the full principal does not
establish how commercial charges will be invoiced.
Proposed onboarding and 10–20-deal pilot
This is a planning checklist, not an approved KYB document list or a promise of acceptance.- Share business/entity and ownership details, operating jurisdictions, launch countries, customer onboarding/risk flow, goods/services categories, expected amounts/volumes, and technical/support contacts. Rach must provide the formal KYB requirements.
- Agree entity/custody terms, compliance allocation, permitted use/countries, dispute process, charges, participant eligibility and per-deal/aggregate exposure caps.
- Obtain credentials and a confirmed environment; provision/link both wallets, implement state polling and signed webhook verification, and exercise synthetic UI/error states.
- Validate settlement/dispute ordering, deposit recovery, custody, scanning, sponsor capacity, outbox, worker/reconciler health, correct gateway routes and recovery.
- Rehearse failures on isolated infrastructure, then conduct the agreed small pilot with named operations and dispute owners. Reconcile every deposit and payout to chain evidence.