Three design partner slots.
PQSafe AgentPay is building toward a small group of named institutional design partners through 2026. These are not customers in the conventional sense — they ship alongside us, get direct co-design input on AP2-PQ, and trade a 12-month dedicated engineering relationship for a logo placement and reference call.
Slot 1
Reserved for a regulated financial institution
HKMA / MAS / FCA / FFIEC-regulated. AI agent payments or treasury automation.
Slot 2
Reserved for a payment / fintech infrastructure operator
Card issuer, virtual card, account-to-account, or stablecoin rail.
Slot 3
Reserved for an AI agent platform / framework
Team shipping agents that move money to production.
What we ship together
- Dedicated integration engineering. Direct line to the co-founders. We help your team wire PQSafe into your existing payment flow, agent runtime, or compliance stack — not just docs and Discord.
- Co-designed mandate schema. If your use case needs extra mandate fields (e.g., regulatory reference number, treasury account class, intent hash), we add them to the AP2-PQ profile rather than asking you to fork.
- Conformance test vectors specific to your rail. We extend the public test vector set so your edge cases become part of the canonical spec.
- Joint white paper (optional). One-pager or full doc co-authored with your team, published on both sites and submitted to the relevant standards body (FIDO TWG, IETF) as evidence of production deployment.
- Pre-audit findings sharing. Our internal security review log and the eventual Trail of Bits report are shared under NDA before broader publication.
What we ask for
- A named integration project with a 12-month timeline and an internal exec sponsor at your organization.
- Permission to publish your logo on this page and in investor materials once the integration ships to your production environment.
- One 30-minute reference call per quarter for our investor due-diligence and prospective design partner conversations.
- Honest feedback in writing. A short quarterly note — what works, what doesn't, what we should ship next — published on the joint white paper if there is one.
What we do not ask for
- No fee for the design partner relationship itself. The infrastructure (signing, ML-DSA-65 verification, SDKs, conformance, RFC contributions) is and remains free under Apache-2.0.
- No exclusivity. You can use any complementary stack (Stripe Issuing for cards, Airwallex for FX, Plaid for ACH, etc.). PQSafe wraps the authorization layer; it does not replace the rails.
- No equity. This is a technical partnership, not a strategic investment relationship.
- No press obligation beyond logo placement. You opt into co-marketing where it suits you.
Timeline
- Today – June 30, 2026: selecting design partners for the three slots above. Target close on Slot 1 by August 1, 2026 (signed LOI).
- July 2026 – February 2027: integration engineering, conformance test vector extensions, internal pre-audit findings exchange.
- Q1 2027: joint white paper and production launch announcement; logos go live on this page; first reference calls available.
- Q2 2027: follow-on cohort for paid customers (pricing per main site: US$29/mo + 0.3% above $10K SUM).
How to apply
Email raymond@pqsafe.xyz with:
- Your organization, your role, and the named exec sponsor.
- One paragraph on the integration project — what you'd like PQSafe to gate, what success looks like.
- Whether your timeline aligns with a Q3 2026 integration start.
First reply within 48 hours. If we are not the right fit, we will tell you in the same reply.