#_durrell
strange knoll
slender plank
Hello! It really depends on the use case and the individual situation.
vivid sail
I would think in order for us to avoid PCI compliance red tape we would not want the account number on our server. That's why we created tokens in the past and sent those to our server instead.
slender plank
PCI applies to cards, not bank accounts.
There are separate rules and guidelines that apply to bank account data.
vivid sail
Our end goal is to let our users schedule Stripe::Treasury::OutboundTransfer
so we need to create a SetupIntent that has a PaymentMethod.
Will the second screenshot above that doesn't have the account numbers on the server work?
slender plank
Yes, I believe so.
vivid sail
ok. This is the next step: https://stripe.com/docs/js/setup_intents/collect_bank_account_for_setup
It says it will automatically load an on-page modal UI to collect bank account details and verification, and attach the PaymentMethod to the SetupIntent.
Upon completetion we should receive webhooks of the updated SetupIntent?
slender plank
Yes, if you're listening for the associated Events.
vivid sail
ok. Thank you Rubeus.
In what scenario might one want to create the SetupIntent on the server with the account number and routing number?
slender plank
Probably when you already have the account details in a database, or from a migration, or if you're unable to use our client-side libraries.
slender plank
You too!