feloe_wallet-manual-capture | Stripe Developers | Page 1

modern laurelBOT May 23, 2024, 5:01 PM

#

👋 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/1243247323128004661

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

drifting hound May 23, 2024, 5:04 PM

#

it can be inferred that Google Pay and Apple Pay do NOT support the ability to place a hold on a payment and then capture the funds later?
no that's not correct though I get why you think that. ApplePay and GooglePay work like a card and support manual capture

#

feloe_wallet-manual-capture

livid heath May 23, 2024, 5:07 PM

#

Ah ok that's great to hear. So in order to fix this error do I have to add these lines to my payment intent?

automatic_payment_methods: {
    enabled: false,
},

drifting hound May 23, 2024, 5:08 PM

#

Do you absolutely want to do card and ApplePay/GooglePay only and nothing else?
Because no, the better fix would be to handle the redirect as required and have a return_url

#

See https://docs.stripe.com/upgrades/manage-payment-methods

modern laurelBOT May 23, 2024, 5:15 PM

#

livid heath May 23, 2024, 5:18 PM

#

I guess I'm not understanding correctly.

Does this list include all the payment methods which support manual capture?

cards
Affirm
Afterpay
Cash App Pay
Klarna
PayPal
Apple Pay
GooglePay

glass pebble May 23, 2024, 5:20 PM

#

Hi 👋

I'm stepping in as my colleague needs to go soon.

Apple Pay and Google Pay are just wrappers around Card payment method types. So in our docs https://docs.stripe.com/payments/place-a-hold-on-a-payment-method#auth-capture-limitations when we say

Payment methods that support this include cards, Affirm, Afterpay, Cash App Pay, Klarna, and PayPal
that includes Apple/Google pay

livid heath May 23, 2024, 5:23 PM

#

Hello, hope you're having a great day.

So is it only Bank Redirects that require the return_url?

#

Or can you tell me which methods require the return_url?

glass pebble May 23, 2024, 5:26 PM

#

So is it only Bank Redirects that require the return_url?
No, that is not accurate. I recommend providing a return url

livid heath May 23, 2024, 5:27 PM

#

Where can I read more about how to handle the redirect?

#

Can you provide a list of the payment methods that typically redirect?

glass pebble May 23, 2024, 5:30 PM

#

If you are using Stripe.js we will handle the redirect for you. What is the workflow you are trying to develop?

livid heath May 23, 2024, 5:46 PM

#

The way it currently works is
user fills cart
goes to checkout
If logged in automatically select primary card or let user enter new card information
if not logged in present card form
user places order - calls stripe.createPaymentMethod()
api creates and confirms payment intent using the payment method id

Restaurant receives notification of new order
Restaurant accepts order and at this point the payment intent is captured

glass pebble May 23, 2024, 5:49 PM

#

So you are creating and confirming the payment intent with the method you just saved?

#

Is there a reason you don't create and save the payment method in the same API call as confirming the payment intent?

livid heath May 23, 2024, 5:58 PM

#

I'm using the Stripe Elements for the form

Client side code looks like this

stripe.createPaymentMethod({
  elements: paymentForm.value, // <-- the elements form
  params: {
    billing_details: {
      name: `${order.value.firstName} ${order.value.lastName}`,
      email: order.value.email,
      phone: `${order.value.phoneFormatted}` || undefined,
    },
  }
}).then( async (res) => {
  // POST api with id in body
  await placeOrder(res.paymentMethod.id)
})

Server side

createOrder() {
const stripeIntent = {
          amount: 100
          currency: 'USD',
          payment_method: paymentMethodId, // from request body
          confirmation_method: 'manual',
          confirm: true,
          // If a mobile client passes `useStripeSdk`, set `use_stripe_sdk=true`
          // to take advantage of new authentication features in mobile SDKs
          use_stripe_sdk: useStripeSdk,
          metadata: {},
          capture_method: 'manual',
        }
}

Further down in create order, if the user is logged in the payment method is attached to the user

glass pebble May 23, 2024, 5:59 PM

#

Okay, but I don't see any reason why you are going this route instead of saving the payment method as part of the payment flow like we show in this guide:
https://docs.stripe.com/payments/save-during-payment

livid heath May 23, 2024, 6:30 PM

#

Can we proceed without creating the Stripe customer? Ideally those are created when the user creates an account in our platform.

The difference I'm seeing is that the intent is created before creating the payment method?

The other big difference I see is the way the payment intent is captured. Currently we are using this method:

const transaction = await getStoredOrderDetails()
 const intent = await Stripe.paymentIntents.capture(transaction.stripeIntentId, {
        stripeAccount: account.stripeAccount,
      })

Would that no longer be usable?

glass pebble May 23, 2024, 6:32 PM

#

If you already know the customer ID you can just provide it instead of creating a new one.

For the capture request, you are using a Stripe Account header (Connect). You would need to make sure to use that for all your API requests .

livid heath May 23, 2024, 6:38 PM

#

Yes we provide that if the user is logged in but the users can checkout as guest so no customer is created

I'm seeing in step 7 another intent is created? Why is another payment intent created instead of capturing the original?

glass pebble May 23, 2024, 6:40 PM

#

If no customer is created then you don't save the payment method. In that case you can just use our canonical accept a payment guide: https://docs.stripe.com/payments/accept-a-payment

For step 7, we are showing how you can used the saved payment method in for a later payment.

livid heath May 23, 2024, 6:43 PM

#

I believe I was following a combination of that guide + https://docs.stripe.com/payments/place-a-hold-on-a-payment-method

Place a hold on a payment method

Separate payment authorization and capture to create a charge now, but capture funds later.

#

I was using version 12 of the API and updated to 15 without checking the breaking changes 😅

glass pebble May 23, 2024, 6:46 PM

#

Do you mean the stripe-node SDK? Our API version numbers use date formats. The most recent is 2024-04-10.

modern laurelBOT May 23, 2024, 6:46 PM

#

livid heath May 23, 2024, 6:47 PM

#

So if I understand correctly I can update my flow to:

allow the user to fill out the form
create the payment intent and return the secret
update the elements page to include the secret
call stripe.confirmPayment()

cursive knot May 23, 2024, 6:51 PM

#

Hey there, just stepping in as my colleague needs to step away.

That sounds mostly correct, though I don't think you need a step here:

update the elements page to include the secret
Instead you end up passing the clientSecret as a parameter in confirmPayment

livid heath May 23, 2024, 6:54 PM

#

He grew tired of my million questions. I understand I would too 😅

If I have to any questions after updating my code ( I have to step away to a meeting) should I open a new thread or will this one remain open?

cursive knot May 23, 2024, 6:58 PM

#

This will be open for a bit longer, but you can also ask again if its after we've closed it 🙂

#

If you're trying it right now, feel free to share any more questions here

#feloe_wallet-manual-capture