Changes for page card-transaction

Last modified by David Persson on 2024/02/21 07:48
From version 46.1
edited by David Persson
on 2020/03/20 14:37
To version 47.1
edited by David Persson
on 2020/04/13 22:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -697,6 +697,24 @@
697 697  
698 698  == Problems ==
699 699  
700 +All errors from the api are returned in the form of "problems" (response body), except for the http status code itself.
701 +The problem object contain more detailed info on what the error is. The "type" property can be used to programmatically interpret the error as it contains a code definition of the problem.
702 +Other properties can be useful for logging and subsequent troubleshooting. Some problems are extended with additional parameters so it may be a good idea to log response body as raw data to include these.
703 +
704 +|=(% style="width: 456px;" %)Httpstatus|=(% style="width: 231px;" %)Problem type (code)|=(% style="width: 1313px;" %)Description
705 +|(% style="width:456px" %)ledger.card-transaction.validation-error|(% style="width:231px" %)400|(% style="width:1313px" %)occurs if any of the inputvalidation fails
706 +|(% style="width:456px" %)ledger.card-transaction.card-token-not-found|(% style="width:231px" %)400|(% style="width:1313px" %)Occurs on post towards "authorizations" when no card could be found according to the specified cardToken.
707 +|(% style="width:456px" %)ledger.card-transaction.seller-no-not-registered|(% style="width:231px" %)501|(% style="width:1313px" %)
708 +|(% style="width:456px" %)ledger.card-transaction.currency-not-supported|(% style="width:231px" %)422|(% style="width:1313px" %)
709 +|(% style="width:456px" %)ledger.card-transaction.company-not-configured|(% style="width:231px" %)501|(% style="width:1313px" %)
710 +|(% style="width:456px" %)ledger.card-transaction.duplicate-authorization|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if specified SourceAuthorizationTransactionId hase already has been used on another authorization
711 +|(% style="width:456px" %)ledger.card-transaction.duplicate-purchase|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if any of the references that is required to be unique already has been used on another purchase
712 +|(% style="width:456px" %)ledger.card-transaction.duplicate-cash-withdrawal|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if any of the references that is required to be unique already has been used on another cash-withdrawal
713 +|(% style="width:456px" %)ledger.card-transaction.duplicate-reversal|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if any of the references that is required to be unique already has been used on another reversal
714 +|(% style="width:456px" %)ledger.card-transaction.duplicate-correction|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if any of the references that is required to be unique already has been used on another correction
715 +|(% style="width:456px" %)ledger.card-transaction.insufficient-funds|(% style="width:231px" %)409|(% style="width:1313px" %)occurs if there is not enough funds in the account. Depending on the type of account, the reason may be that there is not enough prepaid funds or that the total debt (including the new authorization) exceeds the creditlimit of the account
716 +|(% style="width:456px" %) |(% style="width:231px" %) |(% style="width:1313px" %)
717 +
700 700  If an error occur or any validation failed, a "problem" response will be returned.
701 701  Below is a list of problems that can occur:
702 702