Overview

Iris is Midtrans’ cash management solution that allows you to disburse payments to any bank accounts in Indonesia securely and easily. Iris connects to the banks’ hosts to enable seamless transfer using integrated APIs.

Glossary

For the purpose of standardization and to prevent any misunderstanding, below our the terms we are going to use in this documentation:

Partner : Iris’ main user. A partner will be given access to Iris’ API and Partner Portal;
Maker/Creator: Partner’s user that can create payout;
Approver: Partner’s user that can approve a payout;
Beneficiary: Destination account whereby the payout/transfer is intended to.

Business Flow

Iris comes in 2 business schemes: aggregator and facilitator.

Aggregator

Using aggregator scheme, a partner will have a deposit account that can be topped up from time to time using various channels. Any payout/disbursement will be done from this deposit account as the source of fund.

In a nutshell, aggregator scheme is characterized by the following:

Source of funds comes from Midtrans’ bank accounts;
Partners can top up their deposit balance before disbursements; and
Faster onboarding process.

Facilitator

Facilitator scheme lets a partner to use their own bank account as the source of funds for disbursements. In addition to initiate transfers and payouts, partner can inquire their balance and check their statements using Iris’ API.

The facilitator scheme is characterized by the following:

Source of funds comes from Partners’ own bank accounts;
Disbursements can be done as long as the account balance is sufficient; and
Onboarding process involves registering partners’ bank accounts to the bank and Midtrans.

Features

Real Time Transfers

Midtrans disbursement service connects directly to the banks’ hosts for transfer activities to ensure all disbursement is done real time;
Other transfer types such as SKN (Kliring) and Bank Indonesia’s RTGS are also supported.

Transfer Types

All transfer are done real-time for the following banks
- Mandiri
- CIMB
- BCA
- Danamon
- BNI
The rest of the banks will be done by SKN

Easy to Integrate API

Our RESTful API’s enable our partners to integrate to our solution seamlessly;
Iris’ API support: balance inquiry, create transfer, approve transfer, view statements, etc.

Web Dashboard and Analytics

Midtrans provides a portal for our partners to see all transfers history as well as analytics of their transfer activities;
The same portal can also be used to create transfer requests for transfers/disbursements through csv/excel file upload.

Setting Up Iris

Once a partner has registered, it will have an access to our sandbox environment. Iris’ partner portal will also be accessible.

Using the API key, a partner can start exploring Iris’ API. Certain API request can only be accessed based on the partner’s user role. Here below is the matrix of what a user can or cannot do:

	Creator	Approver
Create Payout	Yes	No
Release Payout	No	Yes
View/inquire Balance	Yes	Yes
View/inquire Statements	Yes	Yes

Getting Notifications

Iris allows partners to receive realtime notifications about IRIS related information (payout & top up, etc), by configuring a endpoint url on the Iris Portal.

Once configured, Iris will send a HTTP POST payload to the url, containing detail about specific event which can be seen in the notification payload section. Currently, we only send payout and top up notification.

Configuring the Endpoint URL

To setup an Endpoint URL on Iris, head over to the SETTINGS tab on the sidebar, and click on ENDPOINT URL
Click on the Edit URL button to access the page for adding a new URL
Enter the URL in the ENDPOINT URL field. Before saving the URL, test it using the Send Test Notification button. A test HTTP POST request will be sent with a payload as shown above the button.
Status of the notification is shown on the page. Please check the URL if the status code displayed is 4XX or 5XX
Save the notification URL using the Submit button. The notification URL can be modified anytime from the edit page using the Edit URL button

Notification Payload

Monetary Value

All monetary is serialized as JSON string, with some restrictions: - Only contains numeric characters and a . character as a decimal-fraction separator. - Has at most 2 decimal-fraction digits.

Example of valid monetary values: - "10000" - "10000.0" - "10000.00"

NOTE: decimal rounding might take place if the decimal-fraction value is not equal to .0

Payout Notification Payload

Parameter	Description
reference_no	Unique reference_no of a payout
amount	Amount of the processed payout
status	`approved` : payout request is approved by approver user
	`rejected` : payout request is rejected by approver user
	`processed` : payout request is sent to the bank and completed
	`completed` : payout request is sent to the bank and recieved by beneficiary account
	`failed` : payout didn’t go through
