#aby_docs
woven zincBOT
👋 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/1262399880123514943
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
meager pond
using a card stored by us
Are you saying you have the card number stored on your end? Or are you referring to a card stored previously in Stripe?
meager pond
Got it. And to be clear, is this for a new integration you're building or existing? Do you collect card details from customer at the same time as you process the first payment, or are you wanting to collect card details first and then payment will happen sometime much later?
eternal gust
I mean, we process one payment, and then we save the customer information and payment method, and then some time later we want to perform a MIT
It's for a new integration
And the time window it deppens, but not sometime much later typically
Thank you for looking into it 🙂
meager pond
No problem. Just getting as much info as possible so I can link you the correct docs that explain better
How are you wanting to collect payment information (for the initial CIT)? On a checkout page on your site, or on a stripe-hosted page?
eternal gust
On a Stripe hosted page
meager pond
Ok, so I recommend you follow this doc then for that piece: https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted. When creating the checkout session, you'll need to pass payment_intent_data.setup_future_usage=off_session: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-payment_intent_data-setup_future_usage so that the payment method is saved and set up for future MIT's. Then, to charge the saved payment method later as an MIT, you'd create a payment intent, passing in that saved payment method id to charge: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-payment_method. You'd also want to pass off_session=true: https://docs.stripe.com/api/payment_intents/create#create_payment_intent-off_session.
eternal gust
Oh that's wonderful
Really appreciate it. In case we woudl have stored first that payment information on our end, then after one successful payment thorugh Stripe, and with that payment information already stored in Stripe (and correctly set up for future usage), we would be able to follow the flow you described anyways, right?
meager pond
In case we woudl have stored first that payment information on our end,
If you're talking about storing raw card information on your end, you'd need to be PCI compliant. You'd also need to reach out to our support team to provide the required documents to prove that and to have the ability to pass card numbers to our api enabled