Changes for page card-transaction
Last modified by David Persson on 2024/02/21 07:48
From version 5.1
edited by David Persson
on 2020/02/19 22:09
on 2020/02/19 22:09
To version 6.1
edited by David Persson
on 2020/02/20 08:42
on 2020/02/20 08:42
Change comment: There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -9,8 +9,6 @@ 9 9 (% class="lead" %) 10 10 The credit account acquiring api contains functions that are used in payment scenarios: online, in-store and offline. Before transactions can be created an account must exists. 11 11 12 -(% class="lead" %) 13 -[[image:1581023647237-858.png||height="362" width="511"]] 14 14 15 15 ---- 16 16 ... ... @@ -18,11 +18,11 @@ 18 18 19 19 2020-02-03 20 20 Renamed parameters 21 -seller CaptureTransactionId -> sourceCaptureTransactionId19 +sellerPurchaseTransactionId -> sourcePurchaseTransactionId 22 22 sellerReversalTransactionId -> sourceReversalTransactionId 23 23 24 24 2020-01-30 25 -Added "reversals" resource to use when reversal is made with card and the original capture cannot be referenced.23 +Added "reversals" resource to use when reversal is made with card and the original Purchase cannot be referenced. 26 26 27 27 (% class="wikigeneratedid" %) 28 28 2020-01-30 ... ... @@ -31,7 +31,7 @@ 31 31 == Authorizations == 32 32 33 33 (% class="wikigeneratedid" %) 34 -An authorization is made to try to use an account for payment. A successful authorization leads to a reservation on the account, the account is identified through the **cardToken** or the **accountNo**. The authorization is not a financial transaction, to make the financial transaction a capture must posted on the authorization.32 +An authorization is made to try to use an account for payment. A successful authorization leads to a reservation on the account, the account is identified through the **cardToken** or the **accountNo**. The authorization is not a financial transaction, to make the financial transaction a Purchase must posted on the authorization. 35 35 36 36 ==== Post authorizations ==== 37 37 ... ... @@ -100,7 +100,7 @@ 100 100 "parentHREF": "/", 101 101 "operations": [ 102 102 { 103 - "rel": "create- capture",101 + "rel": "create-Purchase", 104 104 "method": "post", 105 105 "href": "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/purchases" 106 106 }, ... ... @@ -120,14 +120,14 @@ 120 120 |=(% style="width: 215px;" %)Property|=(% style="width: 114px;" %)Data type|=(% style="width: 118px;" %)Format|=(% style="width: 586px;" %)Description 121 121 |(% style="width:215px" %)@id |(% style="width:114px" %)string|(% style="width:118px" %)Uri |(% style="width:586px" %) 122 122 |(% style="width:215px" %)sourceAuthorizationTransactionId|(% style="width:114px" %)string|(% style="width:118px" %)Maxlength: 50|(% style="width:586px" %)Unique identifier of the specific authorization, generated by source (typically the integrating system) 123 -|(% style="width:215px" %)authorizationId|(% style="width:114px" %)string|(% style="width:118px" %)Maxlength: 6|(% style="width:586px" %)Unique identifier of the authorization, generated by PayEx. Should be stored and must be used in capture121 +|(% style="width:215px" %)authorizationId|(% style="width:114px" %)string|(% style="width:118px" %)Maxlength: 6|(% style="width:586px" %)Unique identifier of the authorization, generated by PayEx. Should be stored and must be used in Purchase 124 124 |(% style="width:215px" %)sellerNumber|(% style="width:114px" %)string|(% style="width:118px" %)Maxlength: 15|(% style="width:586px" %)Identifier of the current seller/merchant 125 125 |(% style="width:215px" %)cardToken|(% style="width:114px" %)string|(% style="width:118px" %) |(% style="width:586px" %)identifier of the card. The aurhotization is made on the account that the card is linked to 126 126 |(% style="width:215px" %)accountNo|(% style="width:114px" %)string|(% style="width:118px" %) |(% style="width:586px" %)identifier of the account 127 127 |(% style="width:215px" %)pointOfSale|(% style="width:114px" %)string|(% style="width:118px" %)Maxlength: 50|(% style="width:586px" %)Name of the location/point/shop of sale, will be returned in reservation resource 128 -|(% style="width:215px" %)validToDate|(% style="width:114px" %)date|(% style="width:118px" %)[[ISO 8601>>url:http://en.wikipedia.org/wiki/ISO_8601||rel="noreferrer" title="ISO8601 on Wikipedia"]]|(% style="width:586px" %) Capture can not be executed after this date126 +|(% style="width:215px" %)validToDate|(% style="width:114px" %)date|(% style="width:118px" %)[[ISO 8601>>url:http://en.wikipedia.org/wiki/ISO_8601||rel="noreferrer" title="ISO8601 on Wikipedia"]]|(% style="width:586px" %)Purchase can not be executed after this date 129 129 |(% style="width:215px" %)authorizeAmount|(% style="width:114px" %)decimal|(% style="width:118px" %)Amount|(% style="width:586px" %)Original authorized amount 130 -|(% style="width:215px" %)remainingAmount|(% style="width:114px" %)decimal|(% style="width:118px" %)Amount|(% style="width:586px" %)Amount left on the authorization that can be captured128 +|(% style="width:215px" %)remainingAmount|(% style="width:114px" %)decimal|(% style="width:118px" %)Amount|(% style="width:586px" %)Amount left on the authorization that can be Purchased 131 131 |(% style="width:215px" %)currency|(% style="width:114px" %)string|(% style="width:118px" %)[[ISO 4217>>url:https://sv.wikipedia.org/wiki/ISO_4217]]|(% style="width:586px" %) 132 132 |(% style="width:215px" %)purchases|(% style="width:114px" %)string|(% style="width:118px" %)Uri|(% style="width:586px" %) 133 133 |(% style="width:215px" %)cancellations|(% style="width:114px" %)string|(% style="width:118px" %)Uri|(% style="width:586px" %) ... ... @@ -145,7 +145,7 @@ 145 145 Content-Type: application/json 146 146 147 147 { 148 - "source CaptureTransactionId" : "534313",146 + "sourcePurchaseTransactionId" : "534313", 149 149 "sellerReceiptId": "2019-11-28", 150 150 "additionalReferences":{ 151 151 "acquirerBatchId": "fdsfsdfsd", ... ... @@ -183,7 +183,7 @@ 183 183 184 184 { 185 185 "description": "stora butiken test, köpref. 12345689", 186 - "source CaptureTransactionId" : "534313",184 + "sourcePurchaseTransactionId" : "534313", 187 187 "additionalReferences":{ 188 188 "acquirerBatchId": "fdsfsdfsd", 189 189 "acquirerTransactionId" : "534313", ... ... @@ -191,7 +191,7 @@ 191 191 "sellerReceiptId": "12345689", 192 192 "amount": 200.0, 193 193 "corrections": "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/purchases/YYY/corrections", 194 - "@id": "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/ capture/YYY",192 + "@id": "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/Purchase/YYY", 195 195 "parentHREF": "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN", 196 196 "operations": [ 197 197 { ... ... @@ -208,10 +208,10 @@ 208 208 (% class="table-bordered table-striped" %) 209 209 |=(% style="width: 337px;" %)Property|=(% style="width: 121px;" %)Data type|=(% style="width: 164px;" %)Format|=(% style="width: 1156px;" %)Description 210 210 |(% style="width:337px" %)@id |(% style="width:121px" %)string|(% style="width:164px" %)Uri|(% style="width:1156px" %) 211 -|(% style="width:337px" %)description|(% style="width:121px" %)string|(% style="width:164px" %)Maxlength: 200|(% style="width:1156px" %)Describes the current capture (derives from info sent in the authorization), may be printed on the bill, output only209 +|(% style="width:337px" %)description|(% style="width:121px" %)string|(% style="width:164px" %)Maxlength: 200|(% style="width:1156px" %)Describes the current Purchase (derives from info sent in the authorization), may be printed on the bill, output only 212 212 |(% style="width:337px" %)((( 213 -(% style="background-color:transparent" %)source CaptureTransactionId214 -)))|(% style="width:121px" %)string|(% style="width:164px" %)Maxlength: 50|(% style="width:1156px" %)Unique identifier of the capture transaction211 +(% style="background-color:transparent" %)sourcePurchaseTransactionId 212 +)))|(% style="width:121px" %)string|(% style="width:164px" %)Maxlength: 50|(% style="width:1156px" %)Unique identifier of the Purchase transaction 215 215 |(% style="width:337px" %)((( 216 216 additionalReferences.acquirerBatchId 217 217 )))|(% style="width:121px" %)string|(% style="width:164px" %)Maxlength: 50|(% style="width:1156px" %)Used for reconciling acquirer transactions. See [[RKHA21>>||anchor="HRKHA21format"]] section on this page for more information ... ... @@ -224,7 +224,7 @@ 224 224 225 225 == Offline-purchases == 226 226 227 -Offline capture transactions can be used when the point of sales cannot connect to the acquiring api to perform standard authorizations. Offline purchases can cause the charged credit account to exceed the account limits. Offline purchases are always limited by agreement. Different acquiring terms apply for offline-purchases compared to standard authorization -> purchases.225 +Offline Purchase transactions can be used when the point of sales cannot connect to the acquiring api to perform standard authorizations. Offline purchases can cause the charged credit account to exceed the account limits. Offline purchases are always limited by agreement. Different acquiring terms apply for offline-purchases compared to standard authorization -> purchases. 228 228 229 229 (% class="box warningmessage" %) 230 230 ((( ... ... @@ -241,7 +241,7 @@ 241 241 242 242 { 243 243 "pointOfSale": "stora butiken test, köpref. 12345689", 244 - "source CaptureTransactionId" : "534313",242 + "sourcePurchaseTransactionId" : "534313", 245 245 "additionalReferences":{ 246 246 "acquirerBatchId": "fdsfsdfsd", 247 247 "acquirerTransactionId" : "534313", ... ... @@ -250,7 +250,7 @@ 250 250 "sellerNumber" : "654", 251 251 "cardToken" : "1564316498964156", 252 252 "accountToken" : null, 253 - " captureAmount": 300.0,251 + "PurchaseAmount": 300.0, 254 254 "currency": "SEK", 255 255 "@id" : "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/purchases/YYY", 256 256 "credits" : "/ledger/credit-account-acquiring/v1/XXX/authorizations/NNN/purchases/YYY/credits", ... ... @@ -262,8 +262,8 @@ 262 262 263 263 (% class="box successmessage" %) 264 264 ((( 265 -**Note: **The resource created from POST calls towards "offline- capture" operation is actually a "capture" resource, not "offline-capture".266 -Execute GET calls to the capture resource to retreive previously made offline-purchases263 +**Note: **The resource created from POST calls towards "offline-Purchase" operation is actually a "Purchase" resource, not "offline-Purchase". 264 +Execute GET calls to the Purchase resource to retreive previously made offline-purchases 267 267 ))) 268 268 269 269 ==== Get offline-purchases ==== ... ... @@ -389,7 +389,7 @@ 389 389 390 390 == corrections == 391 391 392 -Used to reverse a capture transaction390 +Used to reverse a Purchase transaction 393 393 394 394 ==== Create corrections ==== 395 395 ... ... @@ -566,7 +566,7 @@ 566 566 * Invoice already authorized 567 567 * Duplicate InvoiceNumber 568 568 * Authorization is cancelled 569 -* Authorization already captured567 +* Authorization already Purchased 570 570 * Authorization has expired 571 571 * Insufficient debited amount XXX 572 572