Glossary
| Term | Meaning |
|---|---|
| Onboarding | The company verification and agreement-signing process required before enabled ZTL services can be used. |
| Consent | A user’s bank authorization for ZTL to access account information and initiate payments for a particular organization and bank. |
| PSU | Payment service user: the person using the partner application and bank service. |
| SCA | Strong customer authentication performed with the bank or identity provider. |
| AIS | Account information service, including account, balance, and entry retrieval. |
| PIS | Payment initiation service. Creation does not replace the user’s bank approval. |
| TPP | Third-party provider consuming an account-servicing bank’s open-banking interface. |
| AISP | Account information service provider. |
| PISP | Payment initiation service provider. |
| ASPSP | Account servicing payment service provider, usually the bank holding the account. |
| BBAN | Basic Bank Account Number, a domestic account identifier. |
| IBAN | International Bank Account Number. |
| BIC/SWIFT | International bank identifier used to route and identify a financial institution. |
| KID/OCR | Structured creditor reference used for invoice matching. The current schemas identify the accepted remittance type per operation. |
| End-to-end ID | Partner-supplied transaction identifier returned in status results so a transaction can be correlated through its lifecycle. |
| Sandbox | Our staging environment used for integration testing purposes. |
Store ZTL resource IDs separately from business identifiers such as an end-to-end ID, organization number, BBAN, or IBAN. They serve different purposes and must not be reconstructed from each other.