Wallet payments
Overview
Connects to PayPal. Your customers pay an invoice, or any record with an amount, with their PayPal account on the PayPal page. The customer approves the payment there and comes back; Adminium then takes the money (PayPal calls this a capture) and records it against the record, once. If the customer never comes back, the webhook or Adminium’s own check takes it instead, and a payment PayPal holds shows as processing, with the reason PayPal gives. Your shop is the seller: it needs its own PayPal Business account, and the money goes from the customer straight to that account. Adminium holds no payment account, no credential of its own and no money, and processes nothing; nothing the customer types on the PayPal page reaches your server. You set it up in Studio → Payments, sandbox first: a REST app with its client ID and secret and a webhook for each mode, then a test payment as a sandbox buyer, which writes nothing to your tables. Refunds are given from a record’s Payment panel or from Activity, and a refund made in the PayPal dashboard is recorded too. A disputed payment is followed until PayPal resolves the dispute; you answer it in the PayPal dashboard. It offers one way to pay, the customer’s PayPal account, and takes the 24 currencies PayPal takes, HUF, JPY and TWD in whole units only. It needs Adminium 0.3.33 or newer on a public https address on port 443, where PayPal sends its webhooks.
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 a REST app from your own PayPal Business account, once for the sandbox and once for live: its client ID, its secret and the ID of its webhook. The secret opens the whole PayPal account — PayPal has no narrower key — so all three are kept encrypted on your server, per mode, and no part of the add-on ever reaches a browser. Every webhook’s signature is checked on your server with the webhook ID. Payments are written only against the rows of the tables you choose under What can be paid. Its server half may call the six addresses below and nothing else.
Addresses its server code may reach
- api-m.paypal.com
- api-m.sandbox.paypal.com
- www.paypal.com
- www.sandbox.paypal.com
- api.paypal.com
- api.sandbox.paypal.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 Sandbox app, Sandbox webhook, Send a test payment, Live app, Live webhook, First live payment arrived
- On a record’s pay page: Pay with PayPal, which sends the customer to the PayPal 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 3
- Client ID
- Secret
- Webhook ID
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 PayPal 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 credentials to finish the payments still waiting and to give refunds. Remove keys: the credentials are deleted from this server, and Adminium can no longer finish a payment or give a refund through PayPal. Removing them here does not cancel them at PayPal; to be safe, make a new secret for the app in the PayPal developer 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 Wallet payments from Add-ons, open Studio → Payments and follow the checklist on its card, the sandbox 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.