motorphotor-connect-chargeflow | Stripe Developers | Page 1

dark pagodaBOT Mar 28, 2023, 10:12 PM

#

topaz garden Mar 28, 2023, 10:12 PM

#

motorphotor-connect-chargeflow

#

@cunning frigate yep! But "which charge flow to use" is more dependent on the type of connected accounts you are using

cunning frigate Mar 28, 2023, 10:15 PM

#

Individual with custom connect, I’m just wondering if I do that and a customer has charges with separate users.. one user might be viewing charges originating from a different user when retrieving customer data, does that makes sense?

topaz garden Mar 28, 2023, 10:16 PM

#

yeah if you use Custom accounts you definitely should use Destination Charges.

#

And as the platform, you can track which Customer objects are re-used across accounts and which PaymentIntents should be made visible to which connected accounts and such

cunning frigate Mar 28, 2023, 10:18 PM

#

Ok, I haven’t gone deep into retrieving customer data yet so I assumed there was a way to filter that but wanted to confirm before I started writing this thank you 🙏🏼

topaz garden Mar 28, 2023, 10:19 PM

#

there isn't really a way to filter per se, you'd track this on your end. But as the platform, when you show all payments to that Customer you want to show them all their payments

cunning frigate Mar 28, 2023, 10:22 PM

#

I built everything with direct charges already and then after a convo on here was convinced to try out destination before continuing, I am glad I did. I think I can limit it on the app side anyway without having to filter anything now that I’m thinking about it.

I might end up with duplicate customers one for each user they initiate payments with. That shouldn’t interrupt anything correct?

topaz garden Mar 28, 2023, 10:25 PM

#

correct but that means you can't "share" card details and such

#

so if someone wants to order from account A and later B they have to enter card details again which is not the greatest experience

dark pagodaBOT Mar 28, 2023, 10:31 PM

#

cunning frigate Mar 28, 2023, 10:32 PM

#

Interesting. So our app will be in the hands of tattoo artists. Say a customer gets a tattoo with account A. Later, they go to account B and start entering in their information.. how many points matching would Stripe consider ‘safe’? Would just email and phone work? Or am I looking at this the wrong way?

#

Also entering their info again wouldn’t be a terrible hassle

willow flicker Mar 28, 2023, 10:33 PM

#

👋 my teammate has to run so just catching up!

cunning frigate Mar 28, 2023, 10:34 PM

#

Because account B won’t know about account A’s interaction with the customer so I’ll have to match on the backend

#

And our platform doesn’t have access to customer information unless they use stripe, we’re using iOS iCloud and CoreData

willow flicker Mar 28, 2023, 10:36 PM

#

Right, makes sense. You should keep a mapping on your end to match app customers and customer object on Stripe instead of looking up customer objects based on email addresses, phone numbers, etc. on the fly

#motorphotor-connect-chargeflow