Changes for page ../credit-account-onboarding

Last modified by David Persson on 2020/04/21 08:18

From version 53.1

edited by David Persson
on 2020/03/27 14:14

To version 53.2

edited by David Persson
on 2020/04/21 08:14

Change comment: There is no comment for this version

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -385,59
          +385,43 @@
  |=(% style="width: 215px;" %)Property|=(% style="width: 114px;" %)Data type|=(% style="width: 118px;" %)Format|=(% style="width: 586px;" %)Description
  |(% style="width:215px" %)createdAccount|(% style="width:114px" %)string|(% style="width:118px" %)Uri|(% style="width:586px" %)
++(% id="HProblems-1" %)
  == Problems ==
--If an error occur or any validation failed, a "problem" response will be returned.
--Below is a list of problems that can occur:
++All errors from the api are returned in the form of "problems" (response body), except for the http status code itself.
++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.
++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.
--**HttpStatus 401 Unauthorized**
++Problems of type validation does contain an additional list ("Problems") that describes exactly which parameter that failed the validation
--* Token expired
--* Token invalid
--* CompanyNumber does not match token
++(% id="HExample" %)
++=== Example ===
--**HttpStatus 400 Error**
--
--* Validation: Argument required
--* Validation: Invalid value
--
--**HttpStatus 422 Unprocessable entity**
--
--* Signing process ended unexpectedly
--* Customer or account creation failed
--* Signicat signing was not successful
--
--**HttpStatus 409 Conflict**
--
--* State expected to be [AwaitSigning]. Actual state: [XXXX]
--*
--
--**HttpStatus 501 NotImplemented**
--
--* CompanyNumber XXX not configured
--* SellerNumber XXX not configured at PayEx
--* CompanyNumber XXX missing configuration
--
--**HttpStatus 404 NotFound**
--
--* Resource not found
--
--Below is an example of a problem that will be returned if buyer##.nationalConsumerIdentifier.value## is not valid in the authorization post request.
--
  {{code language="http" title="**Response**"}}
  HTTP/1.1 400 Error
  Content-Type: application/problem+json
  {
--    "Type": "http://[DNS]/ledger/invoice-purchase/problems/validation",
--    "Title": "A validation error occurred",
--    "Status": 400,
--    "Instance": null,
--    "Detail": "A validation error occurred. Please fix the problems mentioned in the 'problems' property below.",
--    "Problems": [
--        {
--            "buyer.nationalConsumerIdentifier.value": "Not a valid SE nationalConsumerIdentifier"
--        }
--    ]
++   "Type" : "ledger.credit-account.validation",
++   "Title" : "A validation error occurred",
++   "Status" : 400,
++   "Instance" : "215d4206-ca35-4f43-85ad-169c8f6d4ec1",
++   "Detail" : "A validation error occurred. Please fix the problems mentioned in the 'problems' property below.",
++   "Problems" : [
++      {
++         "amount" : "Expected value between [0,01]-[79228162514264337593543950335] actual [0]"
++      }
++   ]
  }
  {{/code}}
++
++(% id="HProblemtypes" %)
++=== Problem types ===
++
++Note, each problem typecode is preceded by "ledger.credit-account." in this API, e.g. the error "validation" in the table below will appear as typecode "ledger.credit-account.validation".
++
++|=Problem type (code)|=Httpstatus|=Description
++|validation|400|occurs if any of the inputvalidation fails, it is described in the problem which parameter that failed the validation
++|account-profile-exists|404|occurs if the customer already has an account with the requested account profile
++
++