#jmny
unkempt cloak
dim steeple
Hi there
pseudo urchin
hello
dim steeple
How are you integrated for one-time payments currently?
pseudo urchin
homemade, without stripe element
with payment intent and charge , with a python sdk on server side
and token on client side
dim steeple
Okay so just a custom form. Sounds like Card Element?
pseudo urchin
yes but without card element i think, but with a custom form, on client side we call stripe to generate a token, and then call our server to do a "manual" payment with this token , our python code call strype to create a PaiementIntent
we use also a payment method directly with a registred payment method , to create a payment intent
like
intent = stripe.PaymentIntent.create(
payment_method=self.payment_method_id,
customer=self.user.stripe_customer,
amount=self.amount,
currency='eur',
confirmation_method='manual',
confirm=True,
return_url=return_url,
use_stripe_sdk=use_stripe_sdk,
metadata=metadata
)
i would like to use stripe billing, but i would like stripe billing only for subscription not for my existing ecommerce payment process
dim steeple
Okay but how are you creating the PaymentMethod? You are handling the raw PANs in your own form? Regardless, you mostly would do the same thing you are doing right now but isntead of creating a PaymentIntent, you create a Subscription: https://stripe.com/docs/api/subscriptions/create
pseudo urchin
ok thank you
dim steeple
Let me know if you have any questions about the specifics.
You can mostly follow our guide here: https://stripe.com/docs/billing/subscriptions/build-subscriptions?ui=elements
Except that if you aren't using one of our Elements then you would just ignore the part about passing the clientsecret and you would just create the Subscription with the PaymentMethod that you collected already from the client.
pseudo urchin
i will not have the subscription fee on my current PaymentIntent ? 0.4 or 0.8 %
but only on the subscription payment
dim steeple
Your one-off payment flow will not be affected