updated_at	Payout status update time in ISO8601 format
error_code	In case payout is failed we will send an error code, related to the failed payout failed payout error code and messages
error_message	In case payout is failed we will send an error message, related to the failed payout failed payout error code and messages

Top up Notification Payload

Parameter	Description
transaction_id	Unique id generated by Midtrans for top up to Bank
order_id	Unique id generated by Iris
gross_amount	Amount topped up
status	`topup`
transaction_time	Transaction time in ISO8601 format

Validating Payout Notification

In order to increase security aspect, there are several ways to ensure notification received from Iris.

Signature Key

Sample code to generate signature key in Ruby

    signature = OpenSSL::Digest::SHA512.new(payload + merchant_key).to_s

We add signature key information in our notification. The purpose of this signature key is to validate whether the notification is originated from Midtrans or not. Should the notification is not genuine, merchants can disregard the notification. We send the signature key via Header Iris-Signature.

Challenge Response

An additional mechanism we provide to verify the content and the origin of the notification is to challenge. This can be achieved by calling the Payout Details API.

Failed Payout Error Code and Messages

In case a payout is failed, we will send an error_code and error_message, explaing what went wrong. Here is a list of codes/messages.

Sample payout API response with error code

{
    "reference_no": "21b6d59f9414b2636b",
    "amount": "10000.00",
    "status": "failed",
    "updated_at": "2018-07-23T10:23:31Z",
    "error_code": "002",
    "error_message": "Invalid destination account number"
}

Error Code	Error Message
001	Invalid beneficiary name
002	Invalid destination account number
003	Invalid destination account or beneficiary name
004	General error
005	Timeout error by bank
006	Unique reference number violation
007	Identical request already processed before
008	Bank cannot authenticated request
009	Bank balance is not enough
010	Payload validation failed
011	Otp code expired / blocked
012	Beneficiary account is blocked
013	Sender and receiver account are the same
014	Monthly account balance limit exceeded
015	Account balance limit exceeded

Iris API

This Iris API contains features that can be used in your disbursement system.

HTTP(S) Request

Iris API can be requested through HTTP(S) Request to Midtrans Base URL endpoint. The HTTP(S) Header has to be used to allow proper authentication.

API Base URL

Development Environment : https://app.sandbox.midtrans.com/iris

Production Environment : https://app.midtrans.com/iris

HTTP(S) Header

Header	Value	Definition
Content-Type	application/json	The Content-Type field indicates that JSON type is acceptable to send to the recipient
Accept	application/json	The Accept field is used to specify that JSON type is acceptable for the response
Authorization	Basic `AUTH_STRING`	The Authorization field credentials can be found in Iris Portal sidemenu

Content-Type and Accept Header

In Iris API, the input and output parameters of the methods will be in JSON format. To accept JSON input and output parameters, you need to add the following HTTP(S) header:

Content-Type: application/json
Accept: application/json

Authorization Header

Generate AUTH_STRING using Ruby

    AUTH_STRING = Base64.strict_encode64(API_KEY + ":")

The authorization header utilizes API Key following HTTP(S) BASIC AUTH convention:

For Development environment, obtain API Key in Iris Sandbox Portal sidebar
For Production environment, obtain API Key in Iris Portal sidebar

Authorization: Basic AUTH_STRING

AUTH_STRING = Base64(API_KEY + :)

Iris validates HTTP request by using Basic Authentication method. You can find your API_KEY, at Iris Portal on the sidebar

Monetary Value

All monetary is serialized as JSON string, with some restrictions: - Only contains numeric characters and a . character as a decimal-fraction separator. - Has at most 2 decimal-fraction digits.

Example of valid monetary values: - "10000" - "10000.0" - "10000.00"

NOTE: decimal rounding might take place if the decimal-fraction value is not equal to .0

Ping

    $ curl -v BASE_URL/ping
    pong

Returns pong message for monitoring purpose

Create Beneficiaries

Request (application/json)

{
  "name": "John Doe",
  "account": "33452784",
  "bank": "bca",
  "alias_name": "johnbca",
  "email": "beneficiary@example.com"
}

Response 201 (application/json)

