Service journeys

Partner-branded payment journey

Stablecoin PaymentsA 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. Havenex provides the underlying orchestration for the approved settlement workflow; the partner retains the customer relationship and service decisions.

Customer journey

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.

  1. 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.

  2. 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.

  3. 03

    Review the quote and disclosures

    Customer sees

    Before confirmation, the customer sees the applicable payment details, fees and required disclosures.

    Underneath

    Havenex coordinates the quote and settlement inputs while the partner determines the customer-facing terms and disclosures.

  4. 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.

  5. 05

    Authorize the transfer

    Customer sees

    The customer reviews the final instruction and authorizes it through the partner’s chosen approval method.

    Underneath

    Authorization requirements and exception handling remain defined by the partner’s operating model.

  6. 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

    Havenex coordinates status updates across the configured payment and settlement handoffs.

  7. 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.

Clear operating roles

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, authorization policy and exception communications.

What Havenex orchestrates

  • Payment instruction and settlement workflow coordination.
  • Configured transaction-control and operational status handoffs.
  • A consistent integration layer across approved rails and counterparties.

Capabilities and controls

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.

Partner outcomes

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.

Implementation considerations

  • 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.

Institutional discussion

Discuss the right customer journey and service scope for your institution.

Request a partner briefing

Licensing is in progress. Havenex Africa’s Botswana VASP application has been filed, and Rwanda follows its implementing regulations. No licence has been granted to any Havenex Africa entity.