| Age | Commit message (Collapse) | Author |
|---|
|
That API has now a new 'ordering' flag that lets the
client choose what ordering the results should have:
ascending or descending.
In particular, this change adapted the fakebank and
tests logic to such introduction.
|
|
|
|
|
|
|
|
out-of-range
|
|
|
|
|
|
|
|
|
|
Add methods signatures to register merchants at banking institutions.
|
|
|
|
Now use the bank base *url* extracted
from the payto:// extractor.
|
|
Moving the extracted bank base URL into proper structure.
|
|
|
|
|
|
The conversion prepends http// or https://
depending on the port given beside the hostname.
If port is 433, then prepends https://, otherwise
prepends http://.
For now, the conversion was only necessary at
the /history bank lib.
|
|
|
|
|
|
|
|
This change enables using multiple wire plugins at the same time.
Also, we now distinguish between the wire plugin (i.e. EBICS or
taler_bank) and the wire method (i.e. SEPA or x-taler-bank) that
the wire plugin is implementing. The "taler-bank" wire method
was renamed from "test" to "x-taler-bank".
This also changes the format of the /wire response of the exchange,
as we now need to return multiple accounts. Note that wire fees
are specified per wire method, not per wire account.
taler-exchange-keyup now automatically signs all of the /wire
responses in the location specified by the configuration.
Account identification in wire plugins was changed to use
payto://-URLs instead of method-specific JSON fields. Signing
and validation of /wire responses was moved from each wire
plugin to a generic validation method in libtalerutil (crypto)
or libtalerjson (for JSON-formatted inputs).
Convenience methods were added to generate JSON for wire accounts
(salting, signing).
Various section and option names were adjusted to streamline the
configuration and make it more consistent overall. Documentation
was updated as well.
|
