When the API request is successful, you receive an HTTP 201 response. However, because a request initiates multiple actions, the 201 response contains additional information.
If all actions are successful, the status value is
SUCCESS
. When some actions are successful and others unsuccessful, the response includes
"status": "PARTIAL",
 and further details are included in the details object. The following table explains various scenarios that can trigger this message.
Detail Messages
Detail Messages Examples
Explanation
 
     "productInformationSetups": [
        {
            "organizationId": "071520211_t0026",
            "setups": {
                "payments": {
                    "recurringBilling": {
                        "configurationStatus": {
                            "status": "SUCCESS",
                            "reason": "NOT_APPLICABLE",
                            "message": "No configuration information is required"
                        },
                        "subscriptionStatus": {
                            "status": "SUCCESS",
                            "message": "success"
                       }
                    },
                    "cardProcessing": {
                        "subscriptionStatus": {
                             "status": "FAILURE",
                              "reason": "INVALID_DATA",
                              "message": "No features provided"                     
                    }
                },
                "commerceSolutions": {
                    "tokenManagement": {
                        "configurationStatus": {
                            "status": "FAILURE",
                            "reason": "NOT_FOUND",
                            "message": "Published profile not found"
                        },
                        "subscriptionStatus": {
                            "status": "SUCCESS",
                            "message": "success"
                        }
                    }
                }
            }
        }
    ]
The organization was successfully created, but one or more product subscription or configuration failed. This sometimes occurs because the submitted product is not enabled for this merchant account. 
  "productInformationSetups" : [ {
    {
      “field”:“subscritionInformation”,
      “reason”: “INVALID_DATA”,
      "reference": {organizationId}
    }
The organization was successfully created, but a product subscription failed due to invalid data in the request. As you can see, the value
subscritionInformation
 is missing a
p
, so the product subscription failed.
  "productInformationSetups" : [ {
    {
      "field": "fieldName",
      "reason": "Failure reason",
      "reference" "Transacting organization"
     }
The merchant organization and product configurations were successful, but the corresponding transacting organization failed.