Approve the obligation.
The buyer links the invoice to the order and delivery, then authorises payment.
Indonesia anchored. Globally minded.
For buyers and suppliers: connect approved invoices, partner-led payments and reconciliation in one trade record.
An authorised buyer user prepares the payment instruction.
01From approval to reconciliation
For the buyer: an invoice matched to its payment.
For the supplier: a clearer view of when funds arrive.
ARRUS is being built to connect the steps between them. Buyer approvals, partner updates and receipt evidence stay attached to one reference, so finance teams can follow a payment without reconstructing its history.
Walk through an exampleThe buyer links the invoice to the order and delivery, then authorises payment.
Partner processing and supplier receipt are separate, evidence-backed stages.
Match the confirmed amount to the invoice. Keep any difference open for review.
02The connected record
Explore how commercial intent, supporting evidence and payment history become one useful transaction record.
Instructions, partner updates and payment confirmations linked back to the trade.
Drag to explore ↔ or use the arrows
3 of 3: Payment
Rooted in the real economy
From a supplier’s first order to an established export business, trade runs on people who deliver.
03A wider field of opportunity
Connect buyers and local suppliers around a shared payment workflow, with clearer status, supporting records and reconciliation.
04The next layer
Collateral tells one part of the story.
Performance adds another.
As businesses transact, a history of agreements, deliveries and payments begins to take shape. That record can support a financing partner’s assessment alongside validated invoices and real-world assets.
Our next layer brings that foundation toward working capital and tokenization, with the evidence and rights behind each asset kept in view.
Explore financing & RWADevelopment roadmapHow we are designing control
Before we talk
Buyers, suppliers and commodity traders who need a clearer connection between their commercial agreements, trade documents and payments. We are developing use cases for domestic supplier networks and cross-border trade.
ARRUS connects the trade workflow, payment visibility and reconciliation. Payment execution, banking, custody and other regulated functions are delivered through relevant partners, with the arrangement defined for each use case.
The design can connect fiat and stablecoin-based partner infrastructure where the relevant arrangements support it. The choice of rail is part of the payment design, alongside documentation, reconciliation and the needs of both trade parties.
A history of documented transactions can give financing partners a richer view of a business. We are developing this foundation first, with working-capital and RWA-based financing as a subsequent layer subject to partner assessment.
Yes. We start with a defined trade or supplier-payment workflow, agree the participants and partner responsibilities, and identify what to measure: onboarding, payment visibility, reliability and reconciliation.
Start with a defined workflow
Choose a small supplier group, map the payment process and agree what success should look like.
Discuss a supplier-payment pilotOnboarding · Receipt visibility · Reconciliation