Paydia QRIS Integration Guide

Paydia QRIS is a payment method provided by Faspay Business for convenience in transactions. QRIS is a payment system utilizing a standardized QR code provided by Bank Indonesia, allowing users to make quick payments by scanning the displayed barcode with their smartphones.

Integration Step:

  1. POST Data

  2. Display QR Code

  3. Inquiry Status

  4. Payment Notification

1. POST Data Transaction

This process is used to view sending transaction data from merchants to Faspay. This POST data process is carried out when the merchant requests parameters and then Faspay will respond to the request.

URL Endpoint

Type
Development

XML

https://debit-sandbox.faspay.co.id/pws/300011/183xx00010100000

JSON

https://debit-sandbox.faspay.co.id/cvr/300011/10

POST data transactions should be done from the merchant backend, the detailed API reference can be found Here

This is an example of a POST data transaction for the Paydia QRIS channel:

A. Post Data Request

<?xml version="1.0" encoding="UTF-8" ?>
<faspay>
	<request>Transmisi Info Detil Pembelian</request>
	<merchant_id>99999</merchant_id>
	<merchant>FASPAY STORE</merchant>
	<bill_no>2020102900000000000003</bill_no>
	<bill_reff>StagingTest</bill_reff>
	<bill_date>2023-11-28 01:00:00</bill_date>
	<bill_expired>2023-11-30 23:49:00</bill_expired>
	<bill_desc>Pembayaran #12345678</bill_desc>
	<bill_currency>IDR</bill_currency>
	<bill_gross></bill_gross>
	<bill_tax>0</bill_tax>
	<bill_miscfee>0</bill_miscfee>
	<bill_total>1000000</bill_total>
	<cust_no>1</cust_no>
	<cust_name>John Doe</cust_name>
	<cust_lastname>Smith</cust_lastname>
	<payment_channel>836</payment_channel>
	<pay_type>1</pay_type>
	<bank_userid></bank_userid>
	<msisdn></msisdn>
	<email></email>
	<terminal>10</terminal>
	<billing_name>John Doe</billing_name>
	<billing_lastname>0</billing_lastname>
	<billing_address>jalan pintu air raya</billing_address>
	<billing_address_city>Jakarta Pusat</billing_address_city>
	<billing_address_region>DKI Jakarta</billing_address_region>
	<billing_address_state>Indonesia</billing_address_state>
	<billing_address_poscode>10710</billing_address_poscode>
	<billing_msisdn></billing_msisdn>
	<billing_address_country_code>ID</billing_address_country_code>
	<receiver_name_for_shipping>John Doe</receiver_name_for_shipping>
	<shipping_lastname></shipping_lastname>
	<shipping_address>jalan pintu air raya</shipping_address>
	<shipping_address_city>Jakarta Pusat</shipping_address_city>
	<shipping_address_region>DKI Jakarta</shipping_address_region>
	<shipping_address_state>Indonesia</shipping_address_state>
	<shipping_address_poscode>10710</shipping_address_poscode>
	<shipping_msisdn>08766688686</shipping_msisdn>
	<shipping_address_country_code>ID</shipping_address_country_code>
	<item>
		<id>01</id>
		<product>Handphone Type K123</product>
		<qty>1</qty>
		<amount>1000000</amount>
		<payment_plan>01</payment_plan>
		<merchant_id>99999</merchant_id>
		<tenor>00</tenor>
		<type>Smartphone</type>
		<url>http://localhost:8088/kredivo</url>
		<image_url>https://cdn.mos.cms.futurecdn.net/Mffc35PH77Dq7USrHb4qNm
-1200-80.jpg</image_url>
	</item>
	<reserve1>0</reserve1>
	<reserve2></reserve2>
	<signature>f81fed8d662bedfcf6ca88dec2426001a02a9c0c</signature>
</faspay>

B. Post Data Response

Response parameters are the parameters sent by the Faspay system in response to requests made by the merchant system. If any of these parameters do not match or contain incorrect values, the transaction will be rejected by Faspay's system. For the Paydia QRIS payment method, there are 2 types of transaction models:

  • Redirect.

  • Direct.

Here below are 2 different responses based on the transaction type model.

Parameter
Data Type
M/O/C
Description

response

Alphanumeric (50)

Mandatory

Response Name

trx_id

Numeric (16)

Mandatory

Transaction ID (Issued/generated by Faspay (Media Indonusa)) Notes: Unique Transaction ID for 1 day or as long as it hasn’t been paid and hasn’t expired

merchant_id

Numeric (5)

Mandatory

Merchant Code

merchant

Alphanumeric (32)

Mandatory

Merchant Name

bill_no

Alphanumeric (32)

Mandatory

Order Number

bill_items

Array

id

Numeric

Optional

ID product

product

Alphanumeric

Optional

Product name

amount

Numeric

Optional

Nominal product price

merchant_id

Numeric (5)

Mandatory

Merchant Code

qty

Numeric

Optional

Quantity of item

payment_plan

Numeric

Optional

Payment code 1: Full Settlement 2: Installement

tenor

Numeric

Optional

Installment Tenor 00: Full Payment 03: 3 months 06: 6 months 12: 12 months

type

Alphanumeric

Optional

Item type

url

Alphanumeric

Optional

Item Link

image_url

Alfaumeric

Optional

Image item Link

response_code

Numeric (2)

Mandatory

Response Code 00 Success

response_desc

Alphanumeric (32)

Mandatory

Response Code Description

web_url

Alphanumeric

Conditional

Used if the transaction model uses direct type, displaying only QR code in the browser.

qr_content

Alphanumeric

Conditional

Data to be encoded in a QR code that will be generated or processed. Use this if the transaction is direct type.

redirect_url

Alphanumeric

Mandatory

Link to Faspay landing page containing QR image

2. Display QR Code

Here are two ways to display the QR Code:

  • Redirect Type: To display the QR Code on Faspay's page, simply redirect using the redirect_url obtained from the POST Data Transaction Response (in JSON format), or refer to the detailed API reference for more information Here

  • Direct Type: To display the QR Code on the merchant's page, if the frontend is HTML, you can use the web_url retrieved from the post data transaction within an image tag like this: Alternatively, you can display it on a similar component without downloading. However, if the front end does not support this scenario, you should download the QR code image from that URL and then display it on the front end.

3. Inquiry Status Transaction

Inquiry Payment Status is a process of checking the status of the payment of Faspay. Merchants previously would have had to post a URL redirect to Faspay.

Endpoint URL Payment Status Inquiry

Type
Development

XML

https://debit-sandbox.faspay.co.id/pws/100004/183xx00010100000

JSON

https://debit-sandbox.faspay.co.id/cvr/100004/10

A. Request Inquiry Status

The Detailed API reference of Request Inquiry Status can be found here.

<?xml version="1.0" encoding="UTF-8" ?>
<faspay>
    <request>Inquiry Status Pembayaran</request>
    <trx_id>9999983622046227</trx_id>
    <bill_no>9333300199999123456</bill_no>
    <merchant_id>99999</merchant_id>
    <signature>ca1ed7300c72b8b14bc503826d0f54db8ed1a8b8</signature>
</faspay>

B. Response Inquiry Status

You will get the response:

<?xml version="1.0" encoding="UTF-8" ?>
<faspay>
    <response>Inquiry Status Pembayaran</response>
    <trx_id>9999983622046227</trx_id>
    <merchant_id>99999</merchant_id>
    <merchant>FASPAY DEMO</merchant>
    <bill_no>9333300199999123456</bill_no>
    <payment_reff>5761210ce5e04f658cbac7afa</payment_reff>
    <payment_date>2023-09-22 16:44:39</payment_date>
    <payment_status_code>2</payment_status_code>
    <payment_status_desc>Payment Sukses</payment_status_desc>
    <payment_total>10000.00</payment_total>
    <response_code>00</response_code>
    <response_desc>Sukses</response_desc>
</faspay>

4. Payment Notification

Payment notification from Faspay to the Merchant backend will also be triggered in event of transaction status getting updated, to ensure the merchant is securely informed. Please provide the URL and make sure it's already registered on the Faspay system The detailed API reference can be found here

PreviousDANA Subs Integration GuideNextFeatures

Last updated