Im very new to bubble and slowly getting the hang of it.
Working on a marketplace app and everything is going great. Im at the stage where I need to put together the payment processing for the app.
After going through all the available docs (at least the ones I thought are relevant to the topic) and stripe documentation, Im more confused on how to approach my solution especially after the SCA requirements added to the equation. (Im in the UK).
I don’t think Im trying anything fancy, just the usual marketplace setup where ,
Seller can register and sell products
A user can buy and pay for the products
Seller makes money and platform gets commission
I have some basic questions and some about meeting SCA compliance.
For a user (not seller) to buy and pay for a product, should I create a customer in stripe before processing the payment ? This is a one-time payment scenario.
If I choose to create a customer can I store the Customer ID & CC ID from stripe, so that I can reference these details if the user wants to buy another product anytime in the future? Will this be considered SCA compliant ? (also applies for seller for subscription fees scenario)
are there any reference on how to use the payment intents api ?
my app lets a buyer buy multiple products from multiple sellers and I don’t want the user to be redirected to a different site to complete his payment (so Stripe Checkout is not an option for me).
I think this would be up to you. You can do it either way, but seeing that you are trying to avoid a checkout situation, or at least streamline it, it might be best to set the customer up first either at signup, or another prompt where you put a conditional on the buy option not being available until the user enters in their CC details (add stripe user). Then when that’s good, show the buy option as step 2, and then process the WF stripe charge.
It should be compliant. The ID’s that Stripe creates are specifically encrypted and generated to be stored on your database. If you tried to store a user’s CC info then that would not be compliant. Never do that. I’m in the US, so I don’t want to talk out of school, but I’m fairly certain that’s how it works. As an extra precaution, breeze through Stripe’s docs and search for compliance to be certain.
Assuming I store the cus_id from stripe and the user make another purchase at some point using a different payment card , will this cause issues or error out the payment process ? i.e is the Cus_id tied to CC_Id ?
In that scenario the new card would have to be added to the customer’s account, and would become the second added payment method.
The Cus_ID is the value assigned to identify the person / account. In Stripe this person could have multiple payment options, so yes they could have multiple cards, and each card would be assigned its own Card ID or CC_Id as you put it.
I believe the convention in Stripe is the last card added to a customer’s account becomes the default payment option. Some of the plugins allow you to retrieve the customer’s card info, and set which card the user wants to use as default,.