Skip to content

Fast-Track Adoption

End-Customer Cross-Border Payments (from FX Wallets)

gs-usecase
Use Case Snapshot

This path activates end-customer cross-border payments from FX wallets.
It enables a platform to allow end customers to send cross-border payments directly from FX wallet balances, using FX360 as the underlying payment and settlement infrastructure.
This path is designed as a deterministic entry point for launching customer-facing international payments with minimal scope and no payment orchestration decisions.

 

Prerequisites

This path can be started only if all of the following conditions are met:

  • The platform operates as B2B2X, serving end customers and owning the customer experience.
  • The platform supports or will activate FX wallets for end customers, either existing or provided as part of Stage 1.
  • The platform is legally permitted to enable outgoing cross-border payments for end customers in at least one jurisdiction.
  • The platform is able to perform end-customer identification as required for payment execution.
  • The platform supports API-based integration. No UI design or payment routing configuration is required in Stage 1.
gs-symbol If any prerequisite is not met, this path should not be started.

Stage 1 – Fast-Track Scope

Included in Stage 1

Stage 1 activates a single, opinionated cross-border payment flow:

  • Outgoing payments only
  • One source currency
  • One destination currency
  • One payment rail
  • Funds sourced from an FX wallet balance
  • Payment execution and settlement handled by FX360
  • Platform-controlled initiation with no end-customer routing choices
gs-symbol Stage 1 establishes a live international payment capability with deterministic behavior.

Explicitly Excluded from Stage 1

The following are not included in Stage 1:

  • Incoming payments
  • Multiple payment rails or routing logic
  • Batch or bulk payments
  • FX protection or hedging
  • Risk analytics or dashboards
  • Payment optimization or pricing configuration
  • UI customization or workflow design
gs-symbol These exclusions exist to prevent operational complexity and decision dependency.

Time to Live

Expected time to Stage 1

live: 2–4 weeks

This estimate assumes:

  • All prerequisites are met
  • A single payment rail is selected
  • No deviation from the Stage 1 scope

Fast-Track Steps

Each step represents a progress gate, not a task list.

solar_wallet-outline

Prepare

Prepare FX wallet balances for payment sourcing.

gs-connect

Connect

Connect the platform to the FX360 payments API.

gs-execute

Execute

Execute outgoing payment flows in a non-production environment.

gs-validate

Validate

Validate settlement behavior and confirmation handling.

gs-go-live

Go Live

Enable cross-border payments for live customer wallets.

Validation Check

Stage 1 is complete when:

  • An end-customer FX wallet contains fundsStage 1 completion is binary: complete or incomplete.
  • An outgoing cross-border payment is initiated
  • FX360 executes and settles the payment
  • Settlement confirmation is received
  • No manual intervention is required
gs-symbol Stage 1 completion is binary: complete or incomplete.

What Comes Next

After Stage 1, the platform may expand to:

  • Incoming cross-border payments
  • Additional payment rails
  • FX protection and risk layers
  • Batch and bulk payment support
  • Monetization and pricing strategies
  • Full FX and payments stack activation
gs-symbol Expansion is optional and occurs outside the Fast-Track scope.