Changes for page card-transaction

Last modified by David Persson on 2024/02/21 07:48
From version 62.5
edited by Mikael Widström
on 2020/04/20 14:27
To version 63.1
edited by Mikael Widström
on 2020/04/20 14:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,10 +32,11 @@
32 32  )))
33 33  
34 34  The card transactions has two major concepts:
35 +
35 35  
36 36  ===== **Authorizations** =====
37 37  
38 -Validates if payments can be done, account has sufficient funds etc.. The authorizations will end up as reservations on the credit-account. Authorization will in most cases end up in financial transaction, a "Purchase".
39 +Validates if payments can be done, account has sufficient funds etc..The authorizations will end up as reservations on the credit-account. Authorization will in most cases end up in financial transaction, a "Purchase".
39 39  
40 40  Authorizations and Cancellations are the only real-time transactions, they take place instantly on at the point of sale (POS) (eg. cache register or online payment).
41 41  
... ... @@ -49,7 +49,6 @@
49 49  
50 50  Although most transactions follow the authorization > financial transaction flow, there are cases with financial transactions without corresponding authorizations. The most typical scenario is when a POS-Terminal loses connection with the internet. To prevent an all-stand-still at the point of sales, the cards can contain an offline-limit. The offline-limit restricts maximum amount of a purchase that can be made unauthorized. (% class="small" %)The offline-limit (if such exist) is regulated in the agreement between the card-issuer and the consumer.
51 51  
52 -
53 53  === Mapping card-transaction to credit-account ===
54 54  
55 55  |=(% style="width: 233px;" %)[[card-transaction api>>doc:]] (this api)|=(% style="width: 134px;" %)Type|=(% style="width: 256px;" %)[[credit-account api>>doc:Main.credit-account.api.credit-account.WebHome]]|=(% style="width: 1043px;" %)Description
... ... @@ -84,7 +84,8 @@
84 84  == ==
85 85  
86 86  (% class="wikigeneratedid" %)
87 -== Authorizations ==
87 +==
88 +Authorizations ==
88 88  
89 89  (% class="wikigeneratedid" %)
90 90  An authorization is done as the first step in using an account as payment. A successful authorization leads to a reservation on the account, the account is identified through the **cardToken.** The authorization is not a financial transaction, to make the financial transaction a Purchase (or other type of transaction) must be posted on the authorization.