Skip to main content

Fix “Limited permissions” for Credit automation

Fix "limited permissions" error for Automate credits.

Written by Theodore

Update Chargeback.io’s permissions in your payment processor, then resubmit your access request.

If you see this banner on the Credits page, Chargeback.io could not verify that it has the permissions needed to check transactions in your payment processor:

We couldn’t verify access to [processor]: limited permissions. Fix the issue and resubmit your request.

This article is for users with the Owner or Administrator role in Chargeback.io who see this message. It covers insufficient payment processor permissions, not a missing invitation, an invitation for the wrong account, or a rejected individual credit request.

Before you start

You need permission to manage users or teams in the affected payment processor account. Your role in Chargeback.io does not automatically give you those permissions.

Ask the person who manages the processor account to make the change if necessary.

Follow the access requirements shown for the affected processor in the Credit automation setup. If the required permissions are unclear, contact Chargeback.io Support before changing the permissions.

These instructions apply to processors that require an invitation. Stripe integrations that already provide the required transaction access do not use this invitation process.

Stripe: If the Stripe tab shows Access already available, your connected integration already provides the transaction access needed for Credit automation. You do not need to create a team or send an invitation for that integration.

Update Chargeback.io’s permissions

  1. In the Chargeback.io dashboard, click Credits in the sidebar.

  2. Click Restore payment account.

Resubmit your access request

After saving the permissions:

  1. Return to the Credit automation setup in Chargeback.io.

  2. Under Confirm invitation, select the checkbox after you have granted the required access.

  3. Complete any other required confirmations shown in the pop-up. If there are multiple tabs, use Next to reach the final tab.

  4. Click Submit request.

Submit request remains disabled until the required confirmations are complete.

Changing permissions in your payment processor does not resubmit the request. You must also complete the confirmation and submission steps in Chargeback.io.

What happens after you resubmit?

The Credits page shows a Pending banner while Chargeback.io checks your payment processor access. This usually takes one business day.

Do not submit another request while the check is pending unless Chargeback.io asks you to update it. We will email you when Credit automation becomes active or another change is needed.

Once the required access is verified for all connected processors, Credit automation becomes active for the business account. Chargeback.io then handles system credit requests without asking you to upload proof.

Manual credit requests are not automated. Credit automation also does not create missing system credit requests or search for alerts that do not already have one.

Will credit-request emails continue?

Credit-request emails remain on when access verification fails because of limited permissions. Follow the instructions in any credit-request emails you receive.

Once Credit automation is active for the business account, credit emails stop. This does not turn off other Chargeback.io notifications, including updates about Credit automation.

Still seeing “Limited permissions”?

Check that you updated the access associated with the email address specified in the Credit automation setup page in the correct payment processor account and saved the required permissions.

If you cannot change the permissions, ask the person who manages users or teams in that processor account to help. If the required permissions are saved but verification fails again, contact Chargeback.io Support.

If the banner shows a different verification reason, follow the instructions for that reason before resubmitting.

💬 Still need help? Contact Chargeback.io support.

Did this answer your question?