- Betalingsservice Guidelines for Data Suppliers (2025)Betalingsservice's 2025 data-supplier guidelines define delivery structures and transaction codes for collection, mandate and payment-status exchanges. They connect creditors and data suppliers with Betalingsservice's proprietary layouts, including XML000 and payment-slip information.
- CHIPS ISO 20022 Message Usage Guidelines 2026The 2026 CHIPS ISO 20022 guidelines turn the message definitions into the content and validation profile used by CHIPS participants. They align how institutions construct payment instructions with the high-value system's processing requirements, reducing conflicting interpretations.
- Common Global Implementation Market PracticeCGI-MP harmonises ISO 20022 exchanges between corporates and banks, covering payment initiation, status messages and account reporting. Implementation choices reduce bank-specific variants, helping companies reuse integrations and reconcile payment results across banking partners.
- CPMI Harmonised ISO 20022 Data Requirements for Cross-border PaymentsCPMI's harmonised ISO 20022 requirements define a minimum set of data for cross-border payments end to end. They address fragmented message usage so information remains complete and consistently interpretable as a transaction passes between payment providers and infrastructures.
- FEBRABAN CNAB 240 Standard Layout — Version 10.11FEBRABAN CNAB 240 v10.11 defines fixed 240-position files for Brazilian bank-client payments, collections and reporting. It includes electronic Boleto processing and a 44-position barcode field, giving institutions and clients a common layout for remittance and return-file exchange.
- HVPS+ ISO 20022 Usage GuidelinesHVPS+ harmonises ISO 20022 market practice across high-value payment systems. Its guidelines help operators and participants align message content, reducing differences between implementations and supporting consistent payment and reporting data when banks connect to many systems.
- ISO 20022 Financial Services — Universal financial industry message schemeISO 20022 provides the modelling method, business concepts and repository used to create structured financial messages. Payment and other financial-service message families build on that platform, with schemes and market-practice profiles defining how the messages are implemented.
- ISO 8583:2023 Financial-transaction-card-originated messagesISO 8583:2023 defines a messaging interface for card-originated financial transactions between acquiring and issuing systems. It organises transaction-message structure and content, while network or processor implementation profiles determine the data and rules used in a service.
- JSON-RPC 2.0 SpecificationJSON-RPC 2.0 defines a stateless, transport-independent protocol for calling remote procedures using JSON. Requests, responses, named or positional parameters, notifications, identifiers, structured errors and batches give applications message rules without prescribing transport.
- MyDebit ISO8583 SpecificationsMyDebit's PayNet interface uses ISO 8583:1987, with a PayNet header, message types, bitmaps and data elements. Network-management and key-exchange messages complete this scheme-specific profile, defining the message format rather than assuming adoption of the newer ISO 8583 edition.