Identity & authorization
Authenticate callers, validate permissions and enforce resource ownership on the server.
MANAGEMENT API
Connect the platform.
Control the workflow.
An API-first management layer for onboarding, configuration, reporting and operations—with authorization and tenant boundaries at the center.
ImplementedCore capabilities are implemented; deployment scope and applicable validation are confirmed during onboarding.
management-workflow.jsonILLUSTRATIVE
// Conceptual payload, not a published API contract
{
"operation": "merchant.onboarding.review",
"reference": "DEMO-MERCHANT-001",
"context": {
"workspace": "authorized-tenant",
"correlationId": "demo-correlation-id"
},
"workflow": {
"status": "REVIEW_REQUIRED",
"approvalRequired": true
}
}Conceptual examples only. No request is sent. Obtain the agreed OpenAPI contract during onboarding.
CONTROL WITHOUT COUPLING
A management layer.
Not another processing engine.
Keep management contracts separate from provider-specific payment execution. The API coordinates approved actions; the Acquirer remains authoritative for financial outcomes.
Tenant-scoped resources
Design management operations around authorized tenants, partners, merchants and workspaces.
Configuration & governance
Coordinate provider, routing, limit and risk settings through validated management workflows.
Operational actions
Request supported inquiry, recovery and exception actions without bypassing processing controls.
Reports & financial visibility
Provide scoped transaction, clearing, settlement and reconciliation views for approved consumers.
Integration clarity
Document versioned contracts, validation, consistent errors and applicable idempotent behavior.
THE MANAGEMENT SURFACE
Your resources.
A consistent approach.
These resource families describe the planned integration scope—not a public endpoint catalogue. Request the current OpenAPI contract for the release you intend to integrate.
RESOURCE FAMILYWHAT IT ENABLESRESPONSIBILITY
Identity & accessUsers, roles, permissions and authorized scopeManagement API
Partners & merchantsHierarchy and supported onboarding operationsManagement API
ConfigurationProviders, routing policies, risk and limitsManaged configuration
Transactions & operationsSearch, lifecycle context and permitted service actionsAcquirer-authoritative
Financial operationsClearing, settlement, reconciliation and disputesAcquirer-authoritative
Reporting & auditScoped queries, exports and traceable activityPermission-controlled
FROM DESIGN TO VALIDATED INTEGRATION
An explicit path.
Fewer assumptions.
Agree the scope
Confirm the business model, release, tenants and required resource families.
Review the contract
Obtain supported OpenAPI definitions, environment access and agreed security requirements.
Integrate & validate
Test permissions, negative cases, idempotency where applicable and backend outcomes.
Approve the release
Complete UAT, operational evidence, security checks and controlled deployment sign-off.
No production endpoints, credentials or internal Swagger links are exposed on this website. The API examples are conceptual and never send a request.
DEVELOPER QUESTIONS
Clear contracts.
Clear boundaries.
Is the Management API the payment acceptance API?
No. It serves management resources and workflows. Payment ingress and financial execution belong to the acquiring/processing interfaces defined for your solution.
Can I use the sample JSON as an API specification?
No. The samples explain a management workflow only. Field names and operations are illustrative, not a promise that those endpoints or payloads exist. Obtain the release-specific OpenAPI document during onboarding.
Does the website connect to a sandbox?
No. This is a standalone public marketing site. Sample previews, code copying and the checklist run in your browser and do not call management or processing services.
LET’S BUILD TOGETHER
Build on a clearer
integration boundary.
Bring your architecture and use cases. We’ll scope the management contracts your platform needs.