Changes for page card-transaction

Last modified by David Persson on 2024/02/21 07:48
From version 86.1
edited by Daniel Lofqvist
on 2022/06/01 10:23
To version 87.1
edited by Daniel Lofqvist
on 2022/06/01 10:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -59,7 +59,8 @@
59 59  
60 60  Most transactions follow the flow where a authorization is initially made and is later followed by a financial transaction, however there are cases with financial transactions without corresponding authorizations. The 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.
61 61  
62 -=== ===
62 +===
63 +Resource description ===
63 63  
64 64  Each resource in the API corresponds to its own route. All routes are structured according to a specific standard, explained below
65 65  
... ... @@ -80,11 +80,12 @@
80 80  (% class="table-bordered table-striped" %)
81 81  |=(% style="width: 488px;" %)Resource|=(% style="width: 2271px;" %)Identifier
82 82  |(% style="width:488px" %)LedgerNumber|(% style="width:2271px" %)XXX
83 -|(% style="width:488px" %)Accounts|(% style="width:2271px" %)NNN
84 +|(% style="width:488px" %)AuthorizationId|(% style="width:2271px" %)YYY
84 84  |(% style="width:488px" %)Bills|(% style="width:2271px" %)reminder-123
85 85  bill-456
86 -|(% style="width:488px" %)Cards|(% style="width:2271px" %)954c8699-b38f-47a2-b568-668b8837dad8
87 -274c8699-b38f-47a2-b568-668b8837dat7
87 +|(% style="width:488px" %)SourcePurchaseTransactionId|(% style="width:2271px" %)PPP
88 +|(% style="width:488px" %)SourceCashWithdrawalTransactionId|(% style="width:2271px" %)WWW
89 +|(% style="width:488px" %)SourceReversalTransactionId|(% style="width:2271px" %)RRR
88 88  
89 89  === Authorizations ===
90 90  
... ... @@ -293,7 +293,7 @@
293 293  ==== Get purchases ====
294 294  
295 295  {{code language="http" title="**Request**"}}
296 -GET /ledger/card-transaction/v1/XXX/purchases/YYY HTTP/1.1
298 +GET /ledger/card-transaction/v1/XXX/purchases/PPP HTTP/1.1
297 297  Host: -
298 298  Authorization: Bearer <Token>
299 299  Content-Type: application/json
... ... @@ -422,7 +422,7 @@
422 422  ==== Get cash-withdrawals ====
423 423  
424 424  {{code language="http" title="**Request**"}}
425 -GET /ledger/card-transaction/v1/XXX/cash-withdrawals/YYY HTTP/1.1
427 +GET /ledger/card-transaction/v1/XXX/cash-withdrawals/WWW HTTP/1.1
426 426  Host: -
427 427  Authorization: Bearer <Token>
428 428  Content-Type: application/json
... ... @@ -522,7 +522,7 @@
522 522  ==== Get reversals ====
523 523  
524 524  {{code language="http" title="**Request**"}}
525 -GET /ledger/card-transaction/v1/XXX/reversals/YYY HTTP/1.1
527 +GET /ledger/card-transaction/v1/XXX/reversals/RRR HTTP/1.1
526 526  Host: -
527 527  Authorization: Bearer <Token>
528 528  Content-Type: application/json
... ... @@ -590,7 +590,7 @@
590 590  ==== Create purchase corrections ====
591 591  
592 592  {{code language="http" title="**Request**"}}
593 -POST /ledger/card-transaction/v1/XXX/purchases/YYY/corrections HTTP/1.1
595 +POST /ledger/card-transaction/v1/XXX/purchases/PPP/corrections HTTP/1.1
594 594  Host: -
595 595  Authorization: Bearer <Token>
596 596  Content-Type: application/json
... ... @@ -609,7 +609,7 @@
609 609  ==== Create cash-withdrawal corrections ====
610 610  
611 611  {{code language="http" title="**Request**"}}
612 -POST /ledger/card-transaction/v1/XXX/cash-withdrawals/YYY/corrections HTTP/1.1
614 +POST /ledger/card-transaction/v1/XXX/cash-withdrawals/WWW/corrections HTTP/1.1
613 613  Host: -
614 614  Authorization: Bearer <Token>
615 615  Content-Type: application/json
... ... @@ -628,7 +628,7 @@
628 628  ==== Create reversal corrections ====
629 629  
630 630  {{code language="http" title="**Request**"}}
631 -POST /ledger/card-transaction/v1/XXX/reversals/YYY/corrections HTTP/1.1
633 +POST /ledger/card-transaction/v1/XXX/reversals/RRR/corrections HTTP/1.1
632 632  Host: -
633 633  Authorization: Bearer <Token>
634 634  Content-Type: application/json
... ... @@ -708,7 +708,7 @@
708 708  = Mapping card-transaction to credit-account =
709 709  
710 710  |=(% style="width: 233px;" %)Card Transaction Api (this api)|=(% style="width: 134px;" %)Type|=(% style="width: 256px;" %)Credit Account Api|=(% style="width: 1043px;" %)Description
711 -|(% 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 small small small small small small small small small small small small small small small small small small small small small small small small small small small small small" %)##reservedAmount##" property>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HAccounts]](%%).
713 +|(% 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 small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small small" %)##reservedAmount##" property>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HAccounts]](%%).
712 712  |(% 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.
713 713  |(% 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" %)(((
714 714  [[../transactions>>https://developer.payex.com/xwiki/wiki/developer/view/Main/credit-account/api/credit-account/#HTransactions]] (% class="small" %)##**"type" : "purchase"**##