diff options
| -rw-r--r-- | wireformats.rst | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/wireformats.rst b/wireformats.rst index 705f4894..0be79f02 100644 --- a/wireformats.rst +++ b/wireformats.rst @@ -18,23 +18,22 @@ SEPA The Single Euro Payments Area (SEPA) [#sepa]_ is a regulation for electronic payments. Since its adoption in 2012, all of the banks in the Eurozone and some banks in other countries adhere to this standard for sending and receiving -payments. Note that the currency of the transfer will always be *EURO*. In +payments. Note that the currency of the transfer will (currently) always be *EURO*. In case the receiving account is in a currency other than EURO, the receiving bank may covert the amount into that currency; currency exchange charges may be levied by the receiving bank. -For the merchant to receive deposits through SEPA, the deposit request should +For the merchant to receive deposits through SEPA, the deposit request must contain a JSON object with the following fields: .. The following are taken from Page 33, SEPA_SCT.pdf . * `type`: the string constant `"SEPA"` - * `IBAN`: the IBAN of the account of the beneficiary + * `IBAN`: the International Bank Account Number (IBAN) of the account of the beneficiary * `name`: the name of the beneficiary - * `BIC`: the BIC code of the beneficiary's bank - * `edate`: the date given as a timestamp indicating when the transfer should - be executed - * `r`: a 64-bit random nounce + * `BIC`: the Bank Identification Code (BIC) code of the beneficiary's bank + * `edate`: the date given as a timestamp indicating when the transfer should be executed + * `r`: random nounce (used to make brute-forcing the hash harder) The JSON object may optionally contain: * `address`: the address of the Beneficiary |