#n0ah9080
1 messages Β· Page 1 of 1 (latest)
Not sure I get it. Can you describe the situation a bit more fully so I understand and can help?
Ive been forced to work on a no code website solution
They allow me to run my code in different blocks. Yes, its as much pain as it sounds β οΈ
Since I can only run code in different code blocks there is no interception between them. I found out that it might be possible to stringify the card element, save it in localstorage/sessionstorage, and then retrieving it from there.
I tried doing the same with with the stripe object, but because JSON doesnt support functions it cannot travel with the stringified object. (I only have to do this because the same instance of the stripe object had to be used when tokenizing).
Ive been told it might be possible to serialize the function and utilize eval afterwards, but Im unsure about it because of the scope.
Is there any way to create an identical instance or such using built in Stripe.js functions?
Im pretty sure this is the last piece to solve this headache of a puzzle π€£
Oh wow. Interesting challenge
Ive been told it might be possible to serialize the function and utilize eval afterwards, but Im unsure about it because of the scope.
Where did you hear this?
(I would use api calls if they were PCI compliant but Im not sure they are π€·)
A friend briefly mentioned it and I havnt tried it nor think it works π
I have to run for a second, Ill be back in about 15 minutes, hopefully this chat wont close π₯
Yeah I really don't think that would work, but I also haven't tested it
So I guess the part I'm confused about is why you need separate code blocks for intializing stripe.js and accepting payment/tokenizing via the card element
Can't you just wait to initialize stripe.js until the step you accept payment at?
Hey! Im back! π
I was told to first create a card element, and then mounting it. That creates a input field in the Div
To create the card element I need to create a stripe object (because the function to create the card element is within it)
Id love to do it all in the same button, but I HAVE TO use the mounted field if I understand it correct? And therefore I think it would be difficult to both initialize stripe, create a stripe/card element, mounting AND tokenizing
There has to be some time inbetween the user input and the tokenization
Ah so it has to do with the lifecycle of the environment you're in?
Its causing some issues indeed π
I dont want to waste your time any more than I have to π
Theres no parameters or such I could use when creating the stripe object?
In a way I think you could say, yes π₯
Variables reset after a block is ran etc.
Gotcha. This is tricky. let me think on it
Okay thank you π₯°
Take your time!
Any help/ideas mean alot π
Will get back to you
Also my colleague is curious. What no-code platform is this?
You'll have to use a stripe-hosted solution like Payment Links. They informed me what you're trying to do just won't be possible
It's called Bubble.io, and I pray that I never have to touch it ever again π
Would this still allow for the onboarding page to be customized, and the accounts created to be of type "custom" ? π€
That's what they're asking me to help them create π
Oh right π€£
My bad, I apologize. I forgot to mention the thing I'm actually trying to create...
I only explained how it all worked...
When onboarding, I create an account and have to link a card to it. I'm on the latter part of that creation currently.
Got it. You should use our hosted onboarding flow then
What type of connect account?
That's what they're trying to NOT use sadly π’
Custom
I'm afraid you'll have to
Individual accounts for now, company accounts after that gets up and running
The code block scope restriction prevents you from doing this on your site via the api
I talked to the boys just now and explained. π
From your great help (I can't thank you enough for taking your time helping me out π₯°) I can see 2 options being viable solutions? Correct me if I'm wrong π
We could either utilize your hosted onboarding (I'd love if you could link me some documents to point me in the right direction on this) or we could become PCI compliant and utilize your API to tokenize the card information. I know that using the API for tokenization would most likely be a worse option in the case of security, but it's the only option to create a fully custom onboarding page under these circumstances.
To me it sounds like they're fine with me moving over to the hosted onboarding for now, but would want to work further on this later on.
Could you link me some type of documentation or somewhat explain how to apply for PCI compliance at Stripe so I know what they would have to do if they decided to go for that option later on? (I'll have to check with Bubble.io and make sure they are π )
Long message π
The hosted onboarding flow would be the least amount of friction
PCI compliance is complicated and we provide only limited guidance
It's your responsibility to consult legal counsel for advice on that
Here's the docs on the hosted onboarding flow though for custom accounts: https://stripe.com/docs/connect/connect-onboarding
For PCI compliance here's a few resources if you're curious:
https://stripe.com/en-gb-us/guides/pci-compliance
https://stripe.com/docs/security/guide
https://stripe.com/docs/security
https://support.stripe.com/questions/pci-compliance-validation-requirements-depending-on-transaction-volume
We cannot provide guidance on that though
Another alternative is to move away from a no-code solution
You won't believe how many times I've told them 
Yeah I get that the decision isn't up to you. Just wanted to hint at it again haha
That's totally understandable
I'll take a look at the hosted onboarding and hopefully get it up and running for them ASAP because they have to move over to custom accounts. (Express accounts are currently being used, I think it's called?)
Thanks you for all the help! I appreciate it tons! π₯°
No problem! Happy to help!
Also note this small section in the onboarding doc:
Connect Onboarding for Custom Accounts doesnβt collect the external_account requirement by default. To collect external_account, enable the Collect bank account information for payouts setting in Connect Settings. For more detailed instructions, refer to the Managing bank accounts and debit cards guide.
Since you need to collect external account it's important to note
