#coinbeastcrypto

1 messages · Page 1 of 1 (latest)

uncut oreBOT
lavish yoke
#

Hello! What's up?

ivory epoch
#

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?

lavish yoke
#

Then you can reuse it later by creating a Payment Intent instead of a Payment Link.

ivory epoch
#

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?

lavish yoke
#

No.

#

It will bypass the Payment Link entirely. There will not be a Payment Link.

ivory epoch
#

Is there anyway to generate a payment link with the payment method pre-populated?

lavish yoke
#

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.

ivory epoch
#

Is there a way to listen to the intent without that?

lavish yoke
#

What do you mean by listen?

ivory epoch
#

Ok. Is there a way to do this via the widget?

lavish yoke
#

What widget?

ivory epoch
#

Via the Stripe dashboard without requiring code?

lavish yoke
#

No.

#

This would require code.

ivory epoch
#

is there a way to listen to the intents via the stripe widget
we will have code to listen to intents

lavish yoke
#

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.

ivory epoch
uncut oreBOT
ivory epoch
#

by widget meaning the payment link UI

lavish yoke
#

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.

ivory epoch
#

how about if we create the payment link with payment_intent_data.setup_future_usage set as on_session

lavish yoke
#

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.

ivory epoch
#

so we need to handle the payment intent and the customer data?

ivory epoch
#

is that possible with an express account or does it have to be a custom implementation?

tired silo
#

Works with Express accounts as well

ivory epoch
#

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?

tired silo
#

If you are re-using a user's card details usually it is because they are logged in