Pycer Developer Portal

The Pycer Developer Portal is the unified command center for engineering teams, merchants, and enterprise integrators building on the Pycer Switching Network. Developers sign in directly using their Pycer Account credentials to provision API keys, test payment rails, inspect webhook deliveries, and monitor real-time ledger events.

Sign In to Pycer Portal

Log in directly with your Pycer Account (https://pycer.quantivogroup.com/login) to access your merchant and developer console.

Developer Hub Console

Jump straight to the Developer Hub (/admin/developer) to manage webhooks, test endpoints, and view API logs.

API Keys & Scopes

Generate, lock, unlock, and rotate scoped Bearer API tokens (/admin/api-keys) for your brands.

Interactive Sandbox

Simulate Pycer Express Prompts, card 3DS flows, inter-bank transfers, and signed webhook events.

Logging In with Your Pycer Account

Every Pycer merchant and staff account includes built-in access to the Developer Portal based on assigned Role-Based Access Control (RBAC) permissions.
1

Open the Pycer Login Gate

Navigate to https://pycer.quantivogroup.com/login (or your organization’s custom login slug if configured under Branding Settings).Need a new developer or merchant account? Register at https://pycer.quantivogroup.com/register.
2

Authenticate with Email, Password & 2FA

  1. Enter your registered Pycer email address and password.
  2. If Two-Factor Authentication (TOTP 2FA) is enabled on your account, enter the 6-digit verification code from your authenticator app at /2fa.
  3. Upon authentication, Pycer establishes an encrypted, HTTP-only session and lands you on the All Brands or brand-scoped dashboard.
3

Open the Developer Hub

In the left navigation sidebar, go to Security & Access → Developer Hub (/admin/developer) or API Keys (/admin/api-keys).Use the Brand Switcher in the top header to switch between isolated merchant brands — each brand maintains its own dedicated API keys, webhook endpoints, and ledger accounts.

Developer Portal Capabilities

Once logged in with your Pycer account, you have full access to the following developer workspaces:

1. API Key Vault (/admin/api-keys)

Generate and manage Bearer tokens across Pycer’s three API layers:
  • read scope — Query payment statuses, transactions, customer profiles, wallets, and ledger balances.
  • write scope — Initiate payment intents, trigger Pycer Express Prompts, issue refunds, and provision customer wallets.
  • admin scope — Manage brand configurations, SMS verification templates, and operational queues.
  • Lifecycle Controls — Temporarily lock (suspend) or unlock keys during security audits without breaking configuration, or permanently revoke compromised tokens.

2. Webhook Orchestrator & Simulator (/admin/developer)

  • Endpoint Registration: Register HTTPS callback URLs for real-time notifications (payment.completed, payment.failed, refund.completed, transfer.settled).
  • HMAC-SHA256 Signing Secret: View and rotate your per-brand webhook signing secret used to compute the X-Pycer-Signature header.
  • Live Webhook Tester: Click Test Webhook in the Developer Hub to dispatch a signed payment.completed event directly to your server and inspect the exact HTTP status code, latency, and response body.
  • Dead-Letter Queue (DLQ) & Replay (/admin/webhooks/events): Inspect every historical delivery attempt and one-click Replay failed events.

3. Rate Limits & IP Whitelisting (/admin/developer)

  • Monitor active API rate-limit buckets per IP and per API key.
  • Configure custom rate-limit thresholds (api_rate_limit) and whitelist trusted server IPs (rate_limit_whitelist_ips).
  • Reset rate-limit counters immediately during load testing.

4. Mobile Companion & Device Pairing (/admin/devices)

  • Generate one-time pairing OTPs to connect the Pycer Companion App via JWT + AES-256 session keys.
  • Monitor device heartbeats and automated receipt verification queues in real time.

Programmatic API Key Management

In addition to the web console, authenticated developers can manage API keys and test webhooks programmatically: