​
Introduction

With Valmi.io Stripe Connector, you gain full control over your customer data, ensuring accurate and up-to-date information at your fingertips. This enables you to provide personalized experiences, tailor your marketing campaigns, and boost customer satisfaction. Additionally, our solution simplifies the process of distributing coupons and promotional offers, allowing you to engage with your audience effectively and drive sales.

​
Stripe Configuration

You need to create an API key to use the Stripe API through Valmi.io. To create an API key, follow the steps below:
  • Navigate to the Dashboard. In the right-hand menu, click on Developers.
  • Under the API tab, you will find your API keys. There are two types of keys: Publishable key and Secret key.
  • You’ll need the Secret key for server-side integration and accessing more advanced features.

​
Creating a Stripe Connection on valmi.io

Go to destinations on valmi.io and create a new destination. Select Stripe as the destination. Stripe Url On the next page,
  • Enter connection name, connection name can be anything that helps you to identify the connection.
  • Enter the secret key, Click on the Next button to connect to the Stripe, test the connection, and create it.
Stripe Url

​
Setting up a Sync

  1. ​
    Supported Destination Modes

Stripe supports the following destination modes. Please refer to the Destination Sync Modes for more information on the different destination modes.
Stripe ObjectUpsertSupported IdentifiersUpdateSupported Identifiers
Customer✅id✅id
Stripe Url

​
2. Mapping Source Columns to Destination Fields

While creating a Sync on valmi.io, you can select a source table and choose the previously created Stripe connection as the destination. Select one of the channels as the destination object. We have chosen the customer channel for this example. The next screen lets the user map the source columns onto the fields of the Stripe object. The picture below shows that we have selected append destination sync mode. id has been selected as the Primary Key for the Warehouse source. The source fields username have been mapped to the destination fields my_username. It also allows you to send metadata as JSON-mapped data within customer objects. Stripe Url In the next screen, you can choose a schedule for the sync and finally create the sync.

​
3. Verifying data loaded into Stripe

You can confirm the number of records sent to Stripe API from the Sync Runs Page. Stripe Url You can also confirm the data loaded into Stripe from the Stripe UI. The picture below shows the Customer Objects of Stripe. Stripe Url