How to revoke or deactivate Stripe API integration with Cheqdin?

Modified on Mon, 25 Mar 2024 at 05:09 PM

Important: If you revoke access to the Stripe API, you'll no longer be able to process or accept online debit/credit card payments from your customers.  

You can revoke API access only if you have previously successfully set up a Stripe integration with Cheqdin. Revoking or deleting Stripe API access will not delete your Cheqdin account data; however, please note that you will no longer be able to process or accept online payments from your customers. Please contact the Cheqdin support team if you are facing any issues with your Stripe integration.


How to revoke Stripe API access? 

To revoke Stripe API access from your Cheqdin account, please follow the below steps: 

Login to Cheqdin's web portal, go to  'Integrations' > 'Stripe' tab: 

If you've already set up Stripe API with Cheqdin, the button will read as 'Connected' (green colour). 

Step 1: Click on the 'Connected' button to open the API credentials set up page

Step 2: Click on 'Revoke Access'.

Note: If you wish to temporarily turn off online payment collection instead of revoking the API access, then you can choose to simply toggle the button to 'OFF' next to the feature for which you want to disable payment collection. For example, if you toggle the button to 'OFF' for CheqBill, it will disable payments for billing and invoicing. If you toggle CheqBook to 'OFF', it will disable payments for bookings. 

Step 3: Click on 'Revoke access now'

A prompt will be displayed on your screen confirming that your Stripe account linked with Cheqdin has been removed successfully.

After the API integration is revoked, you will see the 'Setup Now' option again. Click on 'Set Up Now' if you wish to use Stripe for online card payments again. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article