Issue with Stripe API key

[virajsoni06]

Hi, we have integrated Stripe for payments. It worked fine in test mode but in live mode when we try to make a payment we get the error that the platform access is revoked. We even tried to reconnect Stripe and still the same results.
Another strange thing is the pk_live_ key in the screenshot doesn't match the key in Stripe

[virajsoni06]

@logeshswell bumping this up

[virajsoni06]

Hi @steven-k1 @ericingram, can someone get back on this with urgency. Our entire deployment is on hold because of this payment issue.

[logeshswell]

Understood. So, it is confirmed that the Swell dashboard contains/passes the right public key to the Stripe system.

[logeshswell]

How do you say that it's not the right key in your Stripe account?

Can you cross-check the response from the below URL to verify that you connected the right Stripe account in Swell dashboard?
https://topmarks-test-store.swell.store/admin/console?get/settings/-payments~Hgateways~Hstripe

[logeshswell]

Does live_account_id and live_secret_key matches with your Stripe account?

[virajsoni06]

@logeshswell No it doesn't match the ones we have in our Stripe account

[virajsoni06]

@logeshswell what's the update on this?

[steven-k1]

@virajsoni06 If the live_account_id and live_secret_key in Swell do not match up, it sounds like at some point, a different Stripe account was connected, so the system is attempting to connect to account B when you need to connect to account A.

The live_account_id and live_secret_key in Swell need to match up with the ones in the account you want to connect with in Stripe.

[logeshswell]

@virajsoni06 Can you give us some time to investigate and respond to you with further information?

[virajsoni06]

@logeshswell sure, can you give an eta on it. We need to understand how long this issue will take to get it resolved

[logeshswell]

Also, another issue, after changing the Stripe keys manually, the order will go through.

I hope the integration issue is resolved for the time-being as per your comment here

Secondly, we already filed a bug ticket stating that double payment intents are created for googlePay method in Stripe.
It is being worked on by our engineers and will be shipped quickly.

Is there anything else do you need assistance?

[virajsoni06]

@logeshswell I wouldn't call it resolved yet. The issue still exists where we do not know where the api keys are coming from and what is suggested is a makeshift solution. Either Swell should allow us to fully control the integration or it should be fixed asap. This is fairly serious issue and we won't call it as resolved at all.

Firstly, can you please clearly and technically let me know where are the api keys coming from? And how can we access them? (PS: Sending a link to Stripe oauth does not help, need to clearly understand where are the keys from)

Secondly, the double payment intents does not exist for Google Pay, infact we do not have Google Pay enabled at all. It happens with credit/debit card payments, we never said its for Google Pay. Why is it happening for normal payment methods? Was the Stripe integration tested?

[logeshswell]

@virajsoni06 I also mean that the makeshift solution helps you for the time being. We will investigate and make a permanent fix for your Stripe integration issue.

the double payment intents issue happens with credit/debit card payments.

Yes, I am aware of it and it happens with all payment methods. We are working on it.

[steven-k1]

@virajsoni06 A fix was released for the double payment intents.

[virajsoni06]

Hi @steven-k1 what about the original issue where the keys on Swell are different than that on Stripe?

[virajsoni06]

Don't understand why is this being closed without resolving the original issue

[logeshswell]

what about the original issue where the keys on Swell are different than that on Stripe?

We will keep you posted in this same discussion after the fix is rolled out.

[logeshswell]

Don't understand why is this being closed without resolving the original issue

If there's no further topic to discuss, we will close the discussion after a week or two.
But, it doesn't mean that your reported issues were resolved, while closing the discussion.

You can always feel free to reopen the discussion for any other information.