Phone operator will need to collect the customers credit card information (and save for future use) and charge the customer for the service. The customer will never log into the app.
Can the operators save CC information without the customer ever being logged into their own user account?
What’s the best way the phone operator can charge customers? Would they use the “Charge Current User” and just swap out the email address with the customer’s?
Can the above requirements be met with Bubble’s Stripe plugin?
You’re able to make your own customers within Stripe with API. You can attach all their information through the panel or API, and charge accordingly. Laws vary based on location in how you can collect personal payment data, but you should be alright.
I definitely wouldn’t swap out the current user’s email. That’s just asking for trouble. And if you want to save it for future use where would you put the Stripe token?!?
It all depends on the workflow and where e/t is happening (is the call being logged in Bubble or Hubspot?) but you can make a user profile with users information and stripe token and then charge them and that way it can handle receipts, etc and if it’s a possibility that the user will user ever creates a login it will sync up with that user .
Thanks for the feedback. To clarify, we would charge the customer and save his/her info to a Customer data type. I figured we could save the Stripe token to the Customer data type (instead of the User data type).
But your point about the customer creating a login down the road makes sense and is a strong argument for saving customers in the User data type.
Is there any problem having the phone operator user save credit card info for another user (customer)? I understand a user can save a credit card to their own profile, but could an employee save a credit card for other users (ie. someone calls in by phone). If possible, could this be done using a Stripe or Stripe.js plugin? Or would I need to use separate API calls?
Taking CC over the phone is legal in all/most states provided you follow the security and disclaimers that states require (disclaimer : not a legal opinion despite it coming from a lawyer). You also dont need to take it over phone as you can text them a link that takes them to the page you want…
Not sure what you mean by plugin or api call as once it’s in the bubble flow you can interact with stripe however you like be it a plugin or preferably an api call) but the fact that it’s in a customer thing doesnt have any real impact on your current payment flow)
not a legal opinion despite it coming from a lawyer). You also dont need to take it over phone as you can text them a link that takes them to the page you want…