Skip to main content Skip to complementary content

Stripe 

Stripe is a suite of APIs powering online payment processing and commerce solutions. You can use Stripe as a data source when landing or replicating data. with Data Gateway - Data Movement.

Supported update methods

For more information, see An overview of target update methods.

  • Change data capture (CDC)

  • Reload and compare

  • Change data capture (CDC) using Change Tables

  • Full load

  • Change data capture (CDC)

  • Reload

Preparing for authentication

To access your Stripe data, you need to authenticate the connection with a secret API key.

To create a secret key:

  1. Go to https://dashboard.stripe.com/dashboard

  2. Click Developers.

  3. Click API Keys.

  4. Click Create secret key.

  5. Set Key name to Qlik, and click Create.

  6. Copy the key to use it in the Secret Key field when creating the connection.

Information noteMake sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.
  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
Setting Description
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Secret Key Secret API key used to authenticate your Stripe account.
Company Name The name of the company that holds the Stripe account.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!