Fund Movement

Follow the XRP. Every movement needs a reason.

Funding, releases, refunds and fees should connect to visible contract state and independently reviewable XRP Ledger activity.

Exact instructionsLedger verificationState-based settlementVisible transaction history
Funding Path

From payment instruction to active agreement.

A contract does not become funded because somebody says they paid. The transaction must match the funding context expected by the workflow.

Agreement created

The parties, amount, milestones, deadlines and settlement rules are established.

Instructions prepared

The payer receives the expected destination, XRP amount, destination tag and memo where applicable.

XRP submitted

The payer sends the transaction using the exact funding information provided.

Ledger checked

Transaction evidence is compared with the destination, amount, tag, memo and result expected by the agreement.

Funding accepted

A matching transaction allows the agreement to enter its funded or active state.

Evidence retained

The transaction reference remains part of the payment and contract history.

Settlement Path

Contract state determines where eligible value goes.

Release and refund actions follow the active product workflow. A ledger transaction records movement; application state explains the reason behind it.

Milestone release

Approved work can make the applicable milestone payment eligible for release.

Remaining release

Completed agreement value can settle according to the product's final resolution rules.

Milestone refund

Eligible milestone value can return when the defined refund conditions apply.

Remaining refund

Uncommitted or refundable remaining value can follow the applicable return path.

Cancellation

A permitted cancellation closes future work and resolves eligible remaining value.

Fee routing

Applicable platform fees are separated and routed according to the published economic model.

Payment Precision

Small instruction errors can create large operational problems.

Correct destination

Confirm the receiving address rather than relying on a copied message or screenshot.

Correct amount

Send the XRP value expected by the agreement and funding instruction.

Correct destination tag

A missing or incorrect tag can prevent reliable association with the intended workflow.

Correct memo

Where required, memo context helps connect the ledger transaction with the correct contract.

Trust Sequence

Read the complete operating model.

Rules define the agreement. State controls valid actions. Ledger activity records value movement. Risk disclosure explains the remaining limits.

Connected System

Continue into the products, architecture and evidence.

Developer Architecture

See how identity, verification, contract state and settlement fit together.

Developer Overview →

Security

Review operational protections and user security responsibilities.

Review Security →

Fees & Economics

Understand the 5.89% platform fee and its four equal economic buckets.

Review Fees →

Proof & Transparency

Inspect the token supply, issuer, wallets, escrows and documented evidence.

Explore Transparency →
Verify the Ledger Evidence

Every credited payment should match one expected obligation.

Learn how transaction finality, result codes, delivered amounts, destination addresses, tags and memos establish payment evidence.

XRPL Integration

Understand how ledger evidence connects to application and contract state inside the payment infrastructure.

Explore XRPL integration →
Continue

The ledger shows what moved.

Contract state explains why it moved, what became valid and what happens next.

Payment operations guide

Follow the money from instruction to resolution.

The complete guide explains the practical checks users make before funding and the contract states that govern release, refund and cancellation.

Read how to fund a Trustless contract →