Skip to main content

Settings

Notification Channels

Configure how invite links are delivered to merchants. At least one channel must be active to send invites.

Loading…

Email & SMS Templates

Edit the Handlebars templates used for KYB invites and review-changes notices, plus RMA & Support's own ticket and SLA templates.

Manage Templates

Platform Branding

Your own logo — shown on the login page and admin sidebar. The browser-tab favicon is generated from it automatically, so there's nothing separate to upload for that.

Logo

None

SVG or PNG with a transparent background works best.

SAML / Microsoft 365 SSO

Let admins sign in via your identity provider (e.g. Microsoft Entra ID / Azure AD). Upload your IdP's metadata XML to fill in the fields below automatically, or enter them manually.

Identity Provider

Fills in the entry point and certificate below and switches Active on. Most IdPs (Entra ID, Okta, etc.) call this "Federation Metadata XML".

Register this as the Reply URL / ACS URL in your IdP.

Download SP Metadata XML →

RMA External SSO

External support vendor login — they'll only ever see RMA & Support, nothing else in PSP. Configures a second, independent SAML identity provider, separate from your own company's staff SSO. Use this when an outsourced Customer Support company needs to work tickets without seeing the rest of your platform. New vendors are created with the role below, which must be an RMA-only role.

Vendor Identity Provider

Fills in the entry point and certificate below and switches Active on.

Register this as the Reply URL / ACS URL in the vendor's IdP.

Only RMA-only roles are listed — vendors can never see the rest of PSP. Manage roles under Roles & Permissions.

Vendor login URL: https://psp.blackcat.technology/api/v1/auth/rma-external/login

Payment & Terminal Keys

Rapyd (payment processing) and PAXSTORE (terminal fleet management) credentials, stored in Infisical — never shown in plaintext once saved. Anyone who can view this page can see whether a key is set; changing one requires the Manage Payment Keys permission.

Rapyd

…
…
…

PAXSTORE

…
…

PAXSTORE / MAXSTORE Integration

The API key and secret are managed above, under Payment & Terminal Keys. The base URL and package names are still environment-only: PAXSTORE_BASE_URL.

Core package: net.rapyd.core (env: PAXSTORE_CORE_PACKAGE)
Wrapper package: com.terminal.wrapper (env: PAXSTORE_WRAPPER_PACKAGE)

System Health

Read-only connectivity checks across every integration this platform depends on — Database, Redis, Rapyd, S3, PAXSTORE, SSO config, Infisical. Safe to re-run any time.