Stablecoin Payments
A clear cross-border payment journey, under your institution's brand.
A bank, MFI, payment company, telco or corporate partner presents the payment experience to its own customers. CuduEx provides the underlying orchestration for the approved settlement workflow; the partner retains the customer relationship and service decisions.
Your brand
Customers move through your institution's experience.
Your relationship
The partner owns the customer service and product decisions.
Our orchestration
CuduEx coordinates the underlying configured workflow.
Explore two distinct cross-border journeys.
Sample consumer remittance and business invoice workflows, shown separately. These simulations do not move funds or represent available services.
Personal remittance
Preview a sample sender amount, recipient payout choice and illustrative local-currency outcome.
B2B cross-border payment
Review a fictional supplier invoice, illustrative fee and mock approval state.
What the customer experiences, step by step.
This is the end-customer path within a partner-branded service. Each stage distinguishes the experience the customer sees from the checks and coordination operating underneath.
- 01
Start a payment
Customer sees
The customer opens the partner-branded payment flow and enters the payment purpose and amount.
Underneath
The partner's configured product rules identify which payment journeys may proceed.
- 02
Choose beneficiary, corridor and funding source
Customer sees
The customer selects the beneficiary, receiving market and available funding source in the partner experience.
Underneath
Beneficiary, corridor and funding options follow the partner's approved scope and available rails.
- 03
Review the quote and disclosures
Customer sees
Before confirmation, the customer sees the applicable payment details, fees and required disclosures.
Underneath
CuduEx coordinates the quote and settlement inputs while the partner determines the customer-facing terms and disclosures.
- 04
Complete required checks
Customer sees
If needed, the customer is asked to complete KYC information or an additional security step.
Underneath
Configured identity, transaction and policy checkpoints are applied before an instruction is progressed.
- 05
Authorise the transfer
Customer sees
The customer reviews the final instruction and authorises it through the partner's chosen approval method.
Underneath
Authorisation requirements and exception handling remain defined by the partner's operating model.
- 06
Receive status and proof of payment
Customer sees
The partner experience shows submitted, pending, completed or exception status, with a payment record where available.
Underneath
CuduEx coordinates status updates across the configured payment and settlement handoffs.
- 07
Track settlement or an exception
Customer sees
The customer can follow the payment outcome through the partner's support and status experience.
Underneath
Settlement events, operational exceptions and required follow-up are routed through the agreed partner workflow.
The experience is partner-led. The workflow is orchestrated underneath.
What the partner controls
- The customer relationship, brand and customer support experience.
- Eligible corridors, funding options, pricing presentation and disclosures.
- KYC ownership, authorisation policy and exception communications.
What CuduEx orchestrates
- Payment instruction and settlement workflow coordination.
- Configured transaction-control and operational status handoffs.
- A consistent integration layer across approved rails and counterparties.
Built for the operating model behind the journey.
Settlement orchestration
Coordinate payment, stablecoin settlement and payout steps in one agreed workflow.
Control workflow
Apply configured checkpoints around disclosures, review and transaction handling.
Partner-led delivery
Keep the payment journey in the institution's own brand and operating model.
Partner-led governance
The institution retains its customer relationship, service rules and KYC responsibilities.
A clearer customer proposition with institutional control.
- A customer-facing payment flow that remains partner-led.
- Operational visibility across payment and settlement handoffs.
- A starting point for scoped corridor and product discussions.
- 01
Define the eligible payment use case, counterparties and partner support model.
- 02
Agree customer disclosures, review steps and exception handling before implementation.
- 03
Validate market, liquidity, regulatory and partner conditions for each scope.
Connect the rest of the stack.
Services can be scoped together as product, market and partner conditions allow.
Custody
A controlled custody journey for approved customer asset activity and oversight.
See on the Platform pageBrokerage / On-Off Ramp
A controlled buy, sell and settlement journey for an approved customer base.
See on the Platform pageTokenization
A structured workflow for eligible real-world asset programmes, subject to jurisdiction and legal requirements.
See on the Platform pageYield
A disclosure-led allocation and redemption journey for approved yield products.
No lending of client assets, no rehypothecation
See on the Platform pageDiscuss the right customer journey and service scope for your institution.
Regulatory status
No company in the CuduEx Ltd group currently holds a licence to carry on virtual asset business in any jurisdiction.
The services described on this website reflect the offering the group intends to provide once the necessary authorisations have been granted. No regulated service is provided before authorisation.