Circle launches CPN Managed Payments for USDC settlement

Circle launched CPN Managed Payments on April 8, 2026, offering a fully managed USDC settlement stack for payment service providers, fintechs, banks and global platforms. The service is invitation-only and keeps partners fiat at the edge while Circle handles minting, burning, compliance and onchain settlement.

Circle named Veem, Thunes and Worldline among initial partners. The company reported that USDC processed more than $70 trillion in cumulative onchain settlement as of March 25, 2026, and about $12 trillion in onchain volume in Q4 2025. Circle Internet Financial, LLC provides the product, according to the company’s regulatory disclosures.

Onboarding begins with an invitation and a signed Managed Payments agreement. Circle issues API keys with role-based permissions that determine which endpoints a partner can call, covering subaccount management, wires, stablecoin payouts and reporting. Partners must confirm which capabilities are enabled on their keys before building production flows; if wires or Fiat Burns are not enabled, onboarding must be reopened.

Sandbox and production endpoints follow Circle’s developer documentation and require idempotency UUIDs on applicable POST calls. Merchant subaccounts can be provisioned under two models. In the Direct model, the partner submits merchant KYB through Circle’s End User Onboarding API and Circle performs approval and any requests for information before subaccounts go live, which can add approval latency. In the Intermediary model, the partner creates subaccounts via the Accounts API and retains merchant onboarding responsibility, enabling faster provisioning while shifting compliance obligations to the partner. Each subaccount has an accountId and a walletId that reference the same USDC balance record and can be pending, active, rejected or archived.

For incoming funds, operators create a continuous payment intent that generates a stable USDC receive address for a subaccount. When onchain USDC confirms to that address, Circle credits the subaccount and partners can invoke Fiat Burns to convert USDC to fiat and settle to the pre-registered bank account. Reconciliation relies on settlement reports keyed by accountId and timestamps and on webhook events that link payment IDs to bank credits.

For payouts, partners add bank accounts and wire instructions via the Wires API, fund fiat so Circle credits USDC, register payees in the Address Book, and send onchain USDC with the Payouts API. Payout calls must use the correct source.type and identifier: wallet debits require walletId and account withdrawals require accountId. Some agreements permit an internal line of credit or the use of a pooled main wallet for high-volume payouts; internal transfers between main wallets and subaccounts do not incur blockchain fees. Address Book recipients must be approved before the first payout and operators should treat Address Book webhooks as the readiness signal.

Partners should subscribe to webhook events for payment intents, payments, address book changes, payouts and credit transfers, and design systems for at-least-once delivery and idempotent updates. Requesting daily and monthly payin, payout and wallet balance reports supports operational reconciliation and audit.

Managed Payments is not appropriate when a firm requires self-custody wallets, wants direct onchain control, already runs a self-managed CPN stack, only needs Circle Mint mint/redeem, or has not received a Managed Payments invitation. Direct onboarding can impose KYB-related delays that may affect go-live timelines.