#Matias-test-SEPA
1 messages ยท Page 1 of 1 (latest)
Are you seeing some type of error when using the ones that are currently in the docs?
You must use a test bank account number in test mode. Try FI2112345600000785 or see more options at https://stripe.com/docs/connect/testing#account-numbers.
I get that when using FI1012345600000789 which is the test one for The PaymentIntent status transitions from processing to requires_payment_method after three minutes. (And I tried with pretty much all countries, they all throw the same error) - The other accounts for success anbd what not seem to work just fine
Oh, the processing -> succeed one also fails, just in case. Both accounts that have a 3-minute delay seem to be not working (On all countries).
What page in the docs did you get that number from?
Do you have the request ID from when you got that error? (req_123)
In the response? No
"error": {
"code": "account_number_invalid",
"doc_url": "https://stripe.com/docs/error-codes/account-number-invalid",
"message": "You must use a test bank account number in test mode. Try FR1420041010050500013M02606 or see more options at https://stripe.com/docs/connect/testing#account-numbers.",
"param": "bank_account[account_number]",
"type": "invalid_request_error"
}
}
Thats the full response I get (This is using a different account I tried just now)
It will be a header in the response. Our client libraries have ways of retrieving the request ID https://stripe.com/docs/api/request_ids
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Or it will be in your dashboard logs https://dashboard.stripe.com/test/logs
Whoops, my bad. Sorry ๐
req_8KQ19DPwO4e56K
Thanks! ๐
Weird, those test account numbers are working for me.
Checking what we are doing differently.
What is the client call that you are making?
Can you show me the snippet of code where you try to create this token?
hum, strange. Because all others work just fine.
This is my request payload. Lemme dig up the code in the meantime
bank_account[country]: FR
bank_account[currency]: eur
bank_account[account_number]: FR3020041010050500013M02609
bank_account[account_holder_name]: dad
key: pk_test_kxyz
payment_user_agent: stripe.js/xyzxyz
I'm using https://js.stripe.com/v2/ library for JS
var fullName = $('.iban-full-name').val();
var ibanNumber = $('.iban-number').val().trim();
var ibanCountry = ibanNumber.substring(0,2);
...
Stripe.bankAccount.createToken({
country: ibanCountry,
currency: 'eur',
account_number: ibanNumber,
account_holder_name: fullName,
}, stripeResponseHandler);
A bit unfamiliar with this process. Is there a reason you are using tokens instead of a SetupIntent and confirmSepaDebitSetup? https://stripe.com/docs/payments/sepa-debit/set-up-payment#web-submit-payment-method
Probably, but I can't remember now ๐ , started with this about 6 months ago and didnt get a chance to wrap it up until today.
Maybe the API version is the cause? I'm in a really old API version (for the accounts not working)
Ah yeah, I had to go this way because our system uses a very old API (late 2014), and using the newer JS wrapper meant overhauling a big part of the code.
Thanks for the clarification. Still trying to figure out what this might be and what you can do.
Thank you!
It's odd that only these two accounts-scenarios don't seem to work, but I guess they werent enabled for earlier api versions? Not sure (I'm amazed at how Stripe manages to keep old API versions still functional! - Props for that).
At this point though, my goal is to test payments that are in "processing" state, even if indefinitely, so if you have any suggestions that'd allow me to achieve that, I'd appreciate it.
@twilit saffron I'm catching up, one sec and looking along with Pompey
@twilit saffron when you make the request in #910998136686796860 message
can you paste for me values of all the fields you're passing there? everything, like ibanNumber, fullName etc, log out all the fields and paste them here
I assume they're all test mode so fine to share
This is the request sent. I copied it from the browser
No worries ๐
Not sure if this helps in any way, but this is a request ID for a token that succesfully works (payout succeeds - No delay)
req_EiKdTzoikZ0hKr
And the payload sent was
bank_account[country]: DE
bank_account[currency]: eur
bank_account[account_number]: DE89370400440532013000
bank_account[account_holder_name]: dff
key: pk_test_kxyz
payment_user_agent: stripe.js/3xyz
yeah so for creating IBAN external accounts (i.e. creating an external account Token), I recommend using either FR1420041010050500013M02606 from https://stripe.com/docs/connect/payouts-bank-accounts#formats (select FR from dropdown)
or use the IBANs from https://stripe.com/docs/connect/testing#account-numbers and change the prefix as needed
the FR3020041010050500013M02609 account you used earlier isn't allowlisted internally to create an external account Token from so that one won't work
Oh, I see. Yeah, Anything thats not "will switch from processing to <something> in 3 minutes" works fine (As listed on the docs), but thats the case I needed to test, orders hanging in "processing state" ๐
well let's take a step back
you're using these https://stripe.com/docs/testing#sepa-test-account-numbers
these are meant for PaymentMethods (not Tokens) and that too, when you charge a SEPA Direct Debit PaymentMethod
but you're creating a Token out of it
so my question is, what are you actually testing? Charging a SEPA debit PaymentMethod? Or attaching a SEPA account as an external account to a Connect account
Charging a sepa debit payment method that doesn't get paid/rejected immediately
(Honestly, we started this project about 6 months ago, had to shift gears for a bit and finally deployed it yesterday, but today we realized there can be a delay -We knew, just forgot about it- in the payments being processed and those cases are not being properly handled right now - So I was trying to replicate that state to work on handling it properly ๐
)
Hello! I think the closest thing we have is the three minute test number you already mentioned.
All other test SEPA numbers transition from processing to another status ~immediately.
Why is the three minute delay not working for you?
Hello there, apparently its not allowed for external use? Not sure if its because I'm using an old JS wrapper or straight up not allowed to be used by anyone. In any case, they're throwing an error when I try to attach them (only those 3-minute delay ones, all the others work just fine) as the system seems to think they're "live" and not "test" accounts
Can you give me the request ID showing the error you're getting when you try one? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Is req_8KQ19DPwO4e56K one?
Looking, hang on..
Ah, okay, so that test number isn't compatible with the older Tokens API. It looks like the only test bank account numbers you can use with the older API are the ones listed here, in the old integration guide: https://stripe.com/docs/sources/sepa-debit#testing
There is no option for a delay there unfortunately.