@Bryan-Square that’s what I’m trying to understand then… You said “You can use our APIs to collect that information however validating it would need to be a function of your application”.
So what information can I collect from your API? It sounds like I cannot collect what I need in order to do the validation. Do you understand our confusion?
Either, I need Square to tell me the payment address (or zip) so my app can compare it to the shipping address…
Or, I need to be able to get an address from the buyer (like billing address), and give it to Square and have Square validate it for me. That was where I had started the conversation, but it is unclear to me how the validation on Square’s side works. I don’t see why it would be difficult for Square to just return an attribute that tells us if the address or postal code from the supplied billing address matched the payment address. Instead right now, we have to go off a “risk level” of low/med/high? So we have to assume that medium means it didn’t match? Please clarify.
Thanks!