Why is billTo element required for a call to ARBCreateSubscriptionRequest? EG response:
{
"messages": {
"resultCode": "Error",
"message": [
{
"code": "E00014",
"text": "Bill-To First Name is required."
},
{
"code": "E00014",
"text": "Bill-To Last Name is required."
}
]
}
}
Request code:
{
"ARBCreateSubscriptionRequest": {
"merchantAuthentication": {
"name": "XXXXXX",
"transactionKey": "XXXXXXXXXXXXXXX"
},
"refId": "123456",
"subscription": {
"name": "Sample subscription",
"paymentSchedule": {
"interval": {
"length": "1",
"unit": "months"
},
"startDate": "2020-08-30",
"totalOccurrences": "12",
"trialOccurrences": "1"
},
"amount": "10.29",
"trialAmount": "0.00",
"payment": {
"creditCard": {
"cardNumber": "4111111111111111",
"expirationDate": "2020-12"
}
},
"customer": {
"email": "john@yahoo.com",
},
"billTo": {
"firstName": "John",
"lastName": "Smith"
}
}
}
01-02-2019 09:50 AM
Hi vinniyo,
When an ARB subscription is created a CIM customer profile and payment profile is also created. Obviously, this is done in the background of the call and not visible to the user but the profile ID and payment profile ID are returned with the ARBCreateSubscriptionResponse.
When a subscription, and the associated customer profile, is created any required form fields specified in the Payment Form settings of the Merchant Interface will be required to be included within the creation/update request as well, as transactions which process from this feature will require this field data to be successful, regardless of whether they will be used or not within the ARB subscription.
To edit the Payment Form Field requirement settings:
While we would recommend that you include first name, last name and bill to address fields with ARB subscriptions, if you choose not to do so you can remove the field requirements from the Payment Form settings in the Merchant Interface and use your own methods of requiring this data on your form(s).
I hope this information is helpful.
Thank you,
Elaine
01-03-2019 10:37 AM