Connect to Stripe

This guide outlines the necessary steps to connect your Pagos and Stripe accounts. For more information on connecting Pagos to other payment processors, see our Connect to Braintree and Connect to Adyen guides.

Step 1 – Create a Restricted API Key in your Stripe account

For added data security, use a restricted API key to connect your Stripe and Pagos accounts. If you don't already have one, you'll need to create one in the Stripe dashboard:

  1. Log into your Stripe account, then locate your API keys in the Dashboard.
  2. Create a new restricted key. You'll need to name this API key and change the permission for Webhook Endpoints to Write. Then, change the permissions for the following core resources to Read:
    1. Balance
    2. Balance Transaction Sources
    3. Balance Transfers
    4. Charges
    5. Disputes
    6. Events
    7. Files
    8. PaymentIntents
    9. PaymentMethods
    10. Payouts
    11. Products
    12. SetupIntents
    13. Sources
    14. Tokens
    15. Subscriptions
    16. SKUs
    17. Report Runs and Report Types
  3. After you create the new restricted key, copy the Name and Token for use in the next step.

Step 2: Add a New Data Source to Your Pagos Account

To pull in Stripe data to Pagos, you'll need to add a new data source in your Pagos account:

  1. Log into your Pagos account.
  2. Click the settings icon in the navigation bar.
  3. Click Data Sources.
  4. To add a new data source, click + Add new data source.
  5. In the right-side panel that opens, click Stripe, then enter the restricted API key Name and Token from Step 1 above.
  6. Click Save to complete setup.



  • If you have already configured a webhook for your Stripe account to connect to Pagos, you will receive an error and will need to remove the old webhook so a new one can be generated.
  • After importing your data from Stripe, confirm all BIN number and bank name data appears as expected in your Pagos account. If any data is missing, contact Stripe support and request they enable details on all webhooks.

What’s Next