#coinbeastcrypto
1 messages · Page 1 of 1 (latest)
Hello! What's up?
Hi Rubeus. I am using Stripe Express Connect. On behalf of my Connect accounts, I generate payment links each month and provide these to my Connect accounts' customers.
The challenge I am running into is that after a user decides to pay via ACH - Manual, and has to verifiy micro-deposits, the next month when we issue a payment link to this user, they have to verify micro-deposits again.
What's the cleanest way to save their payment method (ACH, Manual) so that they can use it again the next month?
You can set setup_future_usage on the Payment Links so the payment info provided is set up and stored for future use: https://stripe.com/docs/api/payment_links/payment_links/create#create_payment_link-payment_intent_data-setup_future_usage
Then you can reuse it later by creating a Payment Intent instead of a Payment Link.
If we create a payment intent, will there still be a payment link generated that the customer can see, with their payment method pre-populated where they can click "Pay" ?
Or will this bypass the payment link page altogether?
Is there anyway to generate a payment link with the payment method pre-populated?
No.
If you want your customer to confirm the payment you need to build your own UI on your own site that provides a way for them to authenticate themselves and then confirm the payment, which would trigger Payment Intent creation and confirmation using their saved Payment Method.
Is there a way to listen to the intent without that?
What do you mean by listen?
If you mean with webhooks, yeah, Payment Intents emit several Events: https://stripe.com/docs/payments/payment-intents/verifying-status#webhooks
Ok. Is there a way to do this via the widget?
What widget?
Via the Stripe dashboard without requiring code?
is there a way to listen to the intents via the stripe widget
we will have code to listen to intents
By widget you mean Dashboard? Not sure what you mean.
The fact that you keep using the word "widget" makes me think we're talking about different things.
by widget meaning the payment link UI
That looks like Stripe Checkout.
Ah, Payment Links. No, Payment Links are designed to accept new payment details, they can't use existing payment info.
Payment Links are also designed to be shared with many people and aren't associated with a specific person or their saved payment info.
how about if we create the payment link with payment_intent_data.setup_future_usage set as on_session
That will save their info for later use, but you can't use it later with a Payment Link.
You would use it later with a Payment Intent.
so we need to handle the payment intent and the customer data?
Yeah. You would do this: https://stripe.com/docs/payments/save-during-payment?platform=web#charge-saved-payment-method
is that possible with an express account or does it have to be a custom implementation?
Works with Express accounts as well
Ok, and so, is there a best practice or recommendation around authenticating users prior to providing them with a button to trigger this payment intent -- essentially to simulate the experience of Link with a saved credit card, just in this case, with saved ACH manual info?
If you are re-using a user's card details usually it is because they are logged in