#swe_api

1 messages ยท Page 1 of 1 (latest)

lethal sailBOT
#

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

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

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

forest venture
#

Error message from Stripe - "The following payment method types [-quot-sepa_debit-quot-] can only be used with PaymentIntents that have capture_method=automatic. Please retry by creating a PaymentIntent with capture_method=automatic.; request-id: req_DNjye9vsoip7wO"

The same request works for other accounts.

#

Is there something missing in the configuration?

lethal sequoia
#

๐Ÿ‘‹

#

Sepa PaymentMethod doesn't support manual capture

forest venture
#

But, it worked fine for req_FolT9bIl2Z19Zp.

#

Why is this difference in behaviour happening?

#

{
"amount": "8000",
"capture_method": "manual",
"confirm": "true",
"confirmation_method": "manual",
"currency": "eur",
"mandate_data": {
"customer_acceptance": {
"accepted_at": "1724923345",
"online": {
"ip_address": "",
"user_agent": "Mozilla/5.0 (Macintosh Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36"
},
"type": "online"
}
},
"payment_method_data": {
"billing_details": {
"email": "testdd@mail.com",
"name": "TestFirstName TestLastName"
},
"sepa_debit": {
"iban": "FR
*****************M2606"
},
"type": "sepa_debit"
},
"payment_method_types": [
"sepa_debit"
],
"setup_future_usage": "off_session"
}

We use the above payload for both the requests.

lethal sequoia
#

There must be a private beta/feature enabled for the account acct_19o4IFJv9j0DyntJ and not for this one acct_17q326FHVuBMEiey

lethal sailBOT
forest venture
#
  1. May I know what's the feature enabled in this acct_19o4IFJv9j0DyntJ and not the failing account?
  2. Also, what are the suggested parameters for SEPA, in case we want to use it in future?
    "capture_method": "automatic",
    "confirm": "true",
    "confirmation_method": "manual",
    "setup_future_usage": "off_session"
wanton spoke
#

basically the default behaviour is to error if you pass capture_method and you also pass types in payment_method_types that don't support capture(like SEPA Debit), because that doesn't make sense to do.
The reason it works on one account is because we didn't always enforce this validation and it used to "fail open" (it just ignored capture_method and you're not actually getting manual capture), and when we rolled this out we exempted accounts who were already doing it to prevent immediately breaking their API calls, and your account was in that. But obviously the correct default valdiation applies to new/most accounts.
This was a few years ago and unfortunately we never really cleaned this up or contacted accounts like yours to tell you to migrate

#

the fix really is to remove "capture_method": "manual", in your code if you're only using SEPA Debit.

forest venture
#

Can you let us know for what payment methods - we are passing invalid capture_method value for this account- acct_19o4IFJv9j0DyntJ?
This will help us clean up the code. Since, we did not get any error message, we thought that was the right way to do things

wanton spoke
#

it's only really cards, card-based methods like wallets, and a few BNPLs like Klarna that support it

forest venture
#

Okay, thank you. This helps

#

We will validate the API calls in our end. This was an eye opener for us