Hi @tbas55,
Thanks for the XML. That's really helpful!
Looking back at the previous code you posted, I'm guessing that's the output of our .Net SDK. That SDK will look like it's putting in things that it doesn't actually send down the wire. So, just outputting an object to JSON is a little confusing for me to look at. But, even that was enough for me to figure out what was happening once I tried a similar request on my end.
You're not specifying the hostedPaymentBillingAddressOptions setting (which would look like this:)
{
"settingName": "hostedPaymentBillingAddressOptions",
"settingValue": "{\"show\": true}"
},
In the Accept Hosted documentation, we document that setting as not being a required setting, and with a default of "true". And, just like you'd expect, if you don't send the setting, you do still see the form fields displayed. But, just like you've seen, when you fill them in nothing is passed on once you click the "Pay" button.
So, there's clearly a part of our code that treats the null value of that setting different than the explicit "true" value. I'll escalate this and see about getting it fixed.
To work around this, you have two options. The easiest is probably to explicitly send that hostedPaymentBillingAddressOptions setting set to true. Or, you can prepopulate the address information in the billTo element. If you do that, then the address fields are saved whether or not you have the hostedPaymentBillingAddressOptions setting present.
You mentioned that prepopulating never worked for you. I can't imagine why that would be the case, but we can look into that. First, try prepopulating now, and see if the same change that broke the earlier behavior for you might have changed something on that front.
This is a really good catch, and I'm very thankful you reported it. Thanks for being patient and jumping through the hoops necessary for us to figure it out.
