When an AI agent buys a dataset, hires a freelancer, or pays a vendor, the money has to land somewhere a human bank recognizes. AsterPay, a Birmingham-based developer platform, is betting that the somewhere is a euro account, and that the rails connecting the two will be SEPA Instant fed by USDC.
The company markets itself as “the only API accepting both x402 (Coinbase) and MPP (Stripe/Tempo) payments” with settlement from USDC into euros via SEPA Instant [AsterPay website]. That dual-protocol claim is the wedge. x402, revived by Coinbase, is an HTTP-native payment standard aimed at machine-to-machine commerce. MPP, the Merchant Payment Protocol associated with Stripe and Tempo, is the parallel approach for stablecoin merchant flows. Most fintech infrastructure picks one camp. AsterPay is trying to sit on both.
The bet
AsterPay's pitch to developers is narrow and specific: take a dollar-denominated stablecoin in, drop a euro in a bank account out, and do it fast enough that an autonomous agent or a payroll run does not have to think about it. According to Circle's Alliance Directory, the company “enables payroll servicers, remittance providers, and marketplaces to pay out dollar-denominated stablecoins as euros via SEPA Instant, including multi-currency support (EUR, GBP, AED) through licensed partners” [Circle Alliance Directory].
The product surface goes beyond settlement. AsterPay's site advertises a KYA (Know Your Agent) Trust Score scaled 0 to 100, an x402r escrow and refund mechanism, and session billing primitives, all framed as MiCA-compliant [AsterPay website]. Translated: the company is not just moving money, it is trying to be the trust and dispute layer for agent commerce. If agents are going to spend real money on behalf of real businesses, somebody has to underwrite which agents are good for it and what happens when a transaction goes wrong. AsterPay wants that job.
Why it could be big
Two trends converge here. The first is the rapid normalization of stablecoins as a settlement medium for cross-border B2B flows. The second is the arrival of agent-initiated payments as a real category, with Coinbase publishing x402 and Stripe and Tempo pushing MPP into developer hands. The market for an API that abstracts both protocols and terminates in regulated European bank rails is, on paper, a useful one. Listing in Circle's Alliance Directory [Circle Alliance Directory] places AsterPay inside the orbit of the largest regulated USDC issuer, which matters for distribution to the payroll and remittance buyers Circle already talks to.
The MiCA angle is also more than marketing. Europe's stablecoin regime gives regulated euro off-ramps a structural advantage over offshore conversion routes, particularly for payroll customers who cannot tolerate ambiguity about whether a vendor is licensed. A clean USDC-to-euro pipe, settled on SEPA Instant inside a MiCA-aware framework, is exactly the boring infrastructure that agent-economy headlines tend to skip over and that finance teams actually buy.
Product surface at a glance
| Capability | Detail | Source |
|---|---|---|
| Inbound protocols | x402 (Coinbase) and MPP (Stripe/Tempo) | AsterPay website |
| Settlement rail | USDC to EUR via SEPA Instant | AsterPay website |
| Multi-currency | EUR, GBP, AED via licensed partners | Circle Alliance Directory |
| Agent trust | KYA Trust Score, 0 to 100 scale | AsterPay website |
| Dispute layer | x402r escrow and refunds | AsterPay website |
| Target buyers | Payroll servicers, remittance, marketplaces | Circle Alliance Directory |
The team and traction
AsterPay maintains a public GitHub organization with 17 repositories [GitHub], a developer footprint consistent with an API-first product. The Hacker News listing for “AsterPay, EUR Settlement for AI Agent Payments (USDC to via SEPA Instant)” [Hacker News] points to the company actively courting the developer audience that builds with x402 and MPP today. A whitepaper is published on the company's own domain [AsterPay whitepaper]. The Circle partnership listing is the most concrete external validation in the public record [Circle Alliance Directory].
The honest counterfactual
There is a real complication in the public record worth naming. UK Companies House lists ASTERPAY LTD, company number 15261650, as dissolved [GOV.UK]. A separately named entity, Aster-Pay Limited, appears on Facebook describing a card-to-card remittance service [Facebook], which is a different product from the API operating at asterpay.io today. Bears will read the Companies House status as a reason to ask which legal entity is contracting with developers and Circle partners now, and under which license the SEPA Instant settlement is performed. Bulls will point out that founders frequently restructure UK entities when pivoting product or raising, that the live product surface, the Circle directory listing, the active GitHub, and the published whitepaper all point to an operating company, and that MiCA-compliant settlement requires a licensed partner relationship rather than a single corporate shell. The honest reading is that prospective customers should ask AsterPay which entity holds the contracts and which partner bank terminates the SEPA leg before wiring production traffic. That is a normal diligence question for any stablecoin off-ramp, not a verdict.
What to watch
The next twelve months will turn on three things. First, whether AsterPay names a marquee payroll or remittance customer publicly, the kind of logo Circle's directory is built to generate. Second, whether the x402 and MPP ecosystems both gain enough developer traction to make dual-protocol support a genuine moat rather than a hedge, a question that depends as much on Coinbase and Stripe as on AsterPay. Third, whether the company discloses its licensed-partner stack and corporate structure in a way that lets enterprise buyers clear procurement. The agent-payments category is forming in real time, and the infrastructure layer underneath it is wide open.
So here is the question for readers watching this space: when an autonomous agent spends a dollar, who do you want holding the euro on the other side, and what proof do you need before you trust them with payroll?