#stellarloony-subscription

1 messages · Page 1 of 1 (latest)

crimson iris
#

heya @heavy pewter, could you explain more on what you're trying to do?

heavy pewter
#

i am creating a subscription. First i create customer object

#

then a paymentMethod, which i attach to the customer

#

then the subscription

#

but if the payment requires authentication then the customer would be redirected to an authentication page

#

so how do i pass a return_url to which customer will b redirected after authentication?

crimson iris
#

it sounds like you're using the Payment Element to collect payment method details?

heavy pewter
#

no i'm not using Elements

crimson iris
#

can you share how you're collecting the payment method details?

heavy pewter
#

a form on client. when the details r submitted they r sent to backend

#

is that not a right way to do it?

crimson iris
#

it sounds like you are collecting the raw credit card numbers in your custom form and then using the Stripe API directly to tokenize the cards. We actively discourage you from doing this because by handling raw card numbers directly you become subject to the full PCI compliance standards. In your case this means you’d have to submit a SAQ D form annually to prove that you are PCI compliant [0]. It’s a 40 page form and trust me, not a headache you want to be dealing with.

You would want to use either Stripe Checkout or Payment Element which would make you eligible for the simplest PCI form - SAQ A. Using either the Stripe Checkout or Payment Element would also make it easy for you to enable 3DS.

[0] https://stripe.com/docs/security/guide#validating-pci-compliance

heavy pewter
#

ok thanks