Reply
Member
Posts: 2
Registered: ‎06-27-2019

Bill-To First and Last name required despite setting to not required in Payment Form - Fields

We have unchecked required for First and Last name in the "Payment Form - Fields" > "Customer Billing Information" section.

 

Despite this change, we still get an API error when creating a subscription that "Bill-To First Name is required" and "Bill-To Last Name is required".

 

It is our understanding that we should be able to create a subscription without needing these fields, but we are not currently able to do so.

Administrator
Posts: 165
Registered: ‎11-29-2017

Re: Bill-To First and Last name required despite setting to not required in Payment Form - Fields

Some processors require a bill to first and last name and the payment form settings are overridden by the processor requirements. It sounds like that is the case here.

 

For confirmation please check with support to verify your processor and if this rule applies.

Member
Posts: 1
Registered: ‎08-17-2020

Re: Bill-To First and Last name required despite setting to not required in Payment Form - Fields

We are getting the same error.

 

settings[1] = new settingType();
settings[1].settingName = settingNameEnum.hostedPaymentBillingAddressOptions.ToString();
settings[1].settingValue = "{\"show\": false, \"required\":false}";

 

We have set show billing address and required to "false" for hosted payment page iFrame parameters.

And we are not passing billing address in payment transaction request, it is working fine on sandbox.

 

When user enters credit/debit card details on hosted payment page on PRODUCTION and clicks "Pay" a validation message appears "Bill To First name required"