Appearance
Merchant portal
Use the Maytes merchant portal to track payments, configure your integration, and manage your account. Your code uses the API; your team uses the portal.
Access is set up during onboarding. The sandbox has a separate portal, accounts, and data.
Settlements
Maytes collects customer payments as checkouts are captured. Each business day, a settlement batches what you're owed and pays it to your Stripe account on a 2-business-day cycle. For example, money captured on Monday settles on Wednesday.
The portal's settlements dashboard shows:
- Daily settlements — each batch's total, status, and included checkouts.
- Per-settlement detail — the orders paid out by each settlement.
- Statements — a bank-statement-style view of your activity, grouped by checkout, for reconciling against your own records.
Your merchant_order_id, set when you create a checkout, appears with each checkout. Use it to match settlement lines to orders in your system without maintaining a separate UUID mapping.
Checkouts
Browse and search all checkouts by status, amount, and timestamp. The portal shows the same lifecycle as the API's status endpoint, so your support team can check whether an order was paid without a separate query tool.
Refunds
Issue refunds in the portal by finding a captured checkout and choosing refund. You can also issue them through the merchant API. In either case, read the outcome from the checkout status.
Integration configuration
Manage the following integration settings in the portal:
| What | Where it's covered |
|---|---|
API credentials — view your client_id, rotate your client_secret (shown once, takes effect immediately) | Authentication |
| Stripe onboarding link — generate a fresh setup link on demand | Onboarding |
| Webhook subscription — endpoint URL and event types | Webhooks |
| Webhook signing secret — view once at creation, rotate with a 2-hour grace window | Rotating your signing secret |
Send a webhook.test event — verify your endpoint end-to-end | Testing your endpoint |
| Webhook delivery log — every attempt with the HTTP status your endpoint returned | The delivery log |
Next
- Onboarding — get portal access.
- Webhooks — manage webhook configuration.
- Refunds — issue a refund and track its status.