{
  "status": "created"
}

Use this API to create a new beneficiary information for quick access on the payout page in Iris Portal.

HTTP Request

POST BASE_URL/api/v1/beneficiaries

Request Parameters

Parameter	Description
name	`string` Name of the Beneficiary
account	`number` Account number of the Beneficiary
	Length should be within 6 to 20 characters
bank	`string` Bank name used by the Beneficiary
alias_name	`string` Alias name used by the Beneficiary
	Length should be less than or equal to 20 characters
	Only alphanumeric characters are allowed
email	`optional` `string` Valid Email address for Beneficiary

Update Beneficiaries

Request (application/json)

{
  "name": "John Doe",
  "account": "334527843",
  "bank": "bca",
  "alias_name": "johnbca1",
  "email": "beneficiary1@example.com"
}

Response 201 (application/json)

{
  "status": "updated"
}

Use this API to update an existing beneficiary identified by its alias_name.

HTTP Request

PATCH BASE_URL/api/v1/beneficiaries/alias_name

Request Parameters

Parameter	Description
name	`string` Name of the Beneficiary
account	`number` Account number of the Beneficiary
	Length should be within 6 to 20 characters
bank	`string` Bank name used by the Beneficiary
alias_name	`string` Alias name used by the Beneficiary
	Length should be less than or equal to 20 characters
	only alphanumeric characters are allowed
email	`optional` `string` Valid Email address for Beneficiary

List Beneficiaries

Response 201 (application/json)

[
    {
        "name": "John Doe",
        "bank": "danamon",
        "account": "1234567890",
        "alias_name": "johndanamon",
        "email": "john@danamnoexample.com"
    },
    {
        "name": "Mary Jane",
        "bank": "mandiri",
        "account": "1232133213",
        "alias_name": "marymandiri1",
        "email": "mary@mandiriexample.com"
    }
]

Use this API to fetch list of all beneficiaries saved in Iris Portal.

HTTP Request

GET BASE_URL/api/v1/beneficiaries

Create Payouts

Request (application/json)

{
  "payouts": [
    {
      "beneficiary_name": "Jon Snow",
      "beneficiary_account": "1172993826",
      "beneficiary_bank": "bni",
      "beneficiary_email": "beneficiary@example.com",
      "amount": "100000.00",
      "notes": "Payout April 17"
    },
    {
      "beneficiary_name": "John Doe",
      "beneficiary_account": "112673910288",
      "beneficiary_bank": "mandiri",
      "amount": "50000.00",
      "notes": "Payout May 17"
    }
  ]
}

Response 201 (application/json)

{
  "payouts": [
    {
      "status": "queued",
      "reference_no": "1d4f8423393005"
    },
    {
      "status": "queued",
      "reference_no": "10438f2b393005"
    }
  ]
}

This API is for Creator to create a payout. It can be used for single payout and also multiple payouts.

HTTP Request

POST BASE_URL/api/v1/payouts

Request Parameters

Parameter	Description
beneficiary_name	`string` Name of the Beneficiary
beneficiary_account	`number` Account number of the Beneficiary
beneficiary_bank	`string` Bank name used by the Beneficiary
beneficiary_email	`optional` `string` Valid Email address for Beneficiary
amount	`string (numeric)` Payout amount. Note: This is a Monetary Value, the decimal-fraction value must be equal to `.0`. Example: `10000`, `10000.0`, `10000.00`.
notes	`string` Add a note to the payout (max 17 characters and needs to be unique)
bank_account_id	`mandatory` Bank account ID registered in Iris for facilitator model, can be accessed in IRIS Portal in Bank Accounts menu

Response Parameters

Parameter	Description
status	`queued` : payout is waiting to be executed
	`processed` : payout request is sent to the bank and completed
	`completed` : payout request is sent to the bank and recieved by beneficiary account
	`failed` : payout didn’t go through
reference_no	unique ID to identify the payout

Approve Payouts

Request (application/json)

{
  "reference_nos": ["10438f2b393005", "1d4f8423393005", "1d2e1123425937"],
  "otp": "335163"
}

Response 202 (application/json)

{
  "status": "ok"
}

Use this API for Apporver to approve multiple payout request.

HTTP Request

