Short Payment Descriptor
SPAYD stored in the QR Code
|Internet media type||
Short Payment Descriptor (SPAYD, SPD) is a compact data format for an easy exchange of a payment information using modern electronic channels, such as smart phones or NFC devices. Practically, the format is being deployed in the Czech Republic (where the format is an accepted unique standard for QR code payments) and Slovak Republic, but format can be technically used with any bank using IBAN account numbers. That includes currently most of European countries, some in the Middle East and few other ones.
The format was started in May 2012 during the development of the mobile banking for Raiffeisenbank a.s. (Czech branch of Raiffeisen BANK International) in cooperation with a technology company Inmite s.r.o.. Originally, the format should have been used for a P2P Payments via the QR Code. Later, it was generalized for many other usages, such as NFC payments or online payments.
Format was started as an opened effort from the very beginning and all specification, documentation, source codes, libraries and APIs were open-sourced under the Apache 2.0 license. Therefore, Short Payment Descriptor can be implemented by any subject without any legal concerns or fees. Due to this approach, the format was quickly recognized and accepted by many Czech invoice software companies and adopted by Czech banks. Československá obchodní banka (together with Zentity s.r.o.) was very active during the format development and it proposed the brand name for the communication to the users.
Short Payment Descriptor uses the ideas from the vCard (by the structure) and SEPA payment (semantics). It is designed to be compact, human readable and therefore, easy to implement. The format is based on defined key-value pairs and it can be extended by proprietary attributes (using the "X-" prefix). The string may contain any ASCII printable characters, any other characters must be encoded using the percent encoding.
Example of SPAYD payload
SPD*1.0*ACC:CZ5855000000001265098001*AM:480.50*CC:CZK*MSG:Payment for the goods
Default SPAYD keys
The default keys that are used in the SPAYD format are:
|ACC||YES||Max. 46 characters (IBAN+BIC)||
||Bank account - an identifier of the payment recipient. Either IBAN account number, or optionally "IBAN+BIC" format (with "+" as separator)|
... or ...
|ALT-ACC||NO||Max. 93 characters (2x ACC field + separator)||
||Alternative bank account list. In case recipient has more accounts, this field allows a banking application to pick the one in the same bank, allowing faster accounting and lower fees for the client.|
|AM||NO||Max. 10 characters - 7 + 1 (separator) + 2 (decimal places) ("9 999 999.99")||
||A payment amount.|
|CC||NO||Exactly 3 characters||Currency code in ISO 4217||A payment currency.|
|RF||NO||Max. 16 characters||
||A sender's reference.|
|RN||NO||Max. 35 characters||
|DT||NO||Exactly 8 characters||Date in ISO 8601 format||Due date|
|PT||NO||Max. 3 characters||
||Payment type (to be used by analytics)|
|MSG||NO||Max. 60 characters||
||Message for payment recipient.|
|CRC32||NO||Exactly 8 characters||
||CRC32 checksum (application level) computed from canonic representation.
Canonic representation is obtained by removing CRC32 field from SPAYD representation, reconstructing SPAYD string while sorting key-pair attributes by key and values (alphabetically), applying CRC32 (IEEE 802.3) and converting to hexadecimal uppercase string.
Original SPAYD string:
Integration with applications
The file type extension is:
MIME type of the format is:
Examples of format usage
- QR Codes with payment information (to be printed on invoices or displayed on the web) that can be scanned using either the mobile phone or a special automated teller machine (ATM)
- sending the payment information using the NFC technology
- sharing the payment information via the web or e-mail (via a downloadable file or and e-mail attachment)
- "Standard No. 26: Format for exchanging the payment information for Czech domestic payments using the QR codes". Czech Banking Association. 2012-11. Check date values in: