Foinse

Checkout & links

Accept compute on your own site or API with the Foinse SDK. Hosted payment links are planned, but they are not available yet.

Use the SDK

How checkout works

  1. You set the price. Choose what the visitor is paying for and which provider compute to accept.
  2. The visitor pays. Foinse checks the payment before your site gives access.
  3. You get the compute and a receipt. The payment, fee, and settlement status are recorded.
See the technical checkout flow
  1. Quote: the route declares its exact price in a provider-denominated unit.
  2. Authorize: the visitor presents a capped native provider key directly to the toll gate. The route owner and recipient do not receive that key.
  3. Settle: Door 1 verifies before charging; Door 2 verifies by making the exact charge. The resulting bearer compute balance is recorded on the Foinse ledger.
  4. Grant access: Door 1 issues a single-use, resource-bound qtt1 ticket. Door 2 uses the committed movement event_id.
  5. Receipt: the per-line record identifies the movement, price, protocol fee, settlement state, and evidence grade.

What it costs

The initial processing toll is 5% on compute-token movement, 5% for Base USDC ramps, and 5.5% for card ramps. The seller receives the full listed subtotal; the buyer pays the disclosed toll on top. See pricing and toll terms.

What you can use today

Use the Toll SDK for a current integration, and start in the sandbox in test mode. Hosted claim links are not ready; do not build around claim-link endpoints yet.