- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Using HOSTED PAYMENT FORM against the Production's environment we're receiving the following exception:
PaymentProfile cannot be sent with billing data.
This was working without hiccups against the sandbox.
Which could be the source of the issue. We're seeing clearly that once presented the hosted form shows the available payment methods under the passed customer's profile.
Thanks in advance for any help that can be provided,
Gabe.
Solved! Go to Solution.
01-09-2018 04:01 PM
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was able to figure out that if I include the setting:
settingNameEnum.hostedPaymentBillingAddressOptions.ToString() in show = true
and a profile has been provided then that error raises.
Now the exception thrown by the API it's not clear at all about the source of the error.
Thanks,
Gabe.
01-10-2018 08:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any ideas what could be wrong here ?
Thanks in advance,
Gabe.
01-10-2018 08:08 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was able to figure out that if I include the setting:
settingNameEnum.hostedPaymentBillingAddressOptions.ToString() in show = true
and a profile has been provided then that error raises.
Now the exception thrown by the API it's not clear at all about the source of the error.
Thanks,
Gabe.
01-10-2018 08:28 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @ggramajo
The team is aware of this issue and will be fixing it in the upcoming release .
For now as a workaround please pass
settingNameEnum.hostedPaymentBillingAddressOptions.ToString() in show = false in the settings .
Send feedback at developer_feedback@authorize.net
01-10-2018 11:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi ,
I imagine that you guys are aware that if I try to add a new card to the passed profile under those conditions it's going to return an AVS Mismatch exception.
Thanks,
Gabe.
01-10-2018 12:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you provide more details on this use case ?
It should be able to add a new card in the customer profile without passing BillTO .
Send feedback at developer_feedback@authorize.net
01-10-2018 02:45 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi anuragg:
So it's really simple to reproduce if you pass the setting in conjunction with a profile id:
settings[4] = new settingType();
settings[4].settingName = settingNameEnum.hostedPaymentBillingAddressOptions.ToString();
settings[4].settingValue = "{\"show\": true}";
and you try to add a payment type (new cc) then the error is sourced in an AVS mismatch while processing the data on the credit card holder's information: address, city, etc. We confimed this with different credit cards for which we're 100% sure the right information is provided and it's always the same outcome.
Regards,
Gabe.
01-11-2018 08:33 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also anuragg:
Can you guys provide an ETA of when the problem is going to be resolved ?
Thanks in advance,
Gabe.
01-11-2018 09:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any updates to the questions in here ?
01-24-2018 09:02 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We just experienced this bug as well with a customer.
Any updates on the fix?
02-13-2018 09:09 AM

