#50an6xy06r6n
1 messages · Page 1 of 1 (latest)
Hi there. Can you link the section in our docs that you're looking at?
Gotcha. Can you paste what you see in your code? Also it would help to know the library version that you are using and the ba_123 id
interface UsBankAccount {
/**
* Account holder type: individual or company.
*/
account_holder_type: UsBankAccount.AccountHolderType | null;
/**
* Account type: checkings or savings. Defaults to checking if omitted.
*/
account_type: UsBankAccount.AccountType | null;
/**
* The name of the bank.
*/
bank_name: string | null;
/**
* The ID of the Financial Connections Account used to create the payment method.
*/
financial_connections_account?: string | null;
/**
* Uniquely identifies this particular bank account. You can use this attribute to check whether two bank accounts are the same.
*/
fingerprint: string | null;
/**
* Last four digits of the bank account number.
*/
last4: string | null;
/**
* Routing number of the bank account.
*/
routing_number: string | null;
}
v. 2020-08-27
not looking at a specific bank account rn
Is that the node library?
yes
What version of the library? Not api version
8.222.0
any update on this?
Hi there! Sorry for the delay, I'm taking over for my colleague and catching up on this
Hm, could you link to the documentation you're referencing that mentions the status property?
Here
@unreal pawn
Ah, got it! I think there's a misunderstanding, sorry for not catching that earlier.
The docs you're looking at refer to bank account objects that have IDs in the shape "ba_..."
PaymentMethods of type us_bank_account do not have a status property. The section of the node library you linked above is for us_bank_account PaymentMethods, which explains why status is not present
where do the ba_... bank accounts come from then? the documentation indicates that those are still linked to customers
relatedly, it's unclear to me how the intermediate unverified bank account states should be handled, as the verification seems to happen instantly in the test environment
Hi there, stepping in as roadrunner is away. Catching up now.
I think what you're looking for is here: https://stripe.com/docs/payments/ach-debit#:~:text=When you use,and fraudulent activities. If you're using Stripe.js, and if the bank account is not verified with the instant verification, then it default to micro-deposit verifications.
So in our system we use a setupIntent and the Payment element to add the bank account, but it's unclear what state the intent/payment method will be in right after the form is submitted
in test mode we get the intent succeeded webhook immediately, and there's not intermediate verification state
basically, we want to know when we should block payments to an unverified bank account
Can you share the request id with me for this test request? Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
req_rPQTMrhIXPgbbP
more recent one would be req_gKOMyy0OYZroBS actually (this is actually the payment method being created and not cloned)
On this request, https://dashboard.stripe.com/test/logs/req_mCoEBhxJJmLIL4 the verification was was instant. If you do not instantly verify the bank account, then it will stay in 'processing' state: https://stripe.com/docs/payments/save-and-reuse?platform=web#web-submit-payment-details
do we get a webhook in that case? I can try again via the manual verification flow
You can look at the Setup Intent status: https://stripe.com/docs/api/errors#errors-setup_intent-status
Hmm, so there's no way to tell just based on the paymentMethod itself?
There is not