taler-docs

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

commit f57587f0311cc4e5ae14d79bebd4c24d0ab0cde8
parent 3580482a11c47e76ae922173cf381b2ddedc9dc9
Author: Christian Blättler <blatc2@bfh.ch>
Date:   Fri, 19 Apr 2024 10:48:39 +0200

fix typo

Diffstat:
Mcore/api-bank-integration.rst | 20++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/core/api-bank-integration.rst b/core/api-bank-integration.rst @@ -151,7 +151,7 @@ for the withdrawal operation (the ``WITHDRAWAL_ID``) to interact with the withdr // Does not guarantee that the funds have arrived at the exchange already. transfer_done: boolean; } - + .. http:post:: /withdrawal-operation/$WITHDRAWAL_ID @@ -210,37 +210,37 @@ for the withdrawal operation (the ``WITHDRAWAL_ID``) to interact with the withdr Allows a provider to notify the Bank about the payment. This will trigger a payment attestation at the provider, which eventually confirms the payment and allows the - withdrawal. The API is idempotent, meaning sending a payment + withdrawal. The API is idempotent, meaning sending a payment notification for the same ``WITHDRAWAL_ID`` return successfuly but not change anything. Attention: A bank shall **never** just accept the payment directly but instead attest the payment using provider specific attestation logic! **Request:** - + .. ts:def:: BankWithdrawalConfirmationRequest interface WithdrawalConfirmationRequest { // The provider specific transaction identifier. - // This identifier is used by the bank to attest the + // This identifier is used by the bank to attest the // payment at the providers backend. provider_transaction_id: string; // An identifier, which identifies the device // processing the payment for the withdrawal - // triggering the confirmation (e.g. Terminal + // triggering the confirmation (e.g. Terminal // or ATM). This is needed to link the withdrawal // to a terminal owned by a specific provider. // This will decide about how the withdrawal - // is attested. The device must be known to + // is attested. The device must be known to // the exchange and be somehow registered. terminal_id: number; - - // The amount to withdraw. Fees are to be sent in the + + // The amount to withdraw. Fees are to be sent in the // separate field 'fees' and not included in the amount. amount: Amount; - - // The fees, the customer payed at the providers facility. + + // The fees, the customer paid at the providers facility. card_fees: Amount; }