Card payments
Overview
Connects to Stripe. Your customers pay an invoice, or any record with an amount, by card and the other ways your Stripe account offers, on the Stripe page. The payment is recorded in Adminium against the record the moment Stripe says it went through, and only once, whether the webhook or Adminium’s own check finds it first. Your shop is the seller: it opens its own Stripe account and makes its own key, and the money goes from the customer straight to that account. Adminium holds no payment account, no key of its own and no money, and processes nothing; customers type their card details only on the Stripe page, so no card number reaches your server. You set it up in Studio → Payments, test mode first: a restricted key and a webhook for each mode, then a test payment with the Stripe test card, which writes nothing to your tables. Refunds are given from a record’s Payment panel or from Activity, and a refund made in the Stripe dashboard is recorded too. A disputed payment is marked and followed until the dispute ends; you answer it in the Stripe dashboard. It does not save cards, take subscriptions or put the payment form on your own page, and payments in BHD, JOD, KWD, OMR, TND and UGX are not taken online yet. It needs Adminium 0.3.33 or newer on a public https address.
What it attaches to
This one is not tied to one app. It works inside Adminium itself, and in any app that hosts add-ons.
What connecting lets it do
It needs two things from your own Stripe account, once for test and once for live: a restricted key (rk_…; a secret key is refused) and the webhook’s signing secret. Both are kept encrypted on your server, per mode, and no part of the add-on ever reaches a browser. The key is given only the access the setup card lists: start a payment and end one no longer needed, read how it ended and the amount taken, give refunds (in Stripe that access also allows changing charges), read events and disputes, the ways to pay you switched on, and which account the key belongs to. Payments are written only against the rows of the tables you choose under What can be paid. Its server half may call the two addresses below and nothing else.
Addresses its server code may reach
- api.stripe.com
- checkout.stripe.com
That list is the whole list: a call to any other address is refused and recorded.
What it needs to connect
An API key
What it adds
Where it appears 3
- In Adminium: its card under Studio → Payments → Setup, with the checklist Test key, Test webhook, Send a test payment, Live key, Live webhook, First live payment arrived
- On a record’s pay page: the ways your Stripe account has switched on, each of which sends the customer to the Stripe page
- On a record’s Payment panel and in Activity: the payments it took, with their refunds and disputes
Tables it brings 0
None — it brings no tables of its own.
Settings you configure 2
- Restricted key
- Webhook signing secret
If you switch it off
Disconnecting removes an add-on’s surfaces. It never drops the tables it created, deletes the files it wrote, or removes the rows it added — everything it wrote stays in your database. The credentials it was given are revoked and deleted with it.
What stays
Every payment and refund already recorded stays: on its record, in Activity, and in your own payments table if you chose one. It brought no tables of its own. Ways to pay by hand and recording a payment by hand work as before, and your Stripe account and the money in it are untouched.
What goes
Disconnect on its card offers two ways out. Stop new payments: no new payment starts, and Adminium keeps the key to finish the payments still waiting and to give refunds. Remove keys: the keys are deleted from this server, and Adminium can no longer finish a payment or give a refund through Stripe. Removing the key here does not cancel it at Stripe; to be safe, roll it in the Stripe dashboard.
About the demo
No demo on this site makes a real call to anyone else’s service. Every add-on ships a stand-in transport that answers from built-in data, and it is on by default. Real credentials are a self-host choice, described in the add-on’s own README.
How to switch it on None of the demos on this site include it. In your own Adminium (0.3.33 or newer), install Card payments from Add-ons, open Studio → Payments and follow the checklist on its card, test mode first. Every test pay page also offers the demo service, which needs no account at all, so the whole flow, refunds included, can be tried before anything is connected.
Adminium is not affiliated with this company.