Theme
digid pay documentation
Everything you need to integrate digid pay — an API-first online payment gateway. Accept card payments under your brand with a checkout your customers never leave, transparent per-transaction pricing, and a token-only trust boundary: card data never touches your servers or ours.
The integration surface is one of two paths:
- Checkout snippet — drop a script tag into your page; digid pay Secure Fields render inside it and do the rest (zero-API path).
- Payments API — a REST API for building your own checkout UI around the same token capture.
Both paths converge on the same object model: a PaymentIntent you create, confirm with a payment token, and follow through webhooks to a terminal state.
Key facts
| API base | https://api.digid.cc/v1 |
| Dashboard | https://pay.digid.cc/dashboard/login |
| Signup | https://digid.cc/signup |
| API contract file | /openapi.yaml (this site) |
| Webhook signature | HMAC-SHA256, Digidpay-Signature header |
| Card data | captured inside digid pay Secure Fields; only tokens cross into digid pay systems |
Status legend
Every page in this site carries an honest status in its frontmatter and is badged where it matters. Treat a page's claims within its status:
| Badge | Meaning |
|---|---|
| live | The behaviour exists today and is what merchants rely on. |
| planned | The capability is committed and specified but not yet provisioned for public use. |
| contract | The interface is defined exactly as the facade will implement it, but the facade is not yet built. Spec-first: nothing invented beyond the agreed contract. |
Quick orienting statuses: the sandbox environment exists and routes test payments today; the open public sandbox keys are planned; the REST API, webhooks, and agent surfaces are documented as contract until the facade ships.
Reading order
- Quickstart — get a sandbox payment working.
- Sandbox — test rails, test cards, limits.
- Payments concept — the PaymentIntent lifecycle.
- Tokens concept — why no card number ever touches you.
- API reference — the REST contract.
- Secure Fields — style the card-entry iframes.
- Agents — MCP and A2A integration for AI agents.
- Operations — from sandbox to live.
Still exploring?
- New here → Quickstart
- Developer → API overview
- Compliance question → PCI posture
- AI agent integration → MCP server · A2A AgentCard