This page lists what the IXO Payments Facilitator does, grouped by the job you want done. Each line has a status and a link to the page that explains it. The full technical list, with a link to each reference doc, is docs/features.md in the product repository.
| Status | Meaning |
|---|---|
| Live on mainnet | Runs with real money on IXO's facilitator (facilitator.ixo.earth). asks.world uses it in production. |
| Ready to install | Shipped in @ixo/payouts-facilitator and tested end to end on devnet. No company runs it on mainnet yet. |
| Test mode only | Works against the provider's sandbox. Refused on mainnet. |
| Coming soon | Built or planned, not offered yet. |
What works today lists the same capabilities next to the rest of IXO.
Charge for decisions
An oracle is paid for each decision. Money is held or checked when the oracle accepts a claim, and moves only after the decision engine signs a receipt.
| Feature | Status | Read more |
|---|---|---|
| The x402 flow: offer, the 402, verify, and settle on the engine's receipts | Live on mainnet | Charge for decisions |
| Card: a hold when the claim is accepted, captured after the decision, on the oracle owner's own Stripe account. At least 50¢ | Live on mainnet | Card |
| Card refunds, disputes and 3-D Secure, without a Stripe dashboard for the owner | Live on mainnet | Card |
USDC on Base with x402's standard exact scheme, sent after the decision, straight from payer to owner. At least $0.01 | Live on mainnet | USDC on Base |
| IXO's USDC fee pulled later under an allowance the owner sets | Live on mainnet | USDC on Base |
| PAY on the IXO chain, only for oracles IXO manages itself | Live on mainnet | PAY |
| No decision, no charge: a hold lapses after 24 hours, can be released early, or extended up to 30 days while a person reviews | Live on mainnet | Nothing is charged before a decision |
Cash out
A pro who earned credit on asks.world turns it into money.
| Feature | Status | Read more |
|---|---|---|
| To USDC on Base, in the pro's own wallet | Live on mainnet | Cash-out |
| To a bank account, through a Stripe account in the pro's name | Live on mainnet | Cash-out |
| No fee. $10 to $1,000 per cash-out, one at a time | Live on mainnet | Cash-out |
| An identity check on every cash-out | Live on mainnet | Cash-out |
| Retry a failed cash-out, or get the amount back | Live on mainnet | Cash-out |
| To African bank accounts and mobile money, through Yellow Card | Coming soon |
Pay your company's people
A company pays people for approved claims from its own payouts facilitator: on its own Cloudflare account, with its own keys, from its own Stripe balance or USDC wallet.
| Feature | Status | Read more |
|---|---|---|
| Set up by Claude Code or Codex from one short prompt | Ready to install | Host your own payouts facilitator |
| Stripe Connect: from your Stripe balance to the payee's bank | Ready to install | How it pays |
| USDC on Base, from a payout wallet the installer creates | Ready to install | How it pays |
| Visa Direct, to a card in the payee's own currency | Test mode only | |
| Yellow Card bank and mobile money in Africa | Coming soon | |
| Pay only decisions from verifier oracles you trust | Ready to install | Trust the verifier |
| Limits per payout, per payee per day, and per day for the company | Ready to install | Set limits and approvals |
| Approval above an amount you choose, with four eyes: the approver is never the person who set the rule, invited the payee or entered the amount | Ready to install | Set limits and approvals |
| Pause every payout at once, and resume | Ready to install | Run it |
| Roles for your payout team: rules, approver, reviewer, reader, payees, manager, exporter, oracles | Ready to install | Set limits and approvals |
| Your company's owners on chain are its payout admins | Ready to install | Set limits and approvals |
| A signed receipt for every payout, which anyone can check against your facilitator's public key | Ready to install | What each record proves |
| Export payouts as a spreadsheet (CSV) | Ready to install | |
| A trust check a Portal runs from public data before it sends you payouts | Ready to install | Check it |
| Payees invited by link add their bank or wallet on asks.world | Ready to install | How it pays |
| An ask your company posts is found on chain within a minute | Ready to install | |
| Emails to payees and team members in your company's name | Ready to install (set up by hand) | |
| A changed payout method waits 24 hours before it is paid, and the payee is warned | Ready to install |
Operations and security
| Feature | Status | Read more |
|---|---|---|
| Money moves only on a decision the engine signed | Live on mainnet | Nothing is charged before a decision |
| IXO never holds a payer's money: card charges land on the owner's Stripe account, USDC goes payer to owner | Live on mainnet | Three ways to pay |
| Each call is signed by the caller for exactly one action (a UCAN) | Live on mainnet | Who may call |
| Alerts for anything a person must act on, a monitor on every scheduled job, metrics and health checks | Live on mainnet | |
| Payee data sealed at rest; logs and alerts carry ids and codes, never personal or payment data | Ready to install | |
| Secrets generated on your computer, never printed, never overwritten | Ready to install | The secrets file |
Report a vulnerability privately through GitHub, never in a public issue: see the security policy.