Skip to main content
Useroutr lets your users fund your application from any supported rail, crypto or fiat, and settles that value wherever you need it, including into a balance you control.
Useroutr is pre-launch. These docs describe the shipping surface and are updated as it lands. Sections marked as not yet available are named as such rather than quietly omitted.

​
The shape of an integration

1

Declare what you want

Create a funding intent with an amount and a destination. The destination can be a blockchain address, a bank account, or an internal balance.
2

Let the user pick how to pay

Open the checkout, or fetch the options yourself and build your own. Your user chooses a rail; you never name one.
3

We route and settle

We quote across every eligible provider, pin a route, and deliver.
4

Your application is credited

A webhook fires and the ledger records the credit. Exactly once.

​
Where to go next

Quickstart

From zero to a settled test funding.

Core model

Rails, endpoints, and funding intents. Read this before building.

API reference

Every endpoint, generated from the spec.

Errors

Every error code, what causes it, and how to resolve it.

​
What makes this different from a payments API

A payment is finished when money reaches an address. Funding is finished when your application’s state changes: a balance rises, credits are granted, a deposit becomes tradeable. That last step is the part most integrations end up building themselves, and it is the part that goes wrong. Useroutr treats it as the product. A funding intent is only settled when its ledger credit exists, so “did this user pay” and “should I credit this user” are the same question with the same answer.