Changes for page card-transaction
Last modified by David Persson on 2024/02/21 07:48
From version 64.1
edited by Mikael Widström
on 2020/04/20 14:35
on 2020/04/20 14:35
To version 65.1
edited by Mikael Widström
on 2020/04/20 14:37
on 2020/04/20 14:37
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -31,9 +31,9 @@ 31 31 The card transaction api is used for making card payments against credit-accounts, it uses card terminology. All card transactions ends up on a credit-account that maintains all balances. 32 32 ))) 33 33 34 -The card transactions has two major concepts: 35 - 34 +The card transactions has two major concepts Authorizations and Financial Transactions. 36 36 36 + 37 37 ===== **Authorizations** ===== 38 38 39 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". ... ... @@ -53,7 +53,7 @@ 53 53 === Mapping card-transaction to credit-account === 54 54 55 55 |=(% style="width: 233px;" %)Card Transaction Api (this api)|=(% style="width: 134px;" %)Type|=(% style="width: 256px;" %)Credit Account Api|=(% style="width: 1043px;" %)Description 56 -|(% style="width:233px" %)[[../authorizations>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HAuthorizations]]|(% style="width:134px" %)(% class="small" %)Authorization|(% style="width:256px" %)[[../reservations>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HReservations]]|(% style="width:1043px" %)(% class="small" %)Successful authorizations will end up as reservations in the credit-account api. The credit account/accounts api will also include a property with the total reservation amount that has not yet received a corresponding financial transaction in [[the "(% class="small small small" %)##reservedAmount##" property>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HAccounts]](%%). 56 +|(% style="width:233px" %)[[../authorizations>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HAuthorizations]]|(% style="width:134px" %)(% class="small" %)Authorization|(% style="width:256px" %)[[../reservations>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HReservations]]|(% style="width:1043px" %)(% class="small" %)Successful authorizations will end up as reservations in the credit-account api. The credit account/accounts api will also include a property with the total reservation amount that has not yet received a corresponding financial transaction in [[the "(% class="small small small small" %)##reservedAmount##" property>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HAccounts]](%%). 57 57 |(% style="width:233px" %)[[../authorization/../cancellations>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HCancellations]]|(% style="width:134px" %)(% class="small" %)Authorization|(% style="width:256px" %)n/a|(% style="width:1043px" %)(% class="small" %)Cancellations are used to free up authorizations/reservations, if the consumer of the api know that a financial transaction will not occur. Authorizations automatically times-out after a configurable time. 58 58 |(% style="width:233px" %)[[../purchases>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/card-transaction/#HPurchases]]|(% style="width:134px" %)(% class="small" %)Financial Transaction|(% style="width:256px" %)((( 59 59 [[../transactions>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HTransactions]] (% class="small" %)##**"type" : "purchase"**## ... ... @@ -80,9 +80,8 @@ 80 80 Financial transactions of type purchase that do not have a corresponding authorization are usually subject to liability shift, meaning that if the transaction fails in the clearing the financial risk is transferred to the mechants. Financial transactions are batch processed in clearing files and do not occur in real time. 81 81 ))) 82 82 83 +== == 83 83 84 -== == 85 - 86 86 == 87 87 Authorizations == 88 88 ... ... @@ -133,7 +133,7 @@ 133 133 Content-Type: application/json 134 134 {{/code}} 135 135 136 -==== 135 +==== ==== 137 137 138 138 {{code language="http" title="**Response**"}} 139 139 HTTP/1.1 200 OK