Links

Client-Side Response Objects

The objects returned from the onSuccess and onError events in Flex Fields 2.0 are essentially the same object, the difference being the inclusion of an array for errors in the onError object.
Client-Side onSuccess Response
Client-Side onError Response
{
"installmentPlan": {
"installmentPlanNumber": "xxxxxxxxxxxxxxxxxxx",
"refOrderNumber": "xxx" //set by merchant during call to Initiate
},
"is3d": true, //indicates if 3DS was performed
"redirectUrl": "", // shows URL set during call to Initiate or empty
"traceId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" //Splitit uses this number to look up specific historical operations for troubleshooting
}
{
"errors": [{
"code": "641-F", //for example, could be any code
"description": "3D secure verification was not completed successfully.", //for example, could be any description
"fieldTypes": [], // Splitit internal field
"showError": true, // whether error will be shown to client or not (some aren't relevant)
"source": "3ds" //origination of error, see below
}],
"installmentPlan": {
"installmentPlanNumber": "xxxxxxxxxxxxxxxxxxx",
"refOrderNumber": "xxx" //set by merchant during call to Initiate
},
"is3d": true, //indicates if 3DS was performed
"redirectUrl": "", // shows URL set during call to Initiate or empty
"traceId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" //Splitit uses this number to look up specific historical operations for troubleshooting
}
Note that the parameter source in Error can be either:
  • client_validation (a front-end error, usually related to form fields)
  • server_validation (related to the Initiate API call, i.e. a missing BIN or debits not accepted)
  • 3ds (related to 3DS validation)
  • payment_error (error happened during authorization, not 3DS related)
  • update_details (error while updating customer details)
  • other
Last modified 5mo ago