We want to process payments from buyers to sellers with us being a 3rd party on our website. The Payments API seems to achieve this and even allow us to take a small fee. However, it is very important to our sellers to make sure that there is a match between payment/billing address and the shipping…

:wave: Currently ZIP or postal code matching, also known as the Address Verification System (AVS), is what is sent to the card network and is a factor that our fraud prevention models consider when assessing risk. Based on seller feedback, we found that rejecting payments based on AVS mismatches alo…

Thanks @Bryan-Square : You can use our APIs to collect that information however validating it would need to be a function of your application To be clear, what we need to compare is the payment address (assoc with the card) to the shipping address (which we can collect). Our vendors will not wa…

Currently there isn’t a way to get the address associated to the card making the payment unless you collect it. That information isn’t required when processing a payment.

@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 t…

You’re right, you can collect all the information from the customer however there isn’t anything within Square that does an address check other than the AVS check when a card is being processed. Square doesn’t get the address associated to the customers card from the card network. If your customers…

Thank you for your prompt replies. As far as I can tell, the ONLY benefit we are getting is the AVS check. So I need to understand more about AVS because it’s the only thing ensuring that the billing address which we collect credible. If AVS check doesn’t do what we expect, then we are deceived i…

Follow up question: [image] Bryan-Square: If the data points to an unintentional mistype, we’ll approve the payment; if it appears fraudulent, we’ll decline it. So if AVS fails, and you still approve the payment, will the response or any API data we have access to indicate that AVS failed? …

Looks like similar concerns over here: [image] CVV and AVS returning as NOT_CHECKED Questions We are using the PHP SDK. The form displays a field for postcode and cvv, however the return we receive is CVV_NOT_CHECKED and AVS_NOT_CHECKED. How can we force the API to check …

And more related concerns here: [image] Square Payment How to validate postal code. Currently Postal Code is not... Questions No, we do not provide the success/failure value for expiration date at this time. …

I wouldn’t rely on AVS checks. I’m trying to understand what you’re trying to solve for? If you worried about fraud I’d recommend using Risk Manager and 3D Secure for the payments. You can set rules and verify the buyer. :slightly_smiling_face:

How to verify Billing Address in Payments API?

Questions

jplehmann March 30, 2022, 9:19pm 9

Looks like similar concerns over here:

Topic		Replies	Views
Square Risk Manager vs errors caught by createPayment; postal vs full address Questions payments-api	3	725	July 15, 2022
Card Verification for Card Not Present Transactions Questions	1	642	April 23, 2020
ADDRESS_VERIFICATION_FAILURE error when create payment Questions payments-api	7	801	June 4, 2024
Some card transactions failing that really shouldn't! Questions payments-api , payment-form	11	2862	October 4, 2022
CVV and AVS returning as NOT_CHECKED Questions	10	2930	January 31, 2022

How to verify Billing Address in Payments API?

Related topics