#shubham_docs

1 messages ยท Page 1 of 1 (latest)

dreamy beaconBOT
#

๐Ÿ‘‹ 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/1239566090976362567

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

scarlet meteorBOT
tribal pewter
barren tartan
#

Sure

#

Here you go:
req_mUIoFXW3aVaXsl

tribal pewter
#

Taking a look

barren tartan
#

Sure

tribal pewter
barren tartan
#

Sure, Let me try this

#

req_WU8f1CdLYsivLm

Another request id with pretty much the same message

#

I think the payment Method is not attached to the intent yet.

tribal pewter
scarlet meteorBOT
barren tartan
#

req_GxNTi0GBhpzQWy
Please check this one

#

I have now a payment method sucessfully attached to this paymentIntent

#

I am using capture method automatic async for this:

Should be something else?

tribal pewter
barren tartan
#

Sure

#

Trying this..

#

Quick question, confirm - automatic works for both payment intent capture (Server Side) and Client Side using customer Sheet / Payment Sheet?

#

This PaymentIntent could not be captured because it has a status of requires_confirmation. Only a PaymentIntent with one of the following statuses may be captured: requires_capture.; code: payment_intent_unexpected_state; request-id: req_TklpZRAdj6k1gw

Still getting the same

tribal pewter
#

Can you share the request id?

barren tartan
#

req_TklpZRAdj6k1gw

tribal pewter
barren tartan
#

Here's my code

barren tartan
#

req_wkJdyXFspHGosS

New error.

analog cove
#

Hi there ๐Ÿ‘‹ that error says that a return_url is missing, does the error subside if you provide a return_url or use the alternative option discussed in the error message to avoid that requirements?

#

Can you also elaborate on what you're trying to do? Initially you asked about doing this server-side, but you're now asking about doing it from the Payment Sheet, so I'm not quite sure what you're trying to accomplish here.

barren tartan
#

req_UpI7gUJmh89m8A
Here's a new one.

I basically changed the setAutomaticPaymentMethods
and configured like this:
.setAllowRedirects(PaymentIntentCreateParams.AutomaticPaymentMethods.AllowRedirects.NEVER)
.setEnabled(true)

Then I got an error to remove the ConfirmationMethod so I did.

Now it says payment intent has already been already captured

analog cove
barren tartan
#

Oh, So does that mean I don't need to do anything else to charge the customer? Just create the intent with said parameters

analog cove
#

When the payments succeed, yes that is correct. You should still be prepared to handle the case where the payment fails, in which case you'll need to bring your customer back on session so they can provide updated payment method details or complete the required authentication challenge.

barren tartan
#

Okay. Thanks So much for this

analog cove
#

Any time!