x402 Payments

DeHeart is small, but x402 is a launch requirement. Paid task registration and paid heartbeat pokes should use x402 challenges rather than custom payment headers.

Flow

1. A task or provider returns an x402 challenge.
2. DeHeart selects an accepted rail and funding wallet.
3. The client builds an unsigned payment attempt.
4. A wallet or facilitator signs/settles the payment.
5. DeHeart records the payment attempt/receipt metadata and accepts the heartbeat.

Supported rail model

• base / USDC through hosted facilitators.
• solana / USDC through hosted facilitators.
• sui / USDC or SUI through self-hosted or verifier-only rails.

The current service exposes capability metadata and unsigned payment attempts. Facilitator execution and on-chain settlement verification are the next steps, but the API shape is x402-first now.

Live endpoints

curl https://api.deheart.io/v1/payments/x402/capability

curl https://api.deheart.io/v1/payments/x402/attempts \
  -H "content-type: application/json" \
  -d '{"deheartObjectId":"deheart:task:demo","providerId":"demo","capability":"task_execution","network":"sui","amount":"0.01"}'