Biller Gateway
  • Introduction
  • Reference
    • Functional Requirements
  • API Specification
    • Postpaid
      • Get Postpaid Product List
      • PLN Postpaid
        • Inquiry
        • Payment
        • Check Status
      • Telkom
        • Inquiry
        • Payment
        • Check Status
      • Mobile Postpaid
        • Inquiry
        • Payment
        • Check Status
      • PDAM
        • Inquiry
        • Payment
        • Check Status
      • BPJS
        • Inquiry
        • Payment
        • Check Status
      • PBB
        • Inquiry
        • Payment
        • Check Status
    • Prepaid
      • Get prepaid product list
      • Mobile Prepaid
        • Purchase
        • Check Status
      • PLN Prepaid
        • Inquiry
        • Purchase
        • Check Status
      • Game Voucher
        • Purchase
        • Check Status
    • General
      • GetDepositBalance
      • GetAccountLedger
    • Digital Signature
    • List of Error Code
Powered by GitBook
On this page
  • Purpose
  • System Architecture

Introduction

NextFunctional Requirements

Last updated 3 years ago

Purpose

This document provides requirements specification of Web Service API at Biller Gateway.

System Architecture

The system architecture overview that illustrate and example of the overall sysem, the connectivity and interaction with each other, is depicted in the diagram below:

  1. Client did payment or prepaid reload transaction through client channel (e.g. Internet banking, EDC, ATM, Mobile payment, etc). The request will be sent to the switching.

  2. Switching forward the request to the core banking/E-Money in order to debit customer accounts as a nominal amount of transactions conducted.

  3. Core Banking/E-Money will send a response to switching once debiting process is completed.

  4. After getting the response from the core banking, switching will proceed the request (purchase or payment) to biller GW.

  5. Biller GW forwards the request to aggregators or billers, furthermore that response will send back to Switching.

Functional Requirements