E-Money Account Linkage
  • Introduction
  • API SPECIFICATION
    • Functional Requirement
    • Authentication
    • Merchant Resource
      • Merchant Registration
        • Merchant Registration Request
        • Merchant Registration Complete
      • Merchant Transfer to Other Account
        • Inquiry Merchant Transfer to Other Account
        • Payment Merchant Transfer to Other Account
      • Merchant Transfer To Bank
        • Inquiry Merchant Transfer Out to Bank
        • Payment Merchant Transfer Out to Bank
      • Merchant Disbursement To Bank
        • Inquiry Merchant Disbursement to Bank
        • Payment Merchant Disbursement to Bank
      • Merchant Verify User Name
      • Resend Registration SMS Token
      • Resend Registration E-Mail
      • Check Balance & Status
      • Check History
      • Change Password for Merchant Account
      • Change E-Mail
      • Change Phone Number
        • Change Phone Number Request
        • Change Phone Number Response
    • Customer Resource
      • Customer Registration
      • Check Balance & Status
      • Check History
      • Customer Upgrade
      • Customer Transaction to Other Account
        • Inquiry Customer Transfer to Other Account
        • Request Customer Transfer to Other Account
        • Confirm Customer Transfer to Other Account
      • Customer Transfer to Bank
        • Inquiry Transfer to Bank Account
        • Payment Transfer to Bank Account
      • Customer Disburse To Bank
        • Inquiry Disbursement to Bank Account
        • Payment Disbursement to Bank Account
      • QR / QRIS Feature
        • QR Internal Feature
          • QR Internal Inquiry
          • QR Internal Payment
        • Qris Feature
          • Qris Customer Inquiry
          • Qris Customer Payment
          • Qris Customer Check Status
      • Balance Limitation Check
    • Log Out
    • Transaction Code
    • Response Code
    • Get List Bank
      • Get List Bank Transfer Out
      • Get List Bank Disbursement
      • Get List Bank BI-Fast
    • List Bank
    • FAQ
Powered by GitBook
On this page
  • Purpose
  • System Architecture

Introduction

Emoney System E2Pay Global Utama

NextFunctional Requirement

Last updated 2 years ago

Purpose

This document provides requirements specification of E-Money API Integration

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 are for disbursement system:

  1. Partners are connected via the internet through each ISP.

  2. Then it will be connected to the E2Pay middleware, the middleware will be directed regarding its interconnection needs, whether to environment testing or production.

  3. Every transaction requested by the partner will be recorded on the Core E2Pay side.

  4. Furthermore, from Core it will be forwarded to the principal environment including the disbursement service which will be connected to the switching / Bank.

  5. But, before partner can do the disbursement transaction they must topup their account balance, so the transaction can be done.

Here are topology for top up account

  1. Partners top up via the Emoney M-Bayar Account topup Channel which has been informed by E2Pay

  2. Top up can be done through Internet / Mobile Banking services, ATMs, and other top up channels

  3. Every topup transaction will be processed by the Bank then the account will be validated by E2pay

  4. If it is valid, it will process the addition of the partner's account balance recorded at E2pay

  5. If the funds have been added, then other transaction processes can be continued including the Disbursement service.

Disbursement System Topology
Topup Channel Topology