POST BASE_URL/api/v1/payouts/approve

Request Parameters

Parameter	Description
reference_nos	`array` of `strings`, unique IDs to identify the payouts
otp	`number` `optional (based on config)` Google auth otp (QR Code will be sent to approver’s email during partner registration)

Reject Payouts

Request (application/json)

{
  "reference_nos": ["10438f2b393005", "1d4f8423393005", "1d2e1123425937"],
  "reject_reason": "Reason to reject payouts"
}

Response 202 (application/json)

{
  "status": "ok"
}

Use this API for Apporver to reject multiple payout request.

HTTP Request

POST BASE_URL/api/v1/payouts/reject

Request Parameters

Parameter	Description
reference_nos	`array` of `strings`, unique IDs to identify the payouts
reject_reason	`string` Reason to reject the payouts

Get Payout Details

Response 200 (application/json)

{
  "amount": "200000.00",
  "beneficiary_name": "Ryan Renolds",
  "beneficiary_account": "33287352",
  "bank": "Bank Central Asia ( BCA )",
  "reference_no": "83hgf882",
  "notes": "Payout June 17",
  "beneficiary_email": "beneficiary@example.com",
  "status": "queued",
  "created_by": "John Doe",
  "created_at": "2017-01-11T00:00:00Z",
  "updated_at": "2017-01-11T00:00:00Z"
}

Get details of a single payout

HTTP Request

GET BASE_URL/api/v1/payouts/reference_no

Response Params

Parameter	Description
amount	Amount of the processed payout
beneficiary_name	Name of the Beneficiary
beneficiary_account	Account number of the Beneficiary
bank	Bank name used by the Beneficiary
reference_no	Unique reference_no of a payout
notes	Note added to a payout
status	`queued` : payout is waiting to be executed
	`processed` : payout request is sent to the bank and completed
	`completed` : payout request is sent to the bank and recieved by beneficiary account
	`failed` : payout didn’t go through
beneficiary_email	Email of beneficiary (only present if email is added during payout create)
created_by	Payout created by the maker
created_at	Payout creation date in ISO8601 format
updated_at	Payout updation date in ISO8601 format

Payout History

Request (application/json)

{
  "from_date": "2016-08-11",
  "to_date": "2016-08-12"
}

Response 200 (application/json)

[
  {
    "amount": "100000.00",
    "beneficiary_name": "John Doe",
    "beneficiary_account": "27128918",
    "bank": "Bank Central Asia ( BCA )",
    "reference_no": "ab45cdyr",
    "notes": "Payout March 17",
    "status": "queued",
    "created_by": "Jane Doe",
    "created_at": "2017-01-12T00:00:00Z",
    "updated_at": "2017-01-12T00:00:00Z"
  },
  {
    "amount": "200000.00",
    "beneficiary_name": "Ryan Renolds",
    "beneficiary_account": "33287352",
    "bank": "Bank Central Asia ( BCA )",
    "reference_no": "83hgf882",
    "notes": "Payout April 17",
    "status": "queued",
    "beneficiary_email": "beneficiary@example.com",
    "created_by": "John Doe",
    "created_at": "2017-01-11T00:00:00Z",
    "updated_at": "2017-01-11T00:00:00Z"
  }
]

Returns all the payout details for specific dates

HTTP Request

GET BASE_URL/api/v1/payouts

Request Parameters

Please check Restrictions and Query Params Logic for more.

Parameter	Description
from_date	start date range for payouts (YYYY-MM-DD)
to_date	end date range for payouts (YYYY-MM-DD)

Response Parameters

Parameter	Description
amount	Amount of the processed payout
beneficiary_name	Name of the Beneficiary
beneficiary_account	Account number of the Beneficiary
bank	Bank name used by the Beneficiary
reference_no	Unique reference_no of a payout
notes	Note added to a payout
status	`queued` : payout is waiting to be executed
	`processed` : payout request is sent to the bank and completed
	`completed` : payout request is sent to the bank and recieved by beneficiary account
	`failed` : payout didn’t go through
beneficiary_email	Email of beneficiary (only present if email is added during payout create)
created_by	Payout created by the maker
created_at	Payout creation date in ISO8601 format
created_at	Payout updation date in ISO8601 format

