#lost.prototype

1 messages · Page 1 of 1 (latest)

atomic bluffBOT
slender badge
#

Hi there, is this a question about how to switch to live mode after you finish development on test mode?

rare frost
#

Yeah

#

I've already switched to using my production keys on my server when I generate intents and authorizations

#

But I still get shown this:

#

Instead of the regular UX which is NFC enabled, etc...

slender badge
#

Can you share with me your merchant ID? you can find it from the Stripe Dashboard -> Settings ->Account Details

rare frost
#

acct_1NccxJLuyOQnR8JD

#

This is for "Street Swipe", which is the merchant account my application code authenticates as.

#

In my test scenario, I have used Stripe Connect to grant the above merchant access to perform transactions on behalf of acct_1MPUldBhBPAhixsR, which is a merchant called "Copper Dusk".

#

This is how I use the Stripe C# SDK to create connection tokens.

image.png
#

This is how I use the Stripe C# SDK to create payment intents.

image.png
#

Overall, everything appears to work with test keys when I'm debugging my app. I see transactions in test mode for both my merchants.
But when I build my app in non-debug (production) mode, the Stripe Android Tap to Pay UI doesn't switch over to the full Tap to Pay experience. Instead, I continue to see the "TAP TO SIMULATE PAYMENT" test view.

I just want to get an idea of how and when I can expect the UX to switch over so that I can test using real credit cards.

slender badge
#

Is this the correct account ID? because I don't see any request to create connection tokens, in both live or test mode.

rare frost
#

Yeah they should be

#

I can try right now again if you'd like...

#

Just attempted again.

#

The charge fails telling me that I attempted to use a test card on a production account.

#

As best as I can deduce, this might be because I'm still being shown the debug UX for tap to pay, but I have everything configured with production keys.

#

I can see the attempts in the dashboard logs as well.

#

req_T11VHIICoWuXn9

slender badge
#

That's a different account, the account ID you provided earlier is
acct_1NccxJLuyOQnR8JD

rare frost
#

I provided a second as well

#

As I'm doing this using stripe connect

#

So the charge is being done by 1Nccx...
But for the connected account 1MPUl...

#

acct_1NccxJLuyOQnR8JD - Street Swipe

#

acct_1MPUldBhBPAhixsR - Copper Dusk

#

In this scenario, Copper Dusk is connected to Street Swipe via Stripe Connect.

#

Street Swipe creates a payment intent for Copper Dusk by providing its id for StripeAccount in the request options.

slender badge
rare frost
#

Oh Hmm

#

That's odd as I haven't even configured the key for Copper Dusk anywhere

#

My server only gets provisioned with the key for Street Swipe.

#

But I'll double check things

#

That said, in general terms, what is the expectation for the stripe tap to pay UX to switch to its production mode?

#

What triggers it to switch over?

slender badge
#

as far as I know, you just need to use the live mode secret key in your server.

#

Maybe some cache in your mobile app? can you try uninstall and re-install the app and try again?

rare frost
#

It's unlikely, I've been reinstalling it pretty aggressively to test other things

#

Heh

#

But in either case, the key has been a live mode key

#

Does the application have to be signed and coming from the Google Play store?

#

Or can side loaded APK builds still work?

#

I'm just wondering if the tap to pay functionality depends on say... Something like play store certificates/chains

slender badge
rare frost
#

Alright. I'll get a second look at things and see if I can deduce anything