mastergates-applepay-platform | Stripe Developers | Page 1

quartz lodge Nov 16, 2021, 4:55 PM

#

@signal terrace 100% we always said it would be on the connected account for Direct charges

#

But if you use the legacy Token API then it's all based on where you create the token. But there's no reason to create the Token on the platform if you use Direct Charges, so I'd recommend not doing that

signal terrace Nov 16, 2021, 4:59 PM

#

can you please elaborate on what you mean by where we create the token when using the legacy token api?

quartz lodge Nov 16, 2021, 5:01 PM

#

Can you ask your real question instead? What is really blocking you right now? I'd rather not get into a hypothetical around edge-cases with a multi-years old API

signal terrace Nov 16, 2021, 5:05 PM

#

I thought I did ask directly.

We have subdomains being registered for apple-pay, but to our platform account
We want to collect apple/google pay tokens for direct charges, and use them as drop-in replacements for direct charges that currently use the sources api
Question: Do we need to change how we're registering apple-pay subdomains since they aren't being done on behalf of the connect stripe accounts?

quartz lodge Nov 16, 2021, 5:06 PM

#

I don't understand #2 and what that could mean unfortunately. What is "the sources API" exactly? What did your code do before exactly and what are you changing and why?

signal terrace Nov 16, 2021, 5:14 PM

#

#2 is using the stripe.js PaymentRequest object 'source' event (https://stripe.com/docs/js/payment_request/events/on_source) to capture apple/google pay as a token that can be used with the Sources api (instead of payment intents).

Our system currently makes direct charges using the Charges api (which uses Sources as the payment instrument).

The change we'd be making is adding the paymentRequest button to our stripe.js setup.

The documentation however states that the subdomain used for stripe.js paymentRequest (with apple pay) has to be registered with the connect account, which we aren't doing right now.

quartz lodge Nov 16, 2021, 5:15 PM

#

I'm really surprised by this. Sources src_123 created on the Platform should never work on connected accounts with direct charges. Do you have an example Charge id ch_123?

signal terrace Nov 16, 2021, 5:17 PM

#

It doesn't, because that's not the end of how we do it.

Collect card details and save token as a Source on a platform user profile
Clone the platform user's Source
Create a direct charge using the cloned Source

#

With apple/google pay tokens (created as Sources via stripe.js paymentRequest.on('source'...) ) we weren't planning on doing the same steps of adding to a platform profile, cloning it, then creating a direct charge because that seemed wasteful. Hence the question of being able to go straight from getting an apple pay Source token to using it as the source for a direct charge.

quartz lodge Nov 16, 2021, 5:27 PM

#

you say "An apple pay Source token" and it doesn't make sense unfortunately. Source and Token are completely unrelated/separate APIs

#

Really if you are changing your integration, move to a more recent/correct integration, use PaymentIntent and PaymentMethod

signal terrace Nov 16, 2021, 5:38 PM

#

We aren't changing our backend integration in my scenarios, we're still using the Charges api.

For clarification: the stripe.js PaymentRequest object only represents wallet-type payments correct? The documentation section for PaymentRequest events has different ones which each emit a different thing, such as a Token, a Source, and a PaymentMethod. Wouldn't all of those things be created for the apple/google/wallet info that was just collected?

quartz lodge Nov 16, 2021, 5:42 PM

#

I'm sorry, I know you're trying to get answers, I just don't follow you at all. You're on a multi-years old API integration. Why are you removing Sources? What are you going to gain from making that risky change but not moving to the more canonical integration?

signal terrace Nov 16, 2021, 5:47 PM

#

There's definitely been a disconnect, because we aren't removing Sources from our integration. My understanding is that you can make charges using the Charges API, and there are newer Payment/Setup Intents that do that now. The Charges api can use a Token, or Source object whereas Payment Intents needs to use a PaymentMethod object as its payment instrument. So in our case we are still using Charges + Sources. We simply want to also capture apple/google pay as a Token or Source object (which the stripe.js documentation leads me to believe is possible), and then use this new Source object for a direct Charge to a connect account.

quartz lodge Nov 16, 2021, 6:20 PM

#

sorry Discord was down for a bit and my messages never posted 😦

#

[9:55 AM] koopajah: Like I still don't really grasp what's blocking you. You already found the event to anchor on to get a src_123 and it works the same as a normal card Source```

quartz lodge Nov 16, 2021, 7:52 PM

#

@signal terrace ^ did this make sense?

signal terrace Nov 16, 2021, 8:37 PM

#

We're just going to test each case to see what works

#mastergates-applepay-platform