Stripe is a developer-focused payments platform. You can use Materialize’s webhook source to ingest data from Stripe in real time.
This guide will walk you through the steps to ingest data from Stripe to Materialize.
Before you begin
Ensure that you have a Stripe account.
Step 1. (Optional) Create a Materialize cluster
If you already have a cluster for your webhook sources, you can skip this step.
To create a Materialize cluster, follow the steps outlined in our create a cluster guide, or create a managed cluster for all your webhooks using the following SQL statement:
CREATE CLUSTER webhooks_cluster SIZE = '3xsmall';
Step 2. Set up a webhook source
Create a webhook source in Materialize to ingest data from Stripe:
CREATE SOURCE stripe_source IN CLUSTER webhooks_cluster FROM WEBHOOK BODY FORMAT JSON;
After a successful run, the command returns a
NOTICE message containing the webhook URL.
Copy and store it. You will need it for the next step.
If you missed the notice, you can find the URLs for all webhook sources in the
Step 3. Create a webhook endpoint in Stripe
In Stripe, go to Developers > Webhooks.
Click Add endpoint.
Enter the webhook URL from the previous step in the Endpoint URL field.
Configure the events you’d like to receive.
Create the endpoint.
Copy the signing secret and save it for the next step.
Step 4. Recreate the webhook source with validation
To ensure that only your Stripe account can write to your webhook source, add
validation with the
to your webhook.
First, add the signing secret from the last step to Materialize:
CREATE SECRET stripe_webhook_secret AS '<signing-secret>';
Then, drop the webhook source you created without validation:
DROP SOURCE stripe_source;
Finally, recreate the webhook source with the following
CREATE SOURCE stripe_source IN CLUSTER webhooks_cluster FROM WEBHOOK BODY FORMAT JSON; CHECK ( WITH (BODY, HEADERS, SECRET stripe_webhook_secret) ( constant_time_eq( -- Sign the timestamp and body. encode(hmac( ( -- Extract the `t` component from the `Stripe-Signature` header. regexp_split_to_array(headers->'stripe-signature', ',|=')[ array_position(regexp_split_to_array(headers->'stripe-signature', ',|='), 't') + 1 ] || '.' || body ), stripe_webhook_secret, 'sha256' ), 'hex'), -- Extract the `v1` component from the `Stripe-Signature` header. regexp_split_to_array(headers->'stripe-signature', ',|=')[ array_position(regexp_split_to_array(headers->'stripe-signature', ',|='), 'v1') + 1 ], ) ) );
For details about the Stripe signing scheme, consult the webhook signature validation section of the Stripe documentation.
Step 5. Monitor incoming data
With the source set up in Materialize, you can now monitor the incoming data from Stripe:
SELECT * FROM stripe_source LIMIT 10;
This will show you the last ten records ingested from Stripe. You may need to wait for webhook-generating events in Stripe to occur.
Step 6. Parse incoming data
Create a view to parse incoming events from Stripe. You have the option to either build your own parser view by pasting your event JSON here, or use the following starter template:
CREATE VIEW parse_stripe AS SELECT body->>'api_version' AS api_version, to_timestamp((body->'created')::int) AS created, body->'data' AS data, body->'id' AS id, (body->'livemode')::boolean AS livemode, body->'object' AS object, body->>'pending_webhooks' AS pending_webhooks, body->'request'->'idempotency_key' AS idempotency_key, body->>'type' AS type FROM stripe_source;
This view parses the incoming data, transforming the nested JSON structure into
discernible columns, such as
With the vast amount of data processed and potential network issues, it’s not
uncommon to receive duplicate records. You can use the
DISTINCT clause to
remove duplicates. For more details, refer to the webhook source
By following the steps outlined above, you will have successfully set up a seamless integration between Stripe and Materialize, allowing for real-time data ingestion using webhooks.