The merchant portal
The portal at app.paysigna.com is where you run your business on PaySigna without writing code. Everything here is also available through the API, and most of it is available to staff who will never see the API.
The sidebar, and why it is in that order
Section titled “The sidebar, and why it is in that order”The portal is organised the way a merchant thinks about money, not alphabetically — collections are something you check daily, settlements weekly, and API keys twice a year.
| Section | Holds | Read about it |
|---|---|---|
| Overview | The dashboard: what came in, what is pending, what needs attention. | — |
| Money | Transactions, Balances, Settlements, Withdrawals, Refunds. | Transactions, Getting paid, Refunds |
| Customers | Customers and Disputes. | Customers, Disputes |
| Developers | API keys and Webhooks. | API keys, Webhooks |
| Account | Team and Settings. | Your team, Settings |
Test and live are two separate worlds
Section titled “Test and live are two separate worlds”The portal has an environment switch, and it is not cosmetic. In test you see test transactions, test API keys and test webhook endpoints; in live you see real ones. They share nothing — not keys, not webhook endpoints, not signing secrets, not transaction history.
This is the same split the API enforces: a psg_test_… key cannot touch live data
and a psg_live_… key cannot touch test data. If a number in the portal does not
match what your integration reports, check which environment each of you is
looking at before anything else.
Why your colleague’s menu looks different from yours
Section titled “Why your colleague’s menu looks different from yours”Nearly every page in the portal requires a permission, and the sidebar hides what you cannot reach rather than showing you a link that answers “forbidden”. A finance-only user and an owner genuinely see different portals.
That is deliberate: a menu full of items that refuse you teaches you to ignore refusals. If you expect a section and cannot see it, you are missing a permission, not looking in the wrong place — ask whoever administers your account. See Your team.
The three things worth setting up on day one
Section titled “The three things worth setting up on day one”- A settlement destination. Without one, money collected has nowhere to go, and live charges are refused outright. Settings → Settlement.
- At least two people with access. A single account holder is an outage waiting for a lost phone. See Your team.
- A webhook endpoint, if you have an integration. It is how your own systems learn that a payment completed. See Webhooks.
If you are the developer
Section titled “If you are the developer”The portal is where you get your keys and register your webhook endpoints; the API documentation is where you find out what to do with them. Start with the quickstart — you can have a sandbox payment working before you finish reading this page.