Solutions

Add credit-backed x402 payments to your facilitator.

4Mica is built first for facilitators. Add the 4mica-credit scheme to the facilitator you already run. Sellers get fast authorization and net settlement, while you keep the customer relationship and interface.

You stay the interface

Keep your endpoint, brand, and customer relationship. 4Mica runs behind them as the credit and clearing layer.

A scheme, not a stack

Advertise 4mica-credit in /supported and call Core from your settle path. You do not need to build collateral, netting, or settlement systems.

Make micropayments viable

Requests are authorized off-chain in one round trip, making small payments practical.

Use cases

Built for facilitators workflows

Give each stakeholder the payment primitives they need: instant authorization, clear limits, and settlement that stays easy to audit.

For facilitator operators

Add credit to your scheme list

Keep your current schemes and add credit-backed payments from the same endpoint.

Cut on-chain writes

Guarantees are netted within each clearing cycle, so settlement costs do not rise with every request.

Keep control of trust

Core verifies each signed claim, so the facilitator does not hold payer keys or customer funds.

For the sellers you serve

No seller-specific prefunding

Buyers use collateral-backed credit instead of topping up a separate balance with each seller.

Verified before delivery

Run paid work only after the guarantee is accepted and the BLS certificate is returned.

Process

Start with facilitators in 3 steps

The path is deliberately small: configure the payment session, verify each request, then settle the cycle with durable records.

  1. 01

    Advertise the scheme

    Add 4mica-credit and the CAIP-2 networks you cover to your /supported response so clients can discover it.

  2. 02

    Call Core during settlement

    Submit the signed guarantee from your settle path, validate V1 and V2 guarantees, and return the BLS certificate.

  3. 03

    Settle net positions

    Payable guarantees enter clearing cycles and settle as net positions on-chain instead of one transfer per request.

Works with the stack you already use — use 4Mica through x402-compatible HTTP clients, SDKs, any x402 facilitator, and the settlement infrastructure behind them.

Ready to integrate?

Plug 4Mica into your existing x402 flow in minutes — start with the docs or talk to the team.

Read the docsTalk to us

Facilitator concepts

Learn how the facilitator connects sellers to Core and what it is responsible for.

Facilitator API reference

The /supported, /verify, /settle, and /health contracts in full.

Talk to the team

Discuss network support and settlement cadence for your deployment.

FAQ

Common questions about facilitators

Do we have to run 4Mica Core ourselves?

No. Your facilitator calls Core over its API to submit guarantees and receive BLS certificates. You can also point sellers at the hosted facilitator if you would rather not operate one at all.

Do our sellers or buyers have to change clients?

They only need to register the 4mica-credit scheme. Buyers add the adapter to their current fetch wrapper, while sellers keep their existing x402 middleware and routes.

Does the facilitator take custody of funds?

No. Collateral is held by the protocol contracts and authorization comes from the payer's EIP-712 signature. A facilitator can delay or reject a request but cannot rewrite an authorization or move funds.

How is this different from settling each x402 request?

Per-request settlement puts one transfer on-chain per call. With the credit scheme, requests are authorized off-chain against collateral and only the net position of a clearing cycle is committed.

Something else on your mind?Contact us

Ready to build for facilitators?

Start buildingTalk to our team