Integrations · Commerce Built · not read in production yet
Liftable and Stripe: failed payments and churn, as counts, for payments outside Shopify
For a brand that takes some payments outside Shopify: charges attempted and failed by decline reason, refund and dispute rates, subscription churn. A restricted read-only key; no amounts are ever read or stored.
- Status as of 6 October 2026
- Read-only
What connecting it does for you
- Failed payments and their top decline reasons beside a checkout opportunity, for payments taken outside Shopify.
What Liftable reads
- Charges attempted, succeeded and failed by decline reason; refund and dispute rates; active and past-due subscriptions and churn, over 28 days. All as counts and rates.
What Liftable can write
Nothing. This connector is read-only: there is no write call in it.
What it never reads or does
- Amounts and currencies: not stored, not returned. A test walks the digest for money fields.
- A secret key: one is refused before it is stored or sent. Only a restricted key is accepted.
The permissions requested
- charge_read
- subscription_read
These are the permissions the connector asks the vendor for, as the vendor names them. The Connections page shows the same list on the row before you connect.
How to connect
- Create a restricted key in Stripe with Read on charges and refunds and on subscriptions, and paste it on the Connections page.
How often, and where the data lands
Daily digest on the connector row. Unrelated to Liftable’s own billing.
Questions
Is this about Liftable’s own billing?
No. This is your Stripe account, read for evidence. Liftable’s own subscription billing is a separate system and is not connected to this.
Solutions it feeds
Also in commerce
Last reviewed against the product on 6 October 2026.
Scan your store.
See where your store is losing revenue and what to fix first. It is free, takes about a minute, and needs no install.