Participant Calls Remi
The participant sends customer, beneficiary, quote, transfer, funding and webhook requests through Remi's inbound API.
Remi is an infrastructure layer, network and API platform, not a standalone app. This page shows how different participants can build distinct money movement use cases on the same regulated infrastructure, using Remi for routing, compliance orchestration, liquidity, settlement tracking, webhooks and reconciliation.
A Remi use case is not defined by one fixed user journey. It is configured by combining participant type, corridor, funding method, payout method, operator route, compliance requirements and reporting needs.
The participant sends customer, beneficiary, quote, transfer, funding and webhook requests through Remi's inbound API.
Remi validates, prices, screens, routes, meters, logs and tracks the full transaction lifecycle.
Banks, exchange houses, MTOs and custodians execute the selected route, then provide payout, settlement or confirmation evidence.
A remittance application can launch UAE to Egypt transfers without integrating every bank, exchange house, payout rail and compliance workflow directly.
A payroll or freelancer platform can distribute wages or contractor payments across corridors through one API surface.
A B2B payment provider can move business payments with clearer references, status tracking and settlement evidence.
A regulated exchange house can use Remi in two roles: as an operator providing payout capacity and as a participant originating its own transactions.
A regulated digital asset platform can support stablecoin-funded off-ramp flows where jurisdiction and licensing allow.
A platform can embed cross-border payout or wallet functionality into a broader product without becoming a full corridor operator.
Participants retrieve corridor availability, supported currencies, payout methods, FX rate, fees, spread, quote expiry, constraints and expected service level.
KYC status, sanctions screening, transaction monitoring, velocity controls, limits, review states, rejection reasons and audit trails are normalized into consistent lifecycle states.
Remi selects the route, submits to the operator path, captures settlement or payout confirmation and exposes transaction status through retrieval APIs and signed webhooks.
Every transaction can be linked to fee components, FX, settlement reference, operator reference, payout confirmation, API usage and exportable reports.