taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit f4e5f2ec0ea16e4794d6e1b63bdade027fcd394e
parent 98e3d9107e8292d406b01cac364fb282b096f6a1
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Tue,  9 Feb 2016 15:04:11 +0100

Merge branch 'master' of ssh://taler.net:/var/git/api

Diffstat:
Mwireformats.rst | 20++++++++++++++++++++
1 file changed, 20 insertions(+), 0 deletions(-)

diff --git a/wireformats.rst b/wireformats.rst @@ -12,6 +12,26 @@ The information required for wire transfer depends on the type of wire transfer used. Since the wire transfers differ for each region, we document here the ones currently supported by the mint. +TEST +---- + +The TEST wire format is used for testing and for integration with Taler's +simple "bank" system which in the future might be useful to setup a bank +for a local / regional currency or accounting system. Using the TEST +wire format in combination with the Taler's bank, it is thus possible to +fully test the Taler system without using real currencies. The wire +format for "TEST" is very simple, in that it only specifies an account +number in a field "account_number". The account number given must be +a positive 53-bit integer. Additional fields may be present, but are +not required. + +For the merchant or mint to receive deposits through TEST, the deposit +request must thus contain a JSON object with the following fields: + + * `type`: the string constant `"TEST"` + * `account_number`: the account number of the merchant at the bank + + SEPA ----