#travis_02905_54090

1 messages · Page 1 of 1 (latest)

burnt heraldBOT
pastel patio
#

hello! let's start here

This one says it will allow it to be attached to a customer (it does) but subsequent attempts to use it will fail. In my testing, this card doesn't fail for me.
mind sharing the request ID for the Customer Attach and the subsequent payment creation (which doesn't fail)?

#

can help from there

atomic depot
#

sure give me a few mins to set one up

#

ok, request id is: req_QF6dYT9Iwh1EjA

#

not sure what you need id wise from the payment intent but this is the secret that came back with the response

#

pi_3NcZBlADt95j5Z0G1i1ndPy2_secret_OZmKpSiJPFcWV9doAkRaTUc9m

#

I can see the payment posted in my account

#

$200

#

it's canceled but my code does that currently

#

A new payment pi_3NcZBlADt95j5Z0G1i1ndPy2 for $200.00 USD was created

pastel patio
#

ah I see your mistake

#

you didn't confirm the PaymentIntent

#

it isn't "paid" or successful really

#

the status is requires_confirmation , not successful

#

your request is passing confirm: false

#

you need to pass confirm: true in that request

#

that will decline the card and the PaymentIntent won't be successful

atomic depot
#

This particular transaction is an 'authorization' which is why I never confirmed it

#

is that not the right way to handle the authorization?

#

We're trying to just verify the card is valid and the user has the funds on their card to cover the order during checkout

#

then when the goods are ready to ship we hit the card for the actual monies

pastel patio
#

sorry, we need to take some steps back, I think you're misunderstanding

#

This particular transaction is an 'authorization' which is why I never confirmed it
that is different

#

what you're talking about is capture_method: manual

#

confirm: true is what triggers the authorization

#

so you need it

#

right now you have no validation, no charge, nothing

#

you have a PaymentIntent with a PaymentMethod attached that is just ... sitting!

atomic depot
#

hmm ok, I'll review the docs on capture_method manual. I thought the 2 step PI was for the first step to auth funds and the second step to claim them when ready

#

Our downstream scenario is more complicated so I want to be careful. We use stripe connect and when it's time to claim the funds for the orders the charge will be handled via totally different PI flow

#

so I need to cancel the original intent to release the funds from the initial auth

#

it's a b2b market place where you can purchase from multiple vendors from a singel checkout. We do 1 auth for total amount but actual charges later will be broken up by vendor via stripe connect

pastel patio
#

I thought the 2 step PI was for the first step to auth funds and the second step to claim them when ready
2 step PaymentIntent can mean many things fwiw but to clarify - your PaymentIntent currently is not set up for authorization, then capture. Which is what you want right?

atomic depot
#

yes that's right

pastel patio
#

that's what you need, you're missing capture_method: "manual"

atomic depot
#

have the article up. Will read it and adjust my code accordingly. Don't want to tie up any more of your time for now. Thanks so much for helping!