FromToDate Restrictions

We will only provide one months data
We will not provide data which are six months old from current date
from_date and to_date has to be in ISO8601 date format (YYYY-MM-DD)
from_date is set to beginning of day (00:00:00) and to_date is set to end of day (23:59:59)

Logic for query params(from_date/to_date)

When no params passed, provides payouts of last month
- to_date (Today)
- from_date (Today - 31)
When from_date is not passed, provides payouts of one months from to_date
- to_date (to_date)
- from_date (to_date - 31)
When to_date is not passed, provides payouts from from_date to a month later
- to_date (from_date * 31)
- from_date (from_date)
When both the params are present and it does not obey the before mentioned restriction
- to_date (to_date)
- from_date (to_date - 31)
When from_date is less than 6 months, we will reset from_date and provide data upto 6 months
- from_date (the date 6 months ago from current date)

Transaction History

Request (application/json)

{
  "from_date": "2016-08-11",
  "to_date": "2016-08-12"
}

Response 200 (application/json)

[
  {
    "account": "Permata virtual account number",
    "type": "Topup",
    "amount": "300000.00",
    "status": "credit",
    "created_at": "2016-08-09T17:00:00Z"
  },
  {
    "reference_no": "1e4d9943929504",
    "beneficiary_name": "Test Benefeciary",
    "beneficiary_account": "7202",
    "account": "PT. Bank Central Asia Tbk.",
    "type": "Payout",
    "amount": "45000.00",
    "status": "debit",
    "created_at": "2016-08-09T17:00:00Z"
  }
]

List all transactions history for a month. You can specified start date and also end date for range transaction history.

HTTP Request

GET BASE_URL/api/v1/statements

Request Parameters

Please check Restrictions and Query Params Logic for more.

Parameter	Description
from_date	start date range for payouts (YYYY-MM-DD)
to_date	end date range for payouts (YYYY-MM-DD)

Response Parameters

Parameter	Description
reference_no	Unique reference_no of a payout (only if payout is present)
beneficiary_name	Name of the Beneficiary (only if payout is present)
beneficiary_account	Account number of the Beneficiary (only if payout is present)
type	Transaction Type, one of `Topup`, `Payout`, `Fee`, `Refund`
account	Name of beneficiary bank/channel used
amount	Amount for a transaction
status	Current status of the Transaction (credit/debit)
created_at	Transaction creation date in ISO8601 format

Top Up Channel Information (Aggregator)

Response 200 (application/json)

[
  {
    "id":1,
    "virtual_account_type":"mandiri_bill_key",
    "virtual_account_number":"991385480006"
  },
  {
    "id":2,
    "virtual_account_type":"permata_virtual_account_number",
    "virtual_account_number":"8778003756104047"
  }
]

Provide top up information channel for Aggregator Partner

HTTP Request

GET BASE_URL/api/v1/channels

Simulate Top Up in sandbox environment

Using Permata VA

Note your VA number that you can see on your Channels page.

permata-va-1

You can visit our Mock Payment Provider and go to Permata Virtual Account payment page. Input your VA number and click Cek Transaksi

permata-va-2

Input the number of amount for your topup, make sure the name is under midtrans athena, then click Bayar.

permata-va-3

Check if your Iris’ balance is updated.

Check Balance (Aggregator)

    {
      "balance": "25000.00"
    }

For Aggregator Partner, you need to top up to Iris’ bank account. Every partner have their own balance in Iris’ bank account. Use this API is to get current balance information.

HTTP Request

GET BASE_URL/api/v1/balance

Return Parameter

Parameter	Description
balance	Balance information for partner

Bank Accounts (Facilitator)

[
  {
    "bank_account_id": "mandiri38fd1f0e",
    "bank_name": "mandiri",
    "account_name": "John Doe",
    "account_number": "189873746743",
    "status": "in_progress"
  },
  {
    "bank_account_id": "danamon64036485",
    "bank_name": "danamon",
    "account_name": "John Snow",
    "account_number": "77975396492",
    "status": "live"
  }
]

Show list of registered bank accounts for facilitator partner

HTTP

GET BASE_URL/api/v1/bank_accounts

Response Parameters

Parameter	Description
bank_account_id	Bank account ID to be used when creating payouts
bank_name	Bank name of partner’s bank account
account_name	Account name of partner’s bank account
account_number	Account number of partner’s bank account
status	`in_progress`: Registration process of bank account still in progress
	`live`: Bank account already live and ready to use for payout

List Banks

{
    "beneficiary_banks": [
        {
            "code": "jateng_syar",
            "name": "BPD Jateng Syariah"
        },
        {
            "code": "jatim_syar",
            "name": "BPD Jatim Syariah"
        },
        {
            "code": "jatim",
            "name": "BPD Jawa Timur"
        },
        {
            "code": "kalsel",
            "name": "BPD Kalimantan Selatan"
        }
    ]
}

Show list of supported banks in IRIS.

HTTP

GET BASE_URL/api/v1/beneficiary_banks

Response Parameters

Parameter	Description
code	Code of the supported bank in IRIS
name	Name of the supported bank in IRIS

Validate Bank Account

Request

curl -X GET \
  'BASE_URL/api/v1/account_validation?bank=danamon&account=000001137298' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic AUTH_STRING' \
  -H 'Cache-Control: no-cache'

Response 200 (application/json)

{
  "account_name": "Danamon Simulator A",
  "account_no": "000001137298",
  "bank_name": "danamon"
}

Response 400 (application/json)

{
  "errors":  {  "account": [ "Account does not exist" ] }
}

Check if an account is valid, if valid return account information.

HTTP

GET BASE_URL/api/v1/account_validation?bank=#{BANK_NAME}&account=#{BANK_ACCOUNT}

Request Parameters

Parameter	Description
bank	Bank name
account	Account number

Response Parameters

Parameter	Description
bank_name	Bank name of partner’s bank account
account_name	Account name of partner’s bank account
account_no	Account number of partner’s bank account

Reference

Testing

Here is a list of dummy bank account number that can be used for testing success payout in the Sandbox Environment, please make sure that you do not use this on Production mode.

Beneficiary Bank	Beneficiary Account	Beneficiary Name
Bank Mandiri	1380011819286	Mandiri Simulator A
	1150006390175	Mandiri Simulator B
Bank Permata	4111911431	Permata Simulator A
Bank Danamon	000001137298	Danamon Simulator A
	000001111111	Danamon Simulator B
	000002678746	Danamon Simulator C
Bank BNI	0613007897	BNI Simulator A
	0238272088	BNI Simulator B
Bank BRI	504101005099530	BRI Simulator A
Bank BCA	0611101146	BCA Simulator A
Bank CIMB	800057357100	CIMB Simulator A
	860000165200	CIMB Simulator B
Gopay	08123450000	Gopay Simulator A

Supported Banks

List of banks supported in IRIS.

Bank Code	Bank Name
aceh	PT. BANK ACEH
aceh_syar	PT. BPD ISTIMEWA ACEH SYARIAH
agris	PT. BANK AGRIS
agroniaga	PT. BANK RAKYAT INDONESIA AGRONIAGA TBK.
amar	PT. BANK AMAR INDONESIA
andara	PT. BANK ANDARA
anglomas	PT. ANGLOMAS INTERNATIONAL BANK
antar_daerah	PT. BANK ANTAR DAERAH
anz	PT. BANK ANZ INDONESIA
artajasa	PT. ARTAJASA
artha	PT. BANK ARTHA GRAHA INTERNASIONAL TBK.
artos	PT. BANK ARTOS INDONESIA
bali	PT. BANK PEMBANGUNAN DAERAH BALI
bangkok	BANGKOK BANK PUBLIC CO.LTD
banten	PT. BANK BANTEN
barclays	PT BANK BARCLAYS INDONESIA
bca	PT. BANK CENTRAL ASIA TBK.
bca_syar	PT. BANK BCA SYARIAH
bengkulu	PT. BPD BENGKULU
bisnis	PT. BANK BISNIS INTERNASIONAL
bjb	PT. BANK PEMBANGUNAN DAERAH JABAR DAN BANTEN
bjb_syar	PT. BANK JABAR BANTEN SYARIAH
bni	PT. BANK NEGARA INDONESIA (PERSERO)
bni_syar	PT BANK BNI SYARIAH
bnp	PT. BANK NUSANTARA PARAHYANGAN
bnp_paribas	PT. BANK BNP PARIBAS INDONESIA
boa	BANK OF AMERICA NA
bri	PT. BANK RAKYAT INDONESIA (PERSERO)
bri_syar	PT. BANK SYARIAH BRI
btn	PT. BANK TABUNGAN NEGARA (PERSERO)
btn_syar	PT. BANK TABUNGAN NEGARA (PERSERO) UNIT USAHA SYARIAH
btpn	PT. BANK BTPN
btpn_syar	PT. BANK TABUNGAN PENSIUNAN NASIONAL SYARIAH
bukopin	PT. BANK BUKOPIN TBK.
bukopin_syar	PT. BANK SYARIAH BUKOPIN
bumiputera	PT. BANK BUMIPUTERA
bumi_artha	PT. BANK BUMI ARTA
capital	PT BANK CAPITAL INDONESIA
centratama	PT. CENTRATAMA NASIONAL BANK
chase	JP MORGAN CHASE BANK, N.A
china	BANK OF CHINA
china_cons	CHINA CONSTRUCTION
chinatrust	PT. BANK CTBC INDONESIA
cimb	PT. BANK CIMB NIAGA TBK.
cimb_syar	PT. BANK CIMB NIAGA TBK. - UNIT USAHA SYARIAH
cimb_rekening_ponsel	PT. BANK CIMB NIAGA TBK. - REKENING PONSEL
citibank	CITIBANK, NA
commonwealth	PT. BANK COMMONWEALTH
danamon	PT. BANK DANAMON INDONESIA TBK.
danamon_syar	PT. BANK DANAMON INDONESIA UNIT USAHA SYARIAH
dbs	PT. BANK DBS INDONESIA
deutsche	DEUTSCHE BANK AG.
dinar	PT. BANK DINAR INDONESIA
dipo	PT. BANK DIPO INTERNATIONAL
diy	PT. BANK PEMBANGUNAN DAERAH DIY
diy_syar	PT.BANK PEMBANGUNAN DAERAH DIY UNIT USAHA SYARIAH
dki	PT. BANK DKI
dki_syar	PT. BANK DKI UNIT USAHA SYARIAH
fama	PT. BANK FAMA INTERNATIONAL
ganesha	PT. BANK GANESHA
gopay	GO-PAY
hana	PT. BANK KEB HANA INDONESIA
harda	PT. BANK HARDA INTERNATIONAL
ekonomi	PT. BANK EKONOMI RAHARJA
hs_1906	PT. BANK HS 1906
icbc	PT. BANK ICBC INDONESIA
ina_perdana	PT. BANK INA PERDANA
index_selindo	BANK INDEX SELINDO
india	PT. BANK OF INDIA INDONESIA TBK.
jambi	PT.BANK PEMBANGUNAN DAERAH JAMBI
jasa_jakarta	PT. BANK JASA JAKARTA
jateng	PT. BANK PEMBANGUNAN DAERAH JAWA TENGAH
jateng_syar	PT. BANK PEMBANGUNAN DAERAH JAWA TENGAH
jatim	PT. BANK PEMBANGUNAN DAERAH JATIM
jatim_syar	PT.BANK PEMBANGUNAN DAERAH JATIM - UNIT USAHA SYARIAH
jtrust	PT. BANK JTRUST INDONESIA TBK.
kalbar	PT.BANK PEMBANGUNAN DAERAH KALBAR
kalbar_syar	PT.BANK PEMBANGUNAN DAERAH KALBAR UUS
kalsel	PT. BANK PEMBANGUNAN DAERAH KALSEL
kalsel_syar	PT. BANK PEMBANGUNAN DAERAH KALSEL - UNIT USAHA SYARIAH
kalteng	PT. BPD KALIMANTAN TENGAH
kaltim	PT.BANK PEMBANGUNAN DAERAH KALTIM
kaltim_syar	PT.BANK PEMBANGUNAN DAERAH KALTIM - UNIT USAHA SYARIAH
kesejahteraan	PT. BANK KESEJAHTERAAN EKONOMI
lampung	PT.BANK PEMBANGUNAN DAERAH LAMPUNG
maluku	PT.BANK PEMBANGUNAN DAERAH MALUKU
mandiri	PT. BANK MANDIRI (PERSERO) TBK.
mandiri_syar	PT. BANK SYARIAH MANDIRI TBK.
mandiri_taspen	PT. BANK MANDIRI TASPEN POS
maspion	PT. BANK MASPION
mayapada	PT. BANK MAYAPADA TBK.
maybank	PT. BANK MAYBANK INDONESIA TBK.
maybank_syar	PT. BANK MAYBANK SYARIAH INDONESIA
maybank_uus	PT. BANK MAYBANK INDONESIA TBK. UNIT USAHA SYARIAH
mayora	PT. BANK MAYORA
mega_syar	PT. BANK MEGA SYARIAH
mega_tbk	PT. BANK MEGA TBK.
mestika	PT. BANK MESTIKA DHARMA
metro	PT. BANK METRO EXPRESS
mitraniaga	PT. BANK MITRANIAGA
mitsubishi	THE BANK OF TOKYO MITSUBISHI UFJ LTD.
mizuho	PT. BANK MIZUHO INDONESIA
mnc	PT. BANK MNC INTERNASIONAL TBK.
muamalat	PT. BANK MUAMALAT INDONESIA
multiarta	PT. BANK MULTI ARTA SENTOSA
mutiara	PT. BANK MUTIARA TBK.
niaga_syar	PT. BANK NIAGA TBK. SYARIAH
nagari	PT. BANK NAGARI
nobu	PT. BANK NATIONALNOBU
ntb	PT. BANK PEMBANGUNAN DAERAH NTB
ntt	PT.BANK PEMBANGUNAN DAERAH NTT
ocbc	PT. BANK OCBC NISP TBK.
ocbc_syar	PT. BANK OCBC NISP TBK. - UNIT USAHA SYARIAH
panin	PT. PANIN BANK TBK.
panin_syar	PT. BANK PANIN SYARIAH
papua	PT.BANK PEMBANGUNAN DAERAH PAPUA
permata	PT. BANK PERMATA TBK.
permata_syar	PT. BANK PERMATA TBK. UNIT USAHA SYARIAH
prima_master	PT. PRIMA MASTER BANK
pundi	PT. BANK PUNDI INDONESIA
purba	PT. BANK PURBA DANARTA
qnb	PT. BANK QNB INDONESIA TBK.
rabobank	PT. BANK RABOBANK INTERNATIONAL INDONESIA
rbos	THE ROYAL BANK OF SCOTLAND N.V.
resona	PT. BANK RESONA PERDANIA
riau	PT. BANK PEMBANGUNAN DAERAH RIAU KEPRI
royal	PT. BANK ROYAL INDONESIA
sampoerna	PT. BANK SAHABAT SAMPOERNA
sbi	PT. BANK SBI INDONESIA
shinhan	PT. BANK SHINHAN INDONESIA
sinarmas	PT. BANK SINARMAS
sinarmas_syar	PT. BANK SINARMAS UNIT USAHA SYARIAH
stanchard	STANDARD CHARTERED BANK
sulselbar	PT. BANK SULSELBAR
sulselbar_syar	PT. BANK SULSELBAR UNIT USAHA SYARIAH
sulteng	PT. BPD SULAWESI TENGAH
sultenggara	PT. BPD SULAWESI TENGGARA
sulut	PT. BANK PEMBANGUNAN DAERAH SULUT
sumbar	BPD SUMATERA BARAT
sumitomo	PT. BANK SUMITOMO MITSUI INDONESIA
sumsel_babel	PT. BPD SUMSEL DAN BABEL
sumsel_babel_syar	PT. BPD SUMSEL DAN BABEL UNIT USAHA SYARIAH
sumut	PT. BANK PEMBANGUNAN DAERAH SUMUT
sumut_syar	PT. BANK PEMBANGUNAN DAERAH SUMUT UUS
uob	PT. BANK UOB INDONESIA
victoria	PT. BANK VICTORIA INTERNATIONAL
victoria_syar	PT. BANK VICTORIA SYARIAH
woori	PT. BANK WOORI SAUDARA INDONESIA 1906 TBK.
yudha_bhakti	PT. BANK YUDHA BHAKTI