Merchant tour

Step 01

Sign in and the home dashboard

Open Merchant panel. Use the Sandbox Demo email above. After sign-in you land on /pgui/jsp/home (the Dashboard). The product navigation is the left side menu, not a header tab bar.

Cards show Total Success, Failed, Invalid, Refunds, POS, and Chargebacks for the selected range. Amounts use major units. This desk is your Merchant ID only.

Step 02

Taking a payment

Three merchant paths collect a card on Mr Ivory hosted checkout. The shopper types the card here — your site never holds PAN.

Optional e-invoicing / Peppol PINT-AE appears on Create Invoice only when those keys are saved on My Profile. Hosted pay links still work without them. Seller legal name and TRN are never invented — use the values you entered.

Step 03

Payment reports and transaction detail

Open Payments Reports. Sale Report, Failed Reports, and Refund Reports share one detail screen: click a row to open /pgui/jsp/transactionDetail?txnId=.

2 Click any row for the same transaction detail. On Sale Report, refunds sit under More on a captured sale.

Also in this menu: Summary Reports, Settlements Report, Authorized Reports, Merchant Visibility Report, Risk Reports, Pos Report, and Batch Report. Payments Filter searches across the same ledger. Chargeback Case is its own item — a seeded example, not a scheme API.

Step 04

Performance and analytics

Open Analytics → Performance Report (/pgui/jsp/analyticsReports). The page totals Success, Failed, and Invalid for the date range, then breaks counts and volume by payment category.

When the range includes more than one currency, amount totals split by currency — for example AED 450.00 · USD 20.00 — instead of mixing units. Single-currency ranges still show one amount. Export uses the same split.

Step 05

Recurring billing

Open Billing. The path is Plans → checkout link → Subscriptions → Recurring Invoices. The first captured payment covers the first period; the next charge is one interval later.

1. Recurring — create or edit a plan in the modal (name, amount, interval). Copy the subscribe checkout link.
2. Share that URL. The customer pays once on hosted checkout.
3. On Captured, a subscription is created on the sale token. That payment is the first period.
4. Subscriptions lists active, paused, and past-due rows. You can also attach a token by hand.
5. Recurring Invoices appear after each charge. There is no separate public REST for recurring start.

The Sandbox Demo already has a sample plan named Sandbox membership and a paid recurring invoice so this path is not empty.

Step 06

Banking, payouts, and customer verify

These items are capability-gated. You only see what your merchant’s rail supports. Missing keys fail closed. This is not remittance and not platform KYC.

If Banking is missing, the rail is not offered for this merchant. Do not paste live production keys on the shared sandbox.

Step 07

KYC, business profile, and My Profile

My Business → Business Summary is hosted onboarding and KYC. Status and documents live there. Platform review is a separate admin screen you will not see as a merchant.

3 Secret Key stays masked until Show / hide. Copy only on a trusted machine. HASH uses this secret — never send it as its own field.

Lower on the same page: card processor slots (Card processor 1, Card processor 2, … in catalog order). Use this processor assigns the rail. Connect is where you paste that account’s card processor keys. Saved secrets show last 4 only. Hosted checkout, S2S, and refunds use your keys; platform env is a demo fallback. E-invoicing / Peppol PINT-AE keys, when offered, sit on this profile too.

Step 08

Staff users and privileges

Open Manage User (merchant owners and staff admins). Add User creates a colleague on the same APP_ID. User List edits role and privileges.

Roles: Super Admin, Admin, Sub-user. Privileges are grouped as View, Create / send, and Sensitive money (refunds, payouts, fund transfer, authorize). A sub-user can be limited to Payment Filter, Payment Reports, Create Invoice, View Invoice, and Chargeback. Authorize can be time-boxed as an override. Change Password is under Settings; Super Admins can also change another user’s password from the user list.

Step 09

Support chat

Signed-in panel pages include a live chat bubble at the bottom right. Ask about payments, processors, onboarding, invoices, or any other panel screen. Replies stay in the same thread.

Support may ask for your Merchant ID (APP_ID) and whether the question is about the shared sandbox or your own live processor keys, so answers match what you signed up for. Never send card numbers or CVV in chat — hosted checkout collects those. Chat is panel-only; it is not on the public holding page.

Step 10

Downloads and exports

Most list screens — Sale Report, Failed Reports, Refund Reports, Performance Report, Invoice Records, Pay By Link search, visibility, and others — offer CSV and PDF next to the date filter.

Files are branded MrIvory. They include your business name, APP_ID, the report title, and column totals. Amounts that span currencies stay split. Some reports let you hide columns before you export (CSV · Visible). Print is available on Performance Report.

Step 11

Language picker

Every panel page and these docs have a language control in the top bar. Nine locales: English, العربية, हिन्दी, اردو, Filipino, Français, Русский, 中文, Español. Arabic and Urdu use a right-to-left layout.

Changing language saves a cookie and reloads the same screen. Integration Docs under Settings opens /docs in the same tab — this tour is in the Start group.

Step 12

Webhooks and return URLs

Two places tell Mr Ivory where to send the shopper and your server after a sale.

1. Webhook URL on My Profile must be http:// or https:// (HTTPS preferred), or blank to disable. We POST JSON and wait a few seconds. There is no retry queue — if the post is missed, check Sale Report or call transaction status before you fulfil.
2. RETURN_URL on hosted checkout is where the browser goes after the shopper finishes. A return can be lost; do not fulfil from the return page alone.
3. Sale captured/declined and refund created use the same sale shape plus HASH from your secret. Recurring sends invoice paid/failed and subscription paused/cancelled events. Bodies never include PAN or CVV.
4. Staff email, SMS, and WhatsApp toggles on My Profile are extra fan-out when a sale becomes Captured. They fire once per transaction id.

Shapes and field lists: Webhooks. HASH recipe: HASH.