Payment Gateway
  • Home
    • Welcome
      • Cheatsheet
      • Contact Us
      • QRIS
      • Virtual Account
      • E-Wallet
      • Debit & Credit Card
      • Internet Banking
      • Convinient Store
      • Buy Now, Pay Later
  • API Documentation
    • Technical Doc of Fiuu ID
      • Payment Flow Overview
      • Online Payment / Transaction Process
      • Payment Status Flow
      • Security & Data Integrity
        • Verify Key [Confidential]
        • Secret Key [Top Secret]
        • vcode
        • skey
      • Developer Account
      • Hosted Integration APIs
      • Seamless Integration APIs
      • Direct Server Integration APIs
      • Payment Request Parameters
        • Hosted Integration
          • Request Parameters
          • Channel Lists
          • Examples
        • Seamless Integration
          • Request Parameters
          • Channel Details (mpschannel)
        • Direct Server Integration
          • Request Parameters
          • API Response
          • Channel Details (TxnChannel)
      • Payment Response Parameter
        • Payment Status Notification (Merchant Webhook or the 3 Endpoints)
          • Return URL with IPN (Instant Payment Notification)
          • Notify URL with IPN
          • Callback URL with IPN
      • TL; DR?
      • Comparison Chart
      • Merchant Request APIs
      • Error Codes
      • Resources
Powered by GitBook
On this page
  • Introduction
  • Usage
  • Production
  • Sandbox
  • Direct Server API Flow
  1. API Documentation
  2. Technical Doc of Fiuu ID

Direct Server Integration APIs

Last updated 2 days ago

Introduction

Direct Server API (previously known as Seamless Payment API) allows merchants to initiate payment requests through post data. Merchant will redirect the customer/user based on the url response back to the merchant site. Merchant will be required to initiate direct status inquiry once user redirects from channel to merchant application.

If a merchant is to obtain credit card data directly from the buyer (not entering on bank or the payment gateway hosted page or URL), then the merchant must be PCI-DSS compliant to proceed. Otherwise assessment fee might be imposed by the brands, i.e. Visa or MasterCard.

This is a server-to-server call API that merchants or developers will have more control on the checkout experience and need to manage on the frontend user interface. Improper integration might cause higher drop rate on the channel.

Usage

Merchant sends HTTPs POST payment request parameter to the payment gateway. The required request parameters are provided in the .

Production

REQUEST URL:

or

Latest version:

Sandbox

or

Direct Server API Flow

REQUEST URL:

Latest version:

Direct Server integration Request Parameters section
https://pg.e2pay.co.id/RMS/API/Direct/1.4.0/index.php
https://pg.e2pay.co.id/RMS/API/Direct/latest/index.php
https://pg-sandbox.e2pay.co.id/RMS/API/Direct/1.4.0/index.php
https://pg-sandbox.e2pay.co.id/RMS/API/Direct/latest/index.php