matrix-block-postcode | Stripe Developers | Page 1

finite vigil Jan 31, 2022, 1:12 PM

#

Hey there! Are you using our Checkout solution, or your own custom flow?

muted lintel Jan 31, 2022, 1:14 PM

#

hello

#

i am using standard checkout

finite vigil Jan 31, 2022, 1:15 PM

#

This? https://stripe.com/docs/payments/checkout

Stripe Checkout

The quickest way to build conversion-optimized payment forms, hosted on Stripe.

muted lintel Jan 31, 2022, 1:15 PM

#

yes

finite vigil Jan 31, 2022, 1:18 PM

#

Got it. Yeah, as that's a hosted solution you can't really implement any additional controls like that. Instead you'd rely on a Radar rule to block those payments: https://stripe.com/docs/radar/rules

Rules

Write fraud prevention rules specific to your business.

muted lintel Jan 31, 2022, 1:20 PM

#

ok, is there a way to ask the customer to add a postcode before checkout AND pass that info to checkout prepopulating the checkout session?

#

I would like to avoid asking the same info 2 times

#

the radar rules seems more focused at security. in my case it is an opertional matter - i have a takeaway business and they can deliver only to certain post codes

finite vigil Jan 31, 2022, 1:22 PM

#

muted lintel ok, is there a way to ask the customer to add a postcode before checkout AND pas...

Not with Checkout, no

#

I guess in this case you'd instead implement an auth and capture flow for the payment with Checkout. Then when the Checkout Session is completed, listen for the checkout.session.completed event and either cancel the associated Payment Intent, or capture it depending on if the postcode is within your delivery range

muted lintel Jan 31, 2022, 1:24 PM

#

ok thanks

finite vigil Jan 31, 2022, 1:24 PM

#

More here: https://stripe.com/docs/payments/capture-later

Place a hold on a card

Separate authorization and capture to create a charge now, but capture funds later.

#matrix-block-postcode