#peter-bacs

1 messages · Page 1 of 1 (latest)

strong musk
#

no, it's only supported through Checkout today

mossy copper
#

Right, so if we offer card payments using custom integration, we would need 2 flows?

#

When using checkout, do the same payment_intent webhooks come in, or is it done of the checkout webhook instead?

#

off*

#

Are there plans to roll BACS out via non-checkout process?

strong musk
strong musk
mossy copper
#

Why do you suggest using checkout?

#

We are running stripe connect

#

We like to keep the user on the site

strong musk
strong musk
# mossy copper Why do you suggest using checkout?

because it works with all payment methods, natively supports 3DSecure/Apple/Google Pay and we constantly add new features and payment methods to it and it's out default integration recommended to everyone

mossy copper
#

so the paymentElement is used for everything but BACS?

strong musk
#

as I mentioned there are ways to not use Checkout for it if you want, details shared above

mossy copper
#

Ok, for now though, we could ask the user what method they want, bacs or "anything else"

#

If they use bacs, then we go the checkout route

#

If they go anything else, we go the paymentElement route

#

bearing in mind 95% of our payments are card

#

Are the big differences in webhooks from checkout to custom integration

mossy copper
#

Ok, got it

#

Do many people mix and match Checkout with their own integration?

#

?

#

Presumably, we would still get the subscription webhooks in this scenario?

latent leaf
#

Hey, taking over for @strong musk

latent leaf
latent leaf
mossy copper
#

Ok, and in the case of a subscription payment requiring action

#

Would we need to direct them to Checkout again

#

Or is that rare?

latent leaf
#

You mean like requiring 3DS/auth?

#

You wouldn't direct them to Checkout no, as Checkout doesn't support recovery flows like that

#

There are emails you can configure that will send the customer to a hosted page to complete invoice payment