#sadern-ach-elements
1 messages · Page 1 of 1 (latest)
Expected behavior
Hello! As far as I know this is not somethign we support with the Payment Element today - you'd need to build your own UI for that if you don't want to colelct those detials in a modal
will it be secure?
what do you mean by "build your own UI"?
I thought the only one way to implement secured and tokenized element is by using Stripe js's elements
When I say build your own UI I mean you'd make your own form w/ inputs that accepts the routing number, account number, account name, etc. and you'd pass that on to your server to create a Payment Method (https://stripe.com/docs/api/payment_methods/create#create_payment_method-us_bank_account)
Card data is subject to pretty strict requirements (so we do ask/require that you use our elements in order to be PCI compliant), but bank data does not have those same restrictions
Thx, I'll go over this docs
sadern-ach-elements
To sum it up. I can create simple form on the front-end. They don't need to be rendered in the iframe element, then just send it to my back-end (endpoint that will create payment method) and this is just it?. If yes and I understand everything correctly, it won't be as secure as using Stripe's elements but secure enough to meet the restrictions?
Almost - you'd create the Payment method but since you're not doing instant verification you'll likely need to build some additional things to handle the verification flow and everything. But yes, generally you have the right idea
additional things like payment intend, etc... Generally flow mentioned here: https://stripe.com/docs/payments/ach-debit/accept-a-payment?platform=web&ui=API
?
I'm new in Stripe and I'm trying to figure out if it's worth it to sacrifice some kind of security to keep application UI consistency. I think it's not. Thank you very much for the guidance