#Felix Cao

1 messages · Page 1 of 1 (latest)

twin turtleBOT
void mango
#

Hi! Let me help you with this.

#

Could you please summarise the issue, my colleague had to step away.

spring fog
#

I want to have a call with you by the discord and show you our design

#

@dark hearth told me there is issue for our design

void mango
spring fog
#

So we step by step

#
  1. our platform is Xoda
  2. Xoda has lots of merchant, we named gym
  3. gym has lots of member
  4. member buy the gym's service
#

This is the requirement for our platform

#

Step1: the gym login our platform and set the Payment method

#

wait a moment, I have to restart my computer, please don't close the channel

void mango
#

Alright.

spring fog
#

Step2: Collect the payment method for the gym's member

void mango
# spring fog

I would advice strongly against asking clients to share their Stripe keys.

spring fog
#

So how to design the case ?

void mango
#

Do you expect your Clients to have an existing Stripe Account?

#

I would recommend using Stripe Connect to create an account for your clients, specifically for your application. You can read more here: https://stripe.com/docs/connect

spring fog
#

I had read it before
So from the doc, my understand is:

  1. our platform has a secret key and publishable key
  2. every merchant has account_id and get the connected_account_id with the account_id
#

Right ?

void mango
#
  1. If the account is connected to your platform, you can control it by only providing the account_id.
#
  1. Yes.
spring fog
#

So we only store the account_id in our DB?

#

Not secret_key and publisable key ?

void mango
#

Yes

spring fog
#

The ezypay and ezidebit and paychoice need to store the private key and public key to our DB

void mango
#

I've never heard of those.

spring fog
#

Thanks very much from you guid

void mango
#

Happy to help!

twin turtleBOT
spring fog
#

Happy Dragon Boat Festival!