payX402WithHazbaseWallet
Inspect HTTP routes, arguments and responses used by @hazbase/kit/wallet. Additional authentication and passkey APIs are covered in the auth SDK reference and integration guide.
User-session, signature and permission requirements differ by API. Check the specifications below and the connection requirements of your API environment. Check API access requirements
POST /api/payments/x402/hazbase-wallet/pay
Request
payX402WithHazbaseWallet(input: PayX402WithHazbaseWalletInput): Promise<X402HazbaseWalletPaymentResult>Operation authorization requires deviceBindingId and highTrustToken.
| Field | Type | Required | Location |
|---|---|---|---|
emailSession | string | Yes | Authorization header |
paymentRequestId | string | Yes | JSON body |
smartAccountAddress | string | Yes | JSON body |
deviceBindingId | string | Yes | JSON body |
highTrustToken | string | Yes | JSON body |
accountSalt | string | No | JSON body |
waitForReceipt | boolean | No | JSON body |
expectedAmountAtomic | string | No | JSON body |
expectedPayTo | string | No | JSON body |
endpoint | string | No | SDK endpoint override |
POST requests include Content-Type: application/json and x-request-id. The request ID supports tracking; it is not a blanket idempotency guarantee.
Response
export type X402HazbaseWalletPaymentResult = {
paymentRequestId: string;
paymentAttemptId: string;
xPaymentHash: string;
paid: boolean;
verified: boolean;
settled: boolean;
payer: string;
chainId: number;
network: string;
relayMode?: string;
submittedUserOpHash?: string | null;
transactionHash?: string | null;
gasEstimate?: Record<string, unknown>;
xPayment?: string | null;
receipt?: Record<string, unknown> | null;
status?: string;
errorCode?: string;
retryAfterMs?: number;
};Find nested types in the SDK reference. The client handles both a top-level response and a response wrapped in data.
X402HazbaseWalletPaymentResultHandling failures
Non-2xx responses become HazbaseWalletApiError. Record status, code and message, distinguishing API errors from network failures. Keep credentials out of logs.
Errors & troubleshooting