#geo_best-practices
green prawnBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1465354263457693797
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
coarse ore
Hello
As of today, Terminal can't work as seamlessly as Elements with Subscriptions API.
You will need to save the payment details using the flow described here: https://docs.stripe.com/terminal/features/saving-payment-details/overview
And create the Subscriptions using the saved payment method on your server
cunning tapir
could you give me a small summary of how it would work?
coarse ore
1/ Customer is checking out in-person
2/ Your app is connected to the in-person Reader
3/ Customer taps/inserts/swipes their payment method that you save to their customer object (Using the guide I shared above)
4/ Once the payment method has been saved, you either set that payment method as customer's default payment method under invoice_settings.default_payment_method & then create a Subscription with the Customer ID specified in the API OR you create a Subscription + pass default_payment_method along with Customer ID via the API - https://docs.stripe.com/api/subscriptions/create
If you've not read the Terminal docs yet then you'd want to start here for how to set up the integration and connect to a Reader: https://docs.stripe.com/terminal/payments/setup-integration
Once you're done with "Connect to a Reader" step, you'd follow the guide about saving the payment details
cunning tapir
when paying with the reader, when does the customer get charged for the first payment? WIth elements is right away once the invoice is created, is it something similar with terminal?
coarse ore
If you create the Subscription with collection_method: 'charge_automatically' -> right away after the payment method has been saved then the customer should get charged ~immediately
cunning tapir
so if I'm reading this correctly
for my current flow is create subscription -> load Elements -> customer pays
for this new one is customer pays -> save payment -> create subscription
?
coarse ore
for this new one is customer pays -> save payment -> create subscription
customer taps/inserts/swipes their payment method -> save -> create subscription (this is where the customer technically gets charged)
cunning tapir
ahhh I see
And since I'm still using subscriptions, are invoices still created when paying with terminal, I assume so bc I'm still going to use the Subscriptions api correct?
I'm just wondering if I need to make changes to all the webhook listeners I currently have
coarse ore
Correct. While this flow seems as "one" to the customer, it is two completely separate flows behind the scenes.
1/ (In-person) flow to save the payment method
2/ (Online) Subscription creation
cunning tapir
got it, I'm going to give it a shot. Now that I at least have an idea on the flow I can fill in the datails by reading the guide you provided.
Thank you so much!