Authenticate
Establish partner-scoped access using approved credentials and environment-specific controls.
Developer / API Center
Understand the integration model before you integrate.
A safe, public overview of the Valuedesign distribution and transaction lifecycle for technology teams. This page intentionally uses illustrative endpoints and contains no production credentials, keys or confidential implementation details.
POST
/api/v1/orders{
"partner_id": "VD_DEMO_PARTNER",
"sku": "DEMO_GAME_499",
"amount": 499,
"quantity": 1
}200 OK
{ "status": "fulfilled", "trace_id": "VD-TRACE-••••" }Integration lifecycle
One controlled path from partner access to reconciliation.
The exact production contract is provided during approved onboarding. The public model below explains the operating sequence only.
Discover Catalogue
Retrieve approved products, SKUs, denominations and partner-visible configuration.
Place Order
Submit a transaction with SKU, amount, quantity and idempotency context.
Fulfil & Trace
Receive controlled fulfilment status and transaction identifiers without exposing unnecessary data.
Reconcile
Use transaction status and MIS/reconciliation outputs to close operational and settlement cycles.
Developer concerns
Built around predictable transaction behavior.
Idempotency
Prevent accidental duplicate processing when clients retry a transaction.
SKU & denomination validation
Ensure the requested product and amount resolve to the intended configured SKU.
Partner / merchant scope
Apply access and configuration rules in the correct business context.
Traceability
Carry order and trace identifiers through fulfilment, reporting and reconciliation.
Error discipline
Return consistent validation, business-rule and processing failures that clients can handle safely.
Security review
Production integration details are shared only through approved onboarding and security review.
Ready to integrate?
Move from public architecture to an approved sandbox discussion.
Tell us your channel, product categories, expected use case and integration route so the correct onboarding path can be prepared.