Frequently asked questions

XyncPay is a non-custodial protocol translation layer for AI agent payments. It bridges the three emerging machine-to-machine payment protocols (x402 from Coinbase, MPP from Stripe and Tempo, and AP2 from Google) so any agent can pay any service regardless of which protocol either party uses. One API integration replaces three separate protocol implementations.

XyncPay supports three protocols: x402 (Coinbase), which uses HTTP 402 responses and EIP-3009 authorization for pay-per-request APIs; MPP (Stripe/Tempo), which provides session-based micropayment streaming with spending caps and rate limits; and AP2 (Google), which uses cryptographically-signed payment mandates. AP2 is currently in stub mode with inbound parsing active.

Non-custodial means XyncPay never holds, controls, or accesses agent funds at any point in the payment flow. The translation layer returns unsigned transactions. The agent signs each transaction with its own private key and submits it directly to the blockchain. XyncPay has no ability to move, freeze, or redirect funds.

Base mainnet is the primary settlement chain, with a verified FeeSplit contract handling atomic fee splits in USDC. Arc testnet is also live, with Arc mainnet beta launch planned for 2026. Solana support is on the roadmap, along with Polygon and Tempo in a future release.

Yes. XyncPay is a member of Circle's Alliance Program, listed in the public directory alongside Circle's ecosystem partners. The relationship aligns with Circle's Arc blockchain roadmap and XyncPay's focus on stablecoin-native infrastructure for the AI agent economy. See the directory listing at partners.circle.com/partner/xyncpay.

No. XyncPay (xyncpay.com) is not affiliated with Xync Network, xync.net, xyncinc.com, or any other similarly named entity. XyncPay is an independent company focused exclusively on AI agent payment protocol translation.

The translation flow has four steps: (1) An agent submits a payment request specifying source protocol, target protocol, amount, and recipient. (2) XyncPay normalizes the request into a canonical payment format, independent of any specific protocol. (3) The engine builds an unsigned transaction for the target settlement rail, including the atomic fee split. (4) The agent signs the unsigned transaction with its own private key and submits it to the blockchain.

The FeeSplit contract is an on-chain Solidity smart contract deployed on Base that atomically splits each payment between the payee and the XyncPay fee wallet in a single transaction. The fee rate is configurable by the contract owner without requiring redeployment. The contract has been verified on BaseScan and validated with live mainnet transactions.

Never. XyncPay returns unsigned transactions to the calling agent. The agent signs the transaction locally using its own private key and submits it to the blockchain. At no point in the payment flow does XyncPay request, receive, or have access to any private key material.

AP2 inbound parsing is active, meaning XyncPay can receive and interpret AP2-formatted payment mandates from Google-compatible agents. Outbound AP2 settlement routes through x402 or MPP settlement rails at launch, since AP2 does not yet define its own on-chain settlement mechanism. Full native AP2 settlement will be supported when the protocol specification matures.

XyncPay charges a flat 1% fee per transaction, with a $0.001 floor and a $1.00 cap. This means transactions below $0.10 pay the minimum floor fee, and transactions above $100 pay the maximum cap of $1.00. All fees are denominated in the settlement token (USDC).

Yes. The fee rate is owner-configurable via the FeeSplit smart contract. The contract owner can adjust the fee percentage, floor, and cap without redeploying the contract. All fee parameters are transparent and readable directly from the on-chain contract state.

Fees are collected atomically on-chain. The FeeSplit smart contract splits each payment into two transfers within a single transaction: one to the payee for the net amount, and one to the XyncPay fee wallet for the fee amount. There is no off-chain reconciliation or delayed settlement.

Yes. The FeeSplit smart contract has undergone Slither static analysis (Trail of Bits methodology) with zero high or medium findings, and Hashlock AI Audit with zero critical or high-severity findings. The one actionable recommendation (an emergency pause mechanism) was implemented using OpenZeppelin Pausable, and the contract was redeployed with the fix. The contract source code is verified and publicly viewable on BaseScan. See our Security page for full details.

XyncPay is a non-custodial protocol translation layer that does not custody or transmit funds. See our Security page for architectural details.

XyncPay practices minimal data collection. The only data processed is wallet addresses and transaction metadata required for protocol translation. No personal information, identity documents, or account credentials are required to use the API. Transaction metadata is retained only as long as necessary for operational purposes.