Build payment apps on top of Stripe

Databases
See all your invoices, charges, refunds, and more.
Overview

The Jet Admin Stripe integration lets your app create and manage Stripe customers, start payments, look up charges and read live balance data, driven by the same tables, forms and record actions you already build in Jet. Whether a customer submits a checkout form, an account moves to a paid plan, or an agent needs to issue a refund, the whole workflow runs inside Jet, and every action is scoped by role and written to the audit log.

That covers what teams build on Stripe first: customer portals that charge on signup, checkout pages backed by a Jet form, support and finance consoles for managing customers, refunds and invoices, and revenue dashboards showing charges, subscriptions and account balance as they stand right now. Because Jet reads your own database alongside Stripe, every screen shows the payment next to the order, the ticket or the account it belongs to, and nobody needs a Stripe login to work with it.

What you can do
Create customer
Create a Stripe customer from a Jet form or workflow, so a signup, a new account record or an approved application opens a billing profile without anyone retyping it.
Get customer
Look up one customer by ID and show their billing details on the record page your support or finance team already works in.
List customers
Pull customers into a Jet table with search, filters and pagination, for example everyone created in the last 30 days or every account without a payment method.
Update customer
Write email, name, address or metadata back to Stripe from a Jet form, so the billing record and your database stop drifting apart.
Delete customer
Delete a customer when an account closes. Put it behind an approval step so it cannot happen on a single click.
Create payment intent
Start a charge for a given amount and currency from a workflow, whether that is signup, an invoice approval or a manual action on a record.
Confirm payment intent
Confirm the intent to take the money, and write the result back to the record that started it.
Get charge
Retrieve a single charge by ID to show a receipt on the customer's page or answer a support question in one screen.
List charges
Fetch charges by customer, by date range or across the account, and read them next to your own data instead of in the Stripe dashboard.
Update charge
Edit the description or metadata on a charge, for example tagging it with an order ID or the agent who handled it.
Create refund
Issue a full or partial refund from the support screen, with limits per role and an approval step above a threshold you set.
List subscriptions
Read subscriptions with their plan, status and renewal date, so churn and dunning views sit next to product usage.
Create coupon
Generate a fixed or percentage coupon from a workflow, without giving the person running the campaign a Stripe login.
List coupons
Pull available coupons into a portal or an internal screen so the team picks from real codes rather than a spreadsheet.
List invoices
Show invoices and their paid, open or overdue status, filtered to the account the person is allowed to see.
Get balance
Read the current account balance with available and pending funds, for a revenue dashboard people can open without billing access.
Use Cases
Scenario
What it looks like
Support refund console
Give agents one screen with the customer, their charges and your own order data. Refunds run with role limits and an approval step, and every action is logged, so nobody needs a Stripe login.
Revenue dashboard
Combine Stripe balance, charges and subscriptions with your product database to show revenue, failed payments and churn in one view, shared with the people who need the number.
Customer billing portal
Let each customer sign in and see only their own invoices, charges and receipts, with your branding and your domain, instead of forwarding PDFs by email.
Charge on signup
Create the customer and the payment intent as part of the signup workflow, then confirm the charge and write the result back to the record, so onboarding and billing stay one process.
Dunning and recovery
Track failed payments and overdue invoices in a queue, with owners, notes and the next action, so recovery stops depending on someone remembering to check Stripe.
Finance reconciliation
Match Stripe charges against orders, invoices or bookings in your own database, flag what does not reconcile and hand finance a working screen instead of two exports.
Coupon campaigns
Let marketing generate coupons and send them to a chosen segment, with a record of who issued what and the limits applied, and no extra Stripe seats.

Key benefits

  • Payments without a backend. Take payments from your Jet app without writing server code or bolting on a separate checkout tool.
  • Paid portals and access control. Charge on signup, hold access until the payment succeeds, and manage subscribers from the same app.
  • Live billing data on the screen. Show customers, charges, invoices and account balance as they stand right now, in both customer views and internal dashboards.
  • Payments joined to your own data. Stripe sits next to the Postgres, MySQL or Mongo you already use, so a charge appears beside the order, ticket or account it belongs to.
  • Actions with limits and a record. Refunds and cancellations run inside your app, scoped by role, held for approval above a threshold you set, and written to the audit log.
  • Complete workflows. Tie a payment to everything that follows it: update records, send the email, notify the team and grant access in one run.
  • No extra Stripe seats. Support, finance and partners work through Jet, so you stop handing out dashboard logins to see a charge.

How to connect Jet Admin with Stripe

  1. In Stripe, open Developers → API keys and copy your Secret key.
  2. In Jet Admin, open your project and add a new resource, or pick Stripe while creating a project.
  3. Choose Stripe and paste the Secret key.
  4. Jet loads your Stripe objects: Customers, Charges, Invoices, Refunds, Disputes, Plans and Products.
  5. Add the data sources you want to join with them, for example your product database or CRM.
  6. Generate the screens you need, then set role permissions on the records and fields each team can see.
  7. Add actions and workflows on top: refunds behind approval, charge on signup, alerts on failed payments.