PAYMENTS ON SOLANA

Payments with a route
you can control.

MultiHopper adds programmable asset routing to payment applications on Solana. Configure the path and timing of a transfer, review the quote, then track delivery in your own product.

Discuss your integration ↗Read the implementation guide

ILLUSTRATIVE WORKFLOW

Approved supplier invoice
Quoted route + wallet approval
Payment status + invoice record

Your application owns the business process. MultiHopper supplies the routing step.

THE ROLE OF ROUTING

How does MultiHopper fit into a payment flow?

For payment platforms, wallets and applications that need configurable transfers between onchain accounts. Use a supported stablecoin or other supported asset, subject to the token and cluster capabilities in the current API.

A PRACTICAL EXAMPLE

An approved invoice becomes a tracked payment.

Imagine a marketplace paying a supplier from its operating wallet. Its application already owns the invoice, approval and recipient records. MultiHopper handles the quoted routing step between the funded source and the supplier’s wallet. This is an illustrative integration, not a claim about a deployed customer.

Define the payment

Confirm the supplier’s wallet, token mint, amount and intended delivery window. Associate the transfer with your invoice reference so reconciliation does not depend on matching amounts alone.

Review and authorize

Get a current estimate and create a transfer quote. Review the recipient’s net amount and required funding, then prepare and sign the returned transactions using your application’s wallet policy.

Reconcile delivery

Track the transfer status and record the resulting transaction references. Update the invoice only after the required completion evidence is available; keep failed or pending attempts visible to your operations team.

Implementation reference: Create-transfer reference.

IN YOUR PRODUCT

Where it fits.

Payment routing

Configure asset movement as a step in your existing checkout, marketplace or settlement system.

Product integration

Keep customer approvals, invoices and support records in your application while using the transfer API.

Multiple payees

For a payout run, evaluate Multi-Send rather than assuming one single-recipient transfer can pay an entire list.

LIMITS AND RESPONSIBILITIES

Define the boundaries before you build.

Onchain settlement

This workflow describes wallet-to-wallet asset movement. Bank payouts, currency conversion, merchant acquiring and chargebacks need separate services where your product requires them.

Supported assets

Confirm the token and deployed cluster before offering it to customers. A token symbol alone is not enough to identify the correct mint.

Timing and fees

Treat the arrival window as a routing parameter. Budget for network conditions, execution dependencies and the live quoted costs rather than promising a fixed delivery time or universal fee.

Routing does not erase onchain history or guarantee anonymity. Smart-contract and execution risks remain. Review the security model and current audit status before selecting the value and scope of an integration.

CLEAR ANSWERS

Questions about payments.

Can I use this for stablecoin payments?

Use the relevant token mint only where the selected deployment supports it. Test the full funding and settlement flow before enabling it for customers.

How do I avoid creating duplicate payments?

Use the documented externalId and idempotency behavior, and retain your own mapping between the business payment and the transfer. A retry should first inspect the existing transfer.

Can one transfer pay several suppliers?

The documented Multi-Send flow supports up to 20 distinct destination wallets. Review its allocation and net-payout rules before using it for a supplier run.

DOCUMENTATION AND EXAMPLES

Build from the documented workflow.

See the EarnFi case study ↗
Explore an agent-funded work example and its MultiHopper demo.

Reviewed October 5, 2026 against the linked documentation. Check the current guide and deployed cluster before implementation.

Explore related workflows.

Payroll ↗Treasury ↗Token migrations ↗

Plan your payments integration.

Bring your workflow, supported asset and operational requirements to the team.

Talk to the team ↗Explore developer tools