#Ksamuel - ACH attach error
1 messages · Page 1 of 1 (latest)
sure thing
{
"error": {
"message": "PaymentMethods of type us_bank_account must be verified before they can be attached to a customer.",
"payment_intent": {
"id": "pi_3McBqiBAuPO34Ji61bq2TLtA",
"object": "payment_intent",
"amount": 100,
"amount_details": {
"tip": {
}
},
"automatic_payment_methods": {
"enabled": true
},
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"client_secret": "pi_3McBqiBAuPO34Ji61bq2TLtA_secret_EnZAxAWWFICdslyiVRMzwma8p",
"confirmation_method": "automatic",
"created": 1676570788,
"currency": "usd",
"description": null,
"last_payment_error": null,
"livemode": false,
"next_action": null,
"payment_method": null,
"payment_method_options": {
"us_bank_account": {
"verification_method": "instant"
}
},
"payment_method_types": [
"card",
"us_bank_account"
],
"processing": null,
"receipt_email": null,
"setup_future_usage": "on_session",
"shipping": null,
"source": null,
"status": "requires_payment_method"
},
"request_log_url": "https://dashboard.stripe.com/test/logs/req_v8zjpjUpQE4OZ0?t=1676571123",
"type": "invalid_request_error"
}
}
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Thanks taking a look
Hm that's strange
What did you click exactly in the flow?
Did you click "test institution" when Payment Element shows up?
Ah I see you are updating the PI to attach a Customer to it
Can you run a quick test for me and pass that Customer ID when you create the PaymentIntent?
sure
Hi! Sorry that took a second. I hard coded a customer id into our createPaymentIntent and our check for an existing customer Id. It still didn't work unfortunately, same error message. I am noticing that the Payment Intent payload above doesn't have the customer id attached to it (nor does the new one). Is that an issue or by design?
Huh this is strange
Can you share that PaymentIntent that you just tested with?
I just ran through the flow myself and didn't run into that error
Not quite sure what you are doing differently but I'm looking
Sure thing. Getting on a plane so it will be a moment
Definitely something weird here. Still looking
I was able to go to the dashboard and retrieve the Payment Intent that had the hardcoded customer. Here was the paymentIntent as it was when it got the us_bank_account error
{
"id": "pi_3McCUaBAuPO34Ji61wMpvpK6",
"object": "payment_intent",
"customer": "cus_NMDHD8OsbsACze",
"last_payment_error": null,
"livemode": false,
"next_action": null,
"status": "requires_payment_method",
"amount": 100,
"amount_capturable": 0,
"amount_details": {
"tip": {
}
},
"amount_received": 0,
"application": null,
"application_fee_amount": null,
"automatic_payment_methods": {
"enabled": true
},
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"charges": {
"object": "list",
"data": [
],
"has_more": false,
"total_count": 0,
"url": "/v1/charges?payment_intent=pi_3McCUaBAuPO34Ji61wMpvpK6"
},
"client_secret": "pi_3McCUaBAuPO34Ji61wMpvpK6_secret_2nbpa8jEVaNFQGr5niyWS5NIv",
"confirmation_method": "automatic",
"created": 1676573260,
"currency": "usd",
"description": null,
"invoice": null,
"latest_charge": null,
"metadata": {
},
"on_behalf_of": null,
"payment_method": null,
"payment_method_options": {
"card": {
"installments": null,
"mandate_options": null,
"network": null,
"request_three_d_secure": "automatic"
},
"us_bank_account": {
"financial_connections": {
"permissions": [
"payment_method"
]
},
"verification_method": "instant"
}
},
"payment_method_types": [
"card",
"us_bank_account"
],
"processing": null,
"receipt_email": null,
"review": null,
"setup_future_usage": "on_session",
"shipping": null,
"source": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"transfer_data": null,
"transfer_group": null
}
Thank you for the info! Will pass that along. Still looking in to the cause on our side
Ksamuel - ACH attach error
@carmine glen you still here?
It looks like in that most recent test you still updated the PI to set a Customer and that request is taking place during the Connections Session request just before confirmation. Can you remove that Customer update request entirely and run one more test?
Sure thing
{
"id": "pi_3McEONBAuPO34Ji61kuLvEqt",
"object": "payment_intent",
"last_payment_error": null,
"livemode": false,
"next_action": null,
"status": "requires_payment_method",
"amount": 100,
"amount_capturable": 0,
"amount_details": {
"tip": {
}
},
"amount_received": 0,
"application": null,
"application_fee_amount": null,
"automatic_payment_methods": {
"enabled": true
},
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"charges": {
"object": "list",
"data": [
],
"has_more": false,
"total_count": 0,
"url": "/v1/charges?payment_intent=pi_3McEONBAuPO34Ji61kuLvEqt"
},
"client_secret": "pi_3McEONBAuPO34Ji61kuLvEqt_secret_vw5hOWgtnJ24vIMSmEOJN43y6",
"confirmation_method": "automatic",
"created": 1676580563,
"currency": "usd",
"customer": "cus_NKiV0WaUBR477X",
"description": null,
"invoice": null,
"latest_charge": null,
"metadata": {
},
"on_behalf_of": null,
"payment_method": null,
"payment_method_options": {
"card": {
"installments": null,
"mandate_options": null,
"network": null,
"request_three_d_secure": "automatic"
},
"us_bank_account": {
"financial_connections": {
"permissions": [
"payment_method"
]
},
"verification_method": "instant"
}
},
"payment_method_types": [
"card",
"us_bank_account"
],
"processing": null,
"receipt_email": null,
"review": null,
"setup_future_usage": "on_session",
"shipping": null,
"source": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"transfer_data": null,
"transfer_group": null
}
No call to update the paymentIntent and it still returned the same error. Here's the payment intent as it stands.
I caught this in the console too, do you think this may have something to do with it? "The Financial Connections authentication flow requires "minimum-scale=1" to be set in your page's viewport meta tag."
Hmm not sure but would be surprised if that is the issue.
Conferring with our Financial Connections team, give me a few more mins
So yeah the viewport meta log is just a warning but you should do that so that the modal styling works in various edge cases like when zoomed
Not going to be root cause here
We are looking into the error further
Okay @carmine glen figured it out. Looks like you are passing save_payment_method: true client-side to confirmPayment. This isn't a supported parameter in our SDK and it seems to be causing an issue here.
I was able to reproduce once adding that
If you remove that then it should work
Ooc where did you see that parameter or why did you add it?
Oh great!
Then it was probably that. My coworker added it