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

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

Ruthinium44 — Thu, 27 Jun 2019 19:14:05 GMT

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.

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

mmcguire — Tue, 02 Jul 2019 17:11:33 GMT

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.

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

eetuser007 — Mon, 17 Aug 2020 12:17:33 GMT

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"

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

JoelAmos — Tue, 13 Apr 2021 20:48:41 GMT

@mmcguire wrote:
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.

Shouldn't there be an setting, then, for requiring first/last name on the payment profile? Currently, first/last name is bundled with billing address, but some of us need to have an optional billing address.