For decision makers
Pehmen is a trust layer over the payment providers you already use: it verifies who is being paid, decides whether each payment and payout should go ahead, releases seller money only when the evidence supports it, and keeps a record of all of it that a regulator, a provider and a seller can each live with.
Written for founders, CTOs, heads of risk, finance and payout operations.
This section is written for someone who will not open the dashboard every day but has to decide whether their company should. It avoids the product's own vocabulary where a plain word will do, and it links to the manual wherever a claim can be checked against a screen.
Read in this order
| Page | The question it answers |
|---|---|
| What Pehmen does | What problem is this for, and what does it actually do to my payments and payouts? |
| How it protects a payout | Walk me through the moment money is about to leave. What stops the wrong payout? |
| Security and trust | Where are my provider credentials, who can move money, and what can nobody do? |
| Data and hosting | What is stored, what is never stored, where it runs, and what happens to it. |
| Compared to what you have | Is this a payment provider, an orchestrator, a fraud tool, or something else? |
| Pilot and activation | What does trying it look like, what counts as success, and what does going live require? |
| Boundaries | The list of things Pehmen will not do or claim. Read this before any of the above if you are short on time. |
The one-paragraph version
Your platform onboards sellers and pays them out through a licensed provider. The risk you own is that a payout goes to the wrong hands: a hijacked organizer account, a redirected bank account, a refund storm when an event cancels. Pehmen does not replace your provider. It sits in front of it and makes three things true. Every seller and every payout destination has a verification record. Every payment and payout gets a decision, one of six words with a reason code, from rules you published under two-person control. And a seller's bank account cannot be changed and paid in the same breath: a change waits out a cooling-off window, both the old and the new contact are told, and a second person must approve it. The money itself never touches Pehmen.
What you can verify yourself today
- Open the seeded demo: a full workspace, already populated, no account needed.
- Create an account and connect your own Stripe test key, HitPay sandbox or Airwallex sandbox. The manual walks the path; the acceptance bar the product is built to is a stranger reaches a routed test payment in under thirty minutes without talking to us.
- Read the runtime architecture if your engineers want to see how it is put together before they touch it.