x402 payments and buyer recovery
Last updated 2026-11-16. Operator: Gabriel Dietsch, Miami, Florida, USA. Contact: gdietsch-j16thn@mail.grokbot.com
This page describes how the server at https://signals.incomefather.com actually handles x402 payments today. It is a description of current behavior, not an extra guarantee. The terms of service still apply.
Where payments go
- Base (eip155:8453), USDC
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, payTo0x6d7be981c103eD360874a7703ad3CD6a98929aFB. Settled through the Coinbase CDP facilitator; PayAI is configured only as a fallback. - Solana (solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp), USDC
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v, payToBvE6kQthHmNPhegeSAA1qS5HvPG1DzngUuSVoLWdnQYV, settled through PayAI.
Order of operations (scheme exact, x402 v2)
- An unpaid request gets HTTP 402 with a
PAYMENT-REQUIREDheader. Nothing is charged. - Your client retries with a signed
PAYMENT-SIGNATURE. The server asks the facilitator to verify it. Verification moves no funds. - The route then runs and its response is held in memory, not sent yet.
- If the route fails (HTTP 4xx or 5xx), the payment is not settled: you get the error and are not charged.
- Only if the route produced a 2xx result does the server ask the facilitator to settle. If settlement succeeds, you receive the result together with a
PAYMENT-RESPONSEheader (base64 JSON withsuccess,transaction,network,payer). - If settlement fails or the facilitator returns an error, the held result is discarded and you get HTTP 402 (for example
settlement_failed) instead of the data.
Each signed authorization carries a one-time nonce and an expiry, so the same signature cannot be charged twice. A retry after a failure means signing a new payment. Results are not cached or stored for later pickup, and we do not keep request or response bodies.
If settlement is uncertain
A network drop or facilitator timeout can leave you with an error and no way to know from the response whether the transfer landed. Before signing a new payment:
- Look for a USDC transfer from your payer address to the payTo address above on Basescan or Solscan around the time of the call.
- On Base you can also read
authorizationState(payer, nonce)on the USDC contract for the nonce you signed. If it is unused and the authorization has expired, it can no longer be settled. - If no transfer exists, you were not charged; retry normally.
If you paid but did not get the result
Open an issue at github.com/gdietsch/trading-signals-mcp/issues or email gdietsch-j16thn@mail.grokbot.com with the network, the transaction hash or signature, the route, and the approximate time. Never send private keys or a signed payment header.
Our server logs each settled paid call (route, HTTP status, payer address, network, amount and transaction hash; no request bodies or raw IPs) and keeps these records for 90 days. We use them to check whether a 2xx result was produced for your transaction and reply with what we find. Any remedy, such as returning the amount to the paying address, is decided case by case by the operator. There is no automatic refund, and settled on-chain payments are otherwise final as stated in the terms.
Official channels
- Website: https://signals.incomefather.com
- X: @TradingSignalsA
- Code and issues: github.com/gdietsch/trading-signals-mcp