Capability matrix
| Capability | Status |
|---|---|
| Payment REST and hosted Checkout | Available |
| Retrieval/listing, idempotency, and signed webhooks | Available |
| Payment-linked e-CF | Assisted setup |
| Fiscal artifact and email delivery | Assisted setup |
| CardNet | Qualification-only |
| Native terminals and POS write-back | Qualification-only |
| Wallets (Google Pay and Apple Pay) | Qualification-only |
| NFC hardware | Qualification-only |
| Provider certification per merchant, domain, and environment | Assisted setup |
| Capabilities outside the published contract | Planned |
Available means the contract is ready for the documented flow. Assisted setup requires account data, a connection, or account support. Qualification-only requires laboratory or provider evidence and is not a general promise. Planned must not be used in production. Effective capability depends on merchant, environment, domain, provider, and recorded evidence; a variable or loaded screen never substitutes for that evidence.