#Vlad007123 - Subscription US Bank Account

1 messages · Page 1 of 1 (latest)

deep plaza
#

Do you have the request ID from when you got that error? (req_123...)

stuck orchid
#

Request POST body
{
"customer": "cus_LNGR1Msc8Xqcjc",
"default_payment_method": "pm_1KgVuhEfB0rwywnLPaUEpUzn",
"payment_behavior": "default_incomplete",
"on_behalf_of": "acct_1KRJjERT0NZtcUFB",
"transfer_data": {
"destination": "acct_1KRJjERT0NZtcUFB"
},
"items": {
"0": {
"price": "price_1KX8deEfB0rwywnLTlyHO2uh"
}
},
"expand": {
"0": "latest_invoice.payment_intent"
}
}

deep plaza
#

I think that that payment method type is still in beta. Do you know if your account is in the Beta and you specified using the beta API version for the us_bank_account beta?

#

That is interesting that that is not even included. I wonder if it is because one of the accounts is in the beta and the other isn't

stuck orchid
#

It works for US bank, but not for Canadian bank

deep plaza
#

Do you have the ID for the request that got that response?

stuck orchid
#

req_75HWn0xJI4EvwB

deep plaza
#

Thank you, will check in to that in a moment

stuck orchid
#

Thanks

#

payment method type is "acss_debit"

#

Maybe I should not use beta?

violet spear
#

And let me know if this still hits an error?

stuck orchid
#

ok, should I use OnBehalfOf?

#

and connected account id?

violet spear
#

Yes do everything the same but just explicitly set the payment_method_types to the one you are going to use.

#

I think this is an issue that is related to automatic payment methods + On_behalf_of + US bank beta but would like to confirm.

stuck orchid
#

I need some time

#

sorry

violet spear
#

No rush

stuck orchid
#

new KeyValuePair<string, string>("payment_settings[payment_method_types]", "acss_debit"),

#

is this good?

#

new KeyValuePair<string, string>("payment_settings[payment_method_types][0]", "acss_debit"),

#

It works

#

Thank you

violet spear
#

Thanks for testing! So yes, this is a known issue that came up recently. It has already been reported and our Engineers are looking into fixing it up. In the meantime, you can specify the payment_method_types explicitly to get around the issue. Once it is fixed it should just work without needing to specify payment_method_types