Paylane events, verified and deduplicated.
Basalt registers a webhook endpoint and checks every signature. Payments, invoices and subscriptions land as typed rows within a second.
How it works.
Basalt creates the endpoint through the Paylane API and stores its signing secret. Each event is verified against the Paylane-Signature header, deduplicated by event ID, and acknowledged only after it is written to the log.
Set it up in three steps.
Add the source
Paste a restricted key with webhook write access. Basalt creates the endpoint, subscribes to the events you choose, and backfills 30 days.
# subscribe to billing events from Paylane basalt source add billing --paylane --events charge.*,invoice.*,customer.subscription.* ✓ endpoint we_1Q8x registered · secret stored ✓ backfilled 30 days · 412,906 events
Shape it with a view
Write plain SQL over the source. Basalt keeps the view current with every record and tracks lineage back to the topic, partition and offset.
CREATE MATERIALIZED VIEW revenue_by_min AS SELECT date_trunc('minute', ts) AS minute, currency, sum(amount) AS revenue, count(*) AS payments FROM payments WHERE status = 'captured' GROUP BY 1, 2;
Read it from anywhere
Every view is an endpoint the moment it exists. Call it over REST, connect with any Postgres client, or use the SDK from your app.
curl https://api.basalt.dev/v1/views/revenue_by_min?limit=5 \ -H "Authorization: Bearer $BASALT_TOKEN"
What you get.
Signature checks
Every payload is verified with HMAC-SHA256. Unsigned or stale requests are rejected.
Event dedup
Paylane retries are dropped by event ID, so a charge is counted once.
Typed objects
Charges, invoices and subscriptions get columns that match the pinned API version.
30-day backfill
Pull up to 30 days of past events from the Events API when you connect.
Set your data in stone.
Free up to 10M events a month. No card, no sales call. Your first pipeline is live in about four minutes.