Skip to main content
Enterprise pilot program — single tier while in pilot

Apple Pay Pilot pricing

A target envelope, scoped per organization. No checkout button — billing is handled alongside the scope agreement.

The CTA below uses the configured owner address in the repository. It is not a verified support channel.

Pilot program

Apple Pay Pilot

€500/month target envelope

Repo-first Apple Pay change program, scoped per organization.

Request a pilot discussion

Target envelope per organization. Final pricing depends on the agreed wallet of merchants, certificates, environments and connectors. Billing is handled alongside the scope agreement — no checkout button is enabled.

  • Repo-first Apple Pay changes (PR-driven)
  • Plan + readiness gating before activation
  • Deterministic synthetic demo (PSP / vault / GitHub)
  • Connector matrix labeled per integration
  • Microsoft Entra ID SSORoadmap — scoped, not built.
  • Google Workspace SSORoadmap — scoped, not built.
  • Real PSP connector (PSP TBD)Selected with the first pilot customer.
  • Real vault connector (vendor TBD)Selected with the first pilot customer.
  • Seat limitsNot invented.
  • SLAsNot invented.
  • Savings guaranteesNot invented.
  • Customer logosNone used in marketing.

Apple Pay Pilot — Frequently Asked Questions

Honest answers. If a question is not below, we have not decided yet.

What does the €500 / month actually cover?

A target envelope for the repo-first Apple Pay change program, scoped per organization: an agreed wallet of merchants, certificates, environments and connectors. SSO (Microsoft Entra ID or Google Workspace) is scoped in the program but not yet built. Implementation work that is not repeatable is estimated separately.

Which PSP, vault and IdP are supported?

The PSP and vault connector are selected with the first pilot customer. Until that decision is made, those integrations are exercised against synthetic fixtures only and are explicitly labeled as such on this page. Microsoft Entra ID and Google Workspace SSO are scoped in the program but not yet available in production.

Is checkout enabled for the pilot?

No. The pilot tier uses an email CTA rather than a checkout button — the program is not in the same self-serve billing flow as legacy plans, and the Stripe backend is not wired to the pilot tier. Billing for the pilot is handled alongside the agreement on scope.

Are there seat limits, SLAs or savings guarantees?

Not invented. The pilot measures interventions per change, work time vs. wait time, blocking causes, percentage of steps automated and verified closures. Any future commitment on SLAs or savings will come from measured pilot data, not marketing copy.

What is the configured owner address used in the CTA?

It is the address configured in the repository source tree (see app/layout.tsx and app/not-found.tsx). It is not certified as a working support channel. Replies are not contractually committed.

cbdbd2d