codespar_crypto_pay

There is no typed wrapper yet — call via session.execute().

Rails

Coinbase Commerce returns a payment page URL — share with the user, they pay any supported chain, and the webhook lands when settled. Bitso is the right pick when the operator wants to accept BRL but settle internally in crypto (or vice versa).

Direct execute

const result = await session.execute("codespar_crypto_pay", {
  amount: "0.05",
  currency: "ETH",
  method: "stablecoin",
  recipient: { wallet_address: "0xabc..." },
  metadata: { order_id: "1234" },
});

console.log(result.payment_url ?? result.destination_address, result.tool_call_id);

Args shape

Result shape

type CryptoPayResult = {
  tool_call_id: string;
  payment_url?: string;          // Coinbase Commerce hosted URL — inbound flow
  destination_address?: string;  // for outbound payouts
  expires_at?: string;
  status: "pending";             // terminal state via paymentStatus
};

Operator setup

• Coinbase Commerce — API key (api_key auth_type). Optional shared-secret for webhook verification.
• Bitso — hmac_signed auth_type. Operator stamps API key + API secret in /dashboard/auth-configs; runtime signs each request with HMAC-SHA256 over nonce + method + path + body.

Async settlement

Crypto rails settle on-chain; latency varies by chain (seconds for most stablecoins on Polygon / Arbitrum, minutes on Bitcoin). The flow mirrors codespar_charge:

1. codespar_crypto_pay returns the payment_url or destination_address and a tool_call_id.
2. Buyer pays on the hosted page or sends the on-chain transfer.
3. Provider webhook lands — backend correlates by idempotency_key ↔ external_reference.
4. session.paymentStatus(tool_call_id) returns succeeded (or expired if the buyer abandoned).

See async settlement.

See also

• codespar_charge — fiat counterpart
• hmac_signed auth — Bitso authentication pattern
• Crypto Pay Agent cookbook — end-to-end stablecoin example
• Tools & meta-tools — full meta-tool list