ZILLQ brings agent payment mandates, EUDI wallet emulation and OAuth2 identity into a working European payments sandbox. The foundation is implemented. The platform grows from it.
Independent sandbox · Synthetic accounts and funds · European payment and identity mechanics
Start with the running sandbox, its public API contract and the recorded payment and identity flows. These are the existing building blocks for ZILLQ's agentic payments direction.
Represent a person's authorization as bounded terms for an agent: spending caps, permitted payees and validity windows. Explore the connection between consent, delegated authority, payment execution and refusal reasons.
Explore the mandate layer ↗The European Digital Identity Wallet sandbox implements signed credential presentation and verification, wallet SCA sessions and e-mandates. SD-JWT and holder-binding checks connect identity evidence to a particular request.
Understand the wallet and identity flow ↗The implemented sign-in flow uses OAuth2 / OpenID Connect through Keycloak. Authentication, session handling and roles provide the identity foundation around consent, payments and operator access.
Try the authentication flow ↗Create and inspect account-access consent, follow Strong Customer Authentication, and observe permission status and revocation. The API makes the consent lifecycle visible to developers.
Explore consent mechanics ↗Explore synthetic euro transfers, name-and-IBAN checks, payment statuses, account balances and transaction history. The sandbox connects the payment request to its resulting records.
Explore payment flows ↗Read the OpenAPI contract and follow payments, mandates and identity sessions through the operator views. Receipt verification and audit-chain inspection support scrutiny of authorization evidence.
Read the API contract ↗Agentic payments require both permission to spend and a way to establish who granted it. ZILLQ connects those questions to the European payment and digital identity landscape.
PSD2 consent, account information, payment initiation and SCA provide the existing open banking context. SEPA transfer semantics and Verification of Payee supply the payment mechanics explored in the sandbox. European Commission payment services overview ↗
The next European payment services framework is part of ZILLQ's engineering direction. Models and API behavior are developed gradually against the relevant texts; implemented sandbox behavior and the legal status of each requirement are separate questions.
European Digital Identity Wallets connect identity, credential presentation and payment authentication. ZILLQ already has an emulator and verifier foundation, using sandbox credentials and trust anchors. Further interoperability grows from those implemented mechanisms. EUDI payment authentication context ↗
The digital euro raises related questions about identity, authorization and European payment infrastructure. ZILLQ's current synthetic EUR accounts are sandbox money; the ECB digital euro is a separate initiative. Its development is relevant context for future payment research. ECB digital euro overview ↗
Start with a practical question, then explore the architecture. References for developers, product and risk teams, payment operations and anyone learning European payments. Read, print and reuse the examples without signing in.
A practical checklist for consent, authentication, retries and the resulting payment records.
Read the payment API testing guide ↗Step through a lost response, a same-key or new-key retry and duplicate webhooks. Synthetic data; runs in your browser.
Open the payment retry simulator ↗See where wallet evidence fits, what to verify and how to frame a sandbox evaluation.
Read the EUDI wallet guide ↗Match, close match, no match and unavailable: connect the check to the intended recipient.
Read the VoP guide ↗Examine the platform thesis, a focused purchasing use case and the evidence needed for the next milestone.
Read the ZILLQ investor brief ↗24 terms across open banking, SEPA, identity and operations. See the distinctions that prevent design mistakes.
Payments glossary ↗Compare consent, authentication, OAuth and agent mandates with a worked €30 purchase.
Payment consent vs SCA ↗Follow provider status, event delivery and reconciliation before retrying an uncertain payment.
Payment pending after SCA ↗Download synthetic JSON scenarios for limits, revoked authority, duplicate retries and concurrent spending.
16 agent payment test cases ↗How an AI agent's goal becomes a permitted payment, where human approval belongs, and why a prompt is not a spending control.
Read the agentic payments guide ↗Explicit spending limits, approved recipients, expiry and revocation. Understand the boundary between OAuth, identity and payment permission.
Read the mandate guide ↗Payment-services rules, wallet identity and payment schemes have different roles. See how they can support a European agentic architecture.
Read the European rails guide ↗Central bank money, conditional payments and delegated authority: what connects, what differs, and what can be designed using existing rails.
Read the digital euro guide ↗As software takes more actions on people's behalf, payment systems need explicit delegated authority, bounded execution and inspectable evidence. ZILLQ's product thesis is a reusable foundation for that boundary.
The existing payment, wallet and authentication components support a direction toward secure agentic payment and identity infrastructure for European use cases. Developers, payment providers and identity teams can examine the same mechanisms from different sides of a transaction.
The current public environment is an independently built sandbox. Product expansion, real-wallet interoperability, regulated integrations and commercial adoption are the next areas to establish through concrete work and partner evaluation.
Read the investor brief and 2027 direction ↗The platform includes agentic payment and mandate mechanisms, EUDI wallet emulation and signed credential verification, OAuth2 / OpenID Connect authentication, and a PSD2-style open banking sandbox. The public API and portal show the supported routes; operator access is required for the corresponding evidence views.
It uses synthetic accounts and funds. ZILLQ is an independent sandbox, and the public demonstration is not a licensed bank or payment service. The implemented mechanisms are the foundation for further product development.
The current wallet is an emulation with sandbox credentials and trust anchors. It supports examination of presentation, cryptographic verification, request binding and e-mandates. Real-wallet interoperability and the applicable relying-party requirements are further integration work.
Start with the mandate explanation, read the public API contract and explore the sandbox. For a deeper technical or investor discussion, contact the builder with the use case and the mechanisms you want to review.
For investment interest, technical partnerships or European payment and identity use cases, share what you want to evaluate. A useful discussion starts with the working platform, its evidence and a specific next step.
Framework references: EU payment services · EUDI payment authentication · ECB digital euro