1. Getting Started
XL DCB API for Partner
  • Getting Started
    • Introduction
    • Authentication
    • Headers
    • Recurring (Subscription)
    • On-Demand (One-Time Charge)
    • Callbacks (Webhooks)
    • Errors & Response Codes
    • Notes (Partner Guidance)
  • Subscriptions
    • Create Subscription (Initiate)
      POST
    • Confirm OTP
      POST
    • Unsubscribe
      POST
  • OnDemand
    • Create one-time charge (OTP flow)
      POST
    • Confirm OTP (execute charge)
      POST
    • Check transaction status
      GET
  1. Getting Started

Introduction

Triyakom XL DCB API#

VersionDescription
1.0 (2026-11-05)Initial API

00 - Introduction#

Overview#

Triyakom provides a partner-facing API that enables third-party partners to access XL Direct Carrier Billing (DCB) services through Triyakom as an authorized aggregator. This API is designed as a universal integration layer so that multiple partners can use a consistent interface, while Triyakom manages the underlying XL-specific workflows, credentialing, token management, transaction orchestration, and operational controls required for carrier billing.
The API supports two primary billing models. The Recurring (Subscription) module is intended for subscription-based services where end users enroll in an ongoing billing cycle. It covers the complete subscription lifecycle, including subscription creation, OTP confirmation, unsubscription, and renewal-related events. Renewal charging results are delivered by XL asynchronously, and Triyakom forwards these outcomes to the partner through a callback mechanism using an outbox-based retry model to ensure reliable delivery. The On-Demand (One-Time Charge) module is intended for single-purchase charging flows (non-subscription), including optional customer inquiry, charge initiation and OTP confirmation. Similar to recurring, on-demand final outcomes may also be delivered asynchronously through internal XL notifications, and Triyakom will notify the partner via callback when applicable.
For security, all partner-facing requests require API Key + HMAC signature validation with timestamp and nonce-based anti-replay protection. Partners are expected to implement a callback endpoint to receive renewal and/or charge result notifications and to respond with HTTP 200 to acknowledge delivery.
This documentation covers two modules:
Recurring (Subscription) → /partner-dcb/v1/recurring/...
On-Demand (One-Time Charge) → /partner-dcb/v1/on-demand/...

Environments#

Production: https://pg.triyakom.me:8388
Staging: https://stg-pg.triyakom.me:8388

Base Paths#

Recurring: /partner-dcb/v1/subscriptions
On-Demand: /partner-dcb/v1/on-demand
Modified at 2026-05-12 07:17:00
Next
Authentication
Built with