# Welcome to Finpay {% embed url="" %} **Finpay** is a digital financial service under **PT Finnet Indonesia (Telkom Group)**. We’ve helped businesses go digital since **2006**. Finpay provides secure money movement and bill payment capabilities for merchants, platforms, and enterprises. Whether you’re running an online store, managing enterprise transactions, or handling daily payouts, Finpay makes digital payments easier for your business — anytime, anywhere. Visit documentation below to understand more about each of our product.

Payment Gateway

/spaces/wdWV5w9iOXHhU6klMx61/pages/HxXgcWQ7yYMbnO9JDH3B

Disbursement

/spaces/wdWV5w9iOXHhU6klMx61/pages/aOjs4gC5WzIpifbjuGsn

Bill Payment

/spaces/wdWV5w9iOXHhU6klMx61/pages/S6OIBiRH2bYADZwC09vy

e-Money Linkage

/spaces/wdWV5w9iOXHhU6klMx61/pages/eCW4cL5Km31c5x5QHMzZ

Mitra Finpay

/spaces/wdWV5w9iOXHhU6klMx61/pages/gjWftssygFiSwDyEMeRu
{% hint style="info" %} If you’re an **individual / small merchant** and want a ready-to-use portal, start with **Mitra Finpay**. If you’re a **company** or need **API integration**, start with **Finpay Dashboard** onboarding. {% endhint %} ### Start here (recommended path) 1. Create a sandbox account in dashboard.finpay.id and read [Onboard to Finpay](/getting-started/registration). 2. Pick your product and integration method. 3. Test end-to-end flows in sandbox. 4. Activate your business to go live. ### Security and access If you integrate via API, read the [Security](/security/overview) section early. IP whitelist and 2FA are common go-live requirements. # Onboard to Finpay ## Create Account To start transacting with Finpay, you first need to create an account. Follow the steps below. {% stepper %} {% step %} #### Visit Finpay Dashboard Visit our [Dashboard](https://dashboard.finpay.id/register) to start your registration. {% endstep %} {% step %} #### Submit the Required Information Fill out the registration form with your full name, business name, business email, business phone number, and password. You’re also required to accept our Terms & Conditions before registering. {% endstep %} {% step %} #### Verify your Email Verify your email by entering the OTP sent to your email. {% endstep %} {% step %} #### Access Our Sandbox Environment You can now access our services in the sandbox environment using the account you created, and start testing in your development environment. {% endstep %} {% endstepper %} ## Activate Account You can only transact in the live environment (real money) after your business is fully activated. To activate your account, sign in to your dashboard, select **Activate my Business** on the homepage, and complete the following steps: 1. [Select your Business Account Type](#select-your-business-account-type) 2. [Submit business information](#submit-business-information) 3. [Upload required documents](#upload-required-document) 4. [Wait for verification status](#wait-for-verification-process) 5. [Finalize the service agreement](#finalize-service-agreement-with-finpay) ### Select your Business Account Type Finpay accepts five business account types: * Corporation (PT, CV, PMA) * Individual Corporation (Perusahaan Perorangan) * Charity (Yayasan) * Cooperation (Koperasi) * Foreign Entity (Badan Usaha Asing) {% hint style="info" %} Per January 2026, Finpay Dashboard onboarding is intended for **business entities**. For **personal / individual** usage, register via [Mitra Finpay](https://webmitra.finpay.id/login). {% endhint %}
Business Account TypeDescription
CorporationIndonesian company entity, such as PT, CV, or PMA. Choose this for standard corporate onboarding and API integration.
Individual CorporationPerseroan Perseorangan (PP). A business registered under an individual owner, but formed as a legal business entity. Common for micro and small businesses that still need a business account.
CharityYayasan (education, health, religious, social). Choose this for non-profit entities that collect and manage funds as an institution.
CooperationKoperasi. Choose this if your organization is registered as a cooperative.
Foreign EntityCompany incorporated outside Indonesia. Choose this if your legal entity is overseas and you need entity-level onboarding (requirements depend on the partnership and business model).
### Submit Business Information Finpay requires businesses to provide the business information below:
Information TypeDescription
Director/Owner Name*Full name of the director/owner
Identity Number/Passport Number*KTP identity number or passport number of the director/owner
Business Name*Your business name
Business Segment*Your business segment
Business Criteria*Your business size based on yearly transaction value:
- Micro (< Rp 2,000,000,001)
- Small (Rp 2,000,000,001 - 15,000,000,000)
- Medium (Rp 15,000,000,001 - Rp 50,000,000,000)
- Government Bodies
- Public Service Obligation
Business Address*Your business address (must be in Indonesia)
Postal Code*Postal code of your business address
Website Link*Your website link to prove business legitimacy
### Upload Required Document {% tabs %} {% tab title="Corporation" %} | Document Name | Additional Information | | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner/Director Identity\* | KTP/Passport of the Owner/Director | | Entity Tax Document\* | Entity NPWP (Nomor Pokok Wajib Pajak) | | NIB (Nomor Induk Berusaha)\* | Risk-based business permit issued by BKPM (Badan Koordinasi Penanaman Modal). | | Akta Pendirian Perusahaan\* | | | Akta Anggaran Dasar\* | | | Akta Perubahan Anggaran and/or Perubahan Pengurus Terakhir\*\* | Conditional - only required if there's any changes in the entity | | SK Kemenkum\* | Document issued by Kemenkum (Kementerian Hukum) to validate your business. Access [here](https://ahu.go.id/) for registration and more information. | | Surat Keterangan Domisili Usaha | Statement letter issued by the local government bodies/building management that state your business is indeed located in the designated address | | Surat Tanda Terdaftar PSE | Permit issued by Kominfo to operate digital platform. See the guide and register [here](https://pse.komdigi.go.id/home) if you don't have one. | | Business Permit according to Business Sector\*\* | Required permit for certain business sectors | *\*Mandatory;** ****\*\*****Conditional* {% endtab %} {% tab title="Individual Corporation" %} | Document Name | Information | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner/Director Identity\* | KTP/Passport of the Owner/Director | | Entity Tax Document\* | Entity NPWP (Nomor Pokok Wajib Pajak) | | NIB (Nomor Induk Berusaha)\* | Risk-based business permit issued by BKPM (Badan Koordinasi Penanaman Modal). | | SK Kemenkum\* | Document issued by Kemenkum (Kementerian Hukum) to validate your business. Access [here](https://ahu.go.id/) for registration and more information. | | Surat Keterangan Domisili Usaha | Statement letter issued by local government bodies stating your business is located at the designated address | | Surat Tanda Terdaftar PSE\* | Permit issued by Kominfo to operate digital platform. See the guide and register [here](https://pse.komdigi.go.id/home) if you don't have one. | *\*Mandatory;** ****\*\*****Conditional* {% endtab %} {% tab title="Charity" %} | Document Name | Additional Information | | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner/Director Identity\* | KTP/Passport of the Owner/Director | | Entity Tax Document\* | Entity NPWP (Nomor Pokok Wajib Pajak) | | NIB (Nomor Induk Berusaha)\* | Risk-based business permit issued by BKPM (Badan Koordinasi Penanaman Modal). | | Tanda Daftar Yayasan\* | Document issued by the local government for charity. Check local government website for the requirement. | | Akta Pendirian Yayasan\* | | | Akta Perubahan Anggaran and/or Perubahan Pengurus Terakhir\*\* | Conditional - only required if there's any changes in the entity | | SK Pengesahan Kemenkum\* | Document issued by Kemenkum (Kementerian Hukum) to validate your business. Access [here](https://ahu.go.id/) for registration and more information. | | Surat Keterangan Domisili Usaha | Statement letter issued by the local government bodies/building management that state your business is indeed located in the designated address | | Surat Tanda Terdaftar PSE\* | Permit issued by Kominfo to operate digital platform. See the guide and register [here](https://pse.komdigi.go.id/home) if you don't have one. | *\*Mandatory;** ****\*\*****Conditional* {% endtab %} {% tab title="Cooperation/Koperasi" %} | Document Name | Additional Information | | -------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Owner/Director Identity\* | KTP/Passport of the Owner/Director | | Entity Tax Document\* | Entity NPWP (Nomor Pokok Wajib Pajak) | | NIB (Nomor Induk Berusaha)\* | Risk-based business permit issued by BKPM (Badan Koordinasi Penanaman Modal). | | Akta Pendirian Badan Usaha\* | | | Akta Anggaran Dasar\* | | | Akta Perubahan Anggaran and/or Perubahan Pengurus Terakhir\*\* | Conditional - only required if there's any changes in the entity | | SK Pengesahan oleh Kemenkum\* | Document issued by Kemenkum (Kementerian Hukum) to validate your business. Access [here](https://ahu.go.id/) for registration and more information. | | Surat Keterangan Domisili Usaha\* | Statement letter issued by the local government bodies/building management that state your business is indeed located in the designated address | | Surat Tanda Terdaftar PSE\* | Permit issued by Kominfo to operate digital platform. See the guide and register [here](https://pse.komdigi.go.id/home) if you don't have one. | | Business Permit according to Business Sector\*\* | Required permit for certain business sectors | *\*Mandatory;** ****\*\*****Conditional* {% endtab %} {% tab title="Foreign Entity" %} | Document Name | Additional Information | | ---------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | Owner/Director Identity\* | Passport of the Owner/Director | | Entity Tax Document\* | Entity NPWP (Nomor Pokok Wajib Pajak) | | Legal Business Document from the Country of Origin\* | Legalized business document from the country of origin | | Surat Tanda Terdaftar PSE\* | Permit issued by Kominfo to operate digital platform. See the guide and register [here](https://pse.komdigi.go.id/home) if you don't have one. | | Business Permit according to Business Sector\*\* | Required permit for certain business sectors | | Business Activities Document in Bahasa Indonesia | Document that explains the entity's business activities in Bahasa Indonesia | *\*Mandatory;** ****\*\*****Conditional* {% endtab %} {% endtabs %} ### Wait for Verification Process It may take 1–2 business days for your account to be fully processed. There are three possible verification outcomes: 1. **Success**\ Your legal and business information has been verified. You can proceed to finalize the service agreement with Finpay. 2. **Pending**\ Your legal and business information is being verified by our team. Please wait 1–2 business days for processing. 3. **Failed**\ Your application has been rejected. Review the rejection reason in the dashboard to understand why. ### Finalize Service Agreement with Finpay As the last step of the onboarding process, you must finalize the service agreement with Finpay. Contact your Account Manager (AM) to complete this step. # Overview Finpay Payment Gateway is a digital payment solution by **PT Finnet Indonesia**, designed to help businesses accept payments from customers securely and efficiently — across multiple payment channels in a single platform. Finpay supports a wide range of payment channels to ensure flexibility and convenience for your customers: * **Bank Virtual Accounts (VA)** — support for major Indonesian banks, including BPD in various region * **QRIS (Static & Dynamic)** — pay using any QRIS-enabled & selected Cross Border QR application * **Credit & Debit Cards** — support for Visa and Mastercard with secured 3DS or recurring method * **E-Money**— such as OVO, DANA, LinkAja, and ShopeePay. * **Retail Outlets & Convenience Stores** — pay via Indomaret, Alfamart, and partner networks. * **PayLater** — enable flexible payment options for customers, such as Indodana, Kredivo, and ShopeePay Later # Payment Channels This table summarizes payment channels available in Finpay Payment Gateway. {% hint style="info" %} Processing time and limits can vary by bank, transfer method, and your merchant configuration. Contact Finpay if you need confirmation for a specific use case. {% endhint %} ### Definitions * **Processing time**: How fast a payment becomes **paid/confirmed** in the system. * **Settlement time**: When funds are **settled to your bank account**(for example, `T+1`). * **T**: The transaction day (working day). Example: `T+1` means the working day after the transaction. * **On-us**: Payer uses the **same bank** as the VA bank. * **Off-us**: Payer uses a **different bank** (interbank transfer). ### Payment Channel Settlement & Limit Summary
TypeChannelProcessing TimeSettlement TimeTransaction LimitFeatures
QR PaymentQRISInstantT+0 & T+1- Min: Rp 1
- Max: Rp 10.000.000
Virtual Account (VA)BCAInstantT+1On Us
- Min: -
- Max: -
Off Us
- Min: Rp 10.000
- Max: Rp 50.000.000
Virtual Account (VA)BRIInstantT+1On Us
- Min: Rp 1
- Max: Rp 9.999.999
Off Us
- Min: Rp 1
- Max: Rp 9.999.999
Virtual Account (VA)BNIInstantT+1On Us
- Min: Rp 1
- Max: Rp 50.000.000
Off Us
- Min: Rp 1
- Max: Rp 50.000.000
Virtual Account (VA)BSIInstantT+1On Us
- Min: Rp 1
- Max: Rp 50.000.000.000
Off Us
- Min: Rp 1
- Max: Rp 50.000.000.000
Virtual Account (VA)MandiriInstantT+1No limitation
Virtual Account (VA)BTNInstantT+1On Us
- Min: Rp 10.000
- Max: -
Off Us
- Min: Rp 10.000
- Max: -
Virtual Account (VA)PermataInstantT+1On Us
- Min: Rp 10.000
- Max: Rp 9.999.999.999
Off Us
- Min: Rp 10.000
- Max: Following the sender bank limitation
Virtual Account (VA)MaybankInstantT+1On Us
- Min: -
- Max: Rp 9.999.999.999
Off Us
- Min: -
- Max: Rp 9.999.999.999
Virtual Account (VA)OCBCInstantT+1On Us
- Min: -
- Max: Rp 9.999.999.999
Off Us
- Min: -
- Max: Rp 9.999.999.999
Virtual Account (VA)MuamalatInstantT+1On Us
- Min: Rp 10.000
- Max: Rp 9.999.999.999
Off Us
- Following sender transfer method limitation
Virtual Account (VA)NagariInstantT+1On Us
- Min: -
- Max: Rp 9.999.999.999
Off Us
- Min: -
- Max: Rp 9.999.999.999
Virtual Account (VA)Bank DKIInstantT+1On Us
- Min: -
- Max: Rp 9.999.999.999
Off Us
- Min: -
- Max: Rp 9.999.999.999
Virtual Account (VA)BJBInstantT+1No limitation
Virtual Account (VA)Bank Neo Commerce (BNC)InstantT+1No limitation
Virtual Account (VA)BPD Jatim (Jawa Timur)InstantT+1No limitation
Virtual Account (VA)MegaInstantT+1No limitation
e-MoneyFinpay MoneyInstantT+1Following BI regulations
e-MoneyShopeePayInstantT+1Following BI regulations
e-MoneyOVOInstantT+1Following BI regulations
e-MoneyDANAInstantT+1Following BI regulations
e-MoneyLinkAjaInstantT+1Following BI regulations
e-MoneyVirgoInstantT+1Following BI regulations
Retail Outlet (Finpay Payment Code)Indomaret, Alfamart, Pegadaian, ATMInstantT+1No limitation
PaylaterIndodanaInstantT+1No limitation
PaylaterKredivoInstantT+1Basic Account: Rp 3.000.000
PaylaterShopeepay LaterInstantT+1-
CardsContact us for more detailsInstantT+1 - T+4No limitation
### Channel details For channel-specific behavior (expiry, payer experience, etc.), check [Payment Channel Details](/payment-gateway/payment-channels/payment-channel-details) documentation. # Payment Channel Details Select a payment channel to see detailed onboarding requirements, flows, and notes. * [Cards](/payment-gateway/payment-channels/payment-channel-details/cards) * [QR Payment](/payment-gateway/payment-channels/payment-channel-details/qr-payment) * [QRIS](/payment-gateway/payment-channels/payment-channel-details/qr-payment/qris) * [Cross Border QR](broken://spaces/wdWV5w9iOXHhU6klMx61/pages/3Scc0JYBlISh9hQkQvQA) * [Virtual Account (VA)](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va) * [BCA Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bca-virtual-account) * [BRI Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bri-virtual-account) * [Mandiri Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/mandiri-virtual-account) * [e-Money](/payment-gateway/payment-channels/payment-channel-details/e-money) * [Retail Outlet](/payment-gateway/payment-channels/payment-channel-details/retail-outlet) * [Direct Debit](/payment-gateway/payment-channels/payment-channel-details/direct-debit) * [Paylater](/payment-gateway/payment-channels/payment-channel-details/paylater) # Cards ## Overview Accept card payments through major card schemes and multiple acquiring options. * Supported schemes: Visa, Mastercard, and JCB. * Supports 3DS authentication for eligible transactions. * Multiple acquirers are available. Contact Finpay for routing options. ## What we support ### Card schemes Visa, Mastercard, AMEX, and JCB are supported. ### Transaction types * One-time e-commerce payments. * Recurring payments (subscription-style charging). {% hint style="info" %} Availability can vary by acquirer, merchant profile, and risk review. {% endhint %} ### Authentication (3DS) 3DS adds an extra authentication step for the cardholder. Use 3DS to reduce unauthorized transaction risk. ### Acquiring options * Finpay can provide more than one acquirer option. * This helps with you to choose your preferred acquirer based on the card schemes coverage and rates ## Payment flows ### Standard card payment flow (high level) 1. Customer enters card details on your checkout. 2. Finpay routes the transaction to the configured acquirer. 3. You receive the transaction result and show the outcome. ### 3DS flow (high level) 1. Customer is redirected or challenged for authentication. 2. Authentication result is returned to continue authorization. 3. Authorization result is returned to your checkout. ### Recurring payment flow (high level) 1. Customer completes the first payment and consent. 2. You trigger subsequent charges on the agreed schedule. 3. Each charge returns a success or failure result. ## Operations ### Settlement Settlement timing and cut-offs depend on acquirer configuration. See [Settlement and Refund](/payment-gateway/settlement-and-refund) for more information. ### Chargebacks Chargebacks are managed under fraud and dispute handling processes. Check [Chargeback Handling](/payment-gateway/fraud-handling/chargeback-handling) for more information. ## Onboarding checklist (business view) * Confirm your merchant category and business model. * Validate your checkout and customer communication flows. * Decide if you require 3DS for all transactions or risk-based usage. * Align on acquirer configuration and go-live timeline. ## Reporting and reconciliation Use transaction statuses to reconcile payments end-to-end. * [Payment Statuses](/report/payment-statuses) # QR Payment ## Overview Finpay accept QR-based payments for supported QR networks, including QRIS and Cross-border QR. ## Supported QR products ### QRIS (Indonesia) QRIS (Quick Response Code Indonesian Standard) is a standard QR-based payment method, regulated by Bank Indonesia, that is used to facilitate transaction across Indonesia. Every single QR-based payment in Indonesia is required to follow QRIS. By its flow, QRIS can be categorized into 2 categories: 1. Merchant Presented Mode (MPM) 2. Customer Presented Mode (CPM) By its amount, QRIS can be categorized into 2 categories: 1. Static 2. Dynamic See [QRIS](/payment-gateway/payment-channels/payment-channel-details/qr-payment/qris) page to learn more. ### Cross-border QR Together with overseas switching network and collaboration lead by Bank Indonesia, Financial Institution in Indonesia can now accept QR code payment from overseas bank, including Finpay. Finpay has accept QR payment from multiple countries including, Thailand and Singapore. Contact us for more details. {% hint style="info" %} Availability depends on your merchant profile and configuration. {% endhint %} # QRIS ## Overview QRIS (Quick Response Code Indonesian Standard) is the Bank Indonesia–regulated standard for QR payments in Indonesia. All QR-based payments in Indonesia must follow QRIS. ## Payment flow ### Merchant Presented Mode (MPM) 1. The merchant requests QR generation from Finpay. 2. Finpay creates the QR and sends it to the merchant. 3. The merchant displays the QR to the customer. 4. The customer scans the QR using their issuer/bank/e-money app. 5. The customer reviews the details and confirms the payment. 6. The issuer notifies Finpay of the transaction status. 7. Finpay notifies the merchant of the final transaction status. {% hint style="info" %} Static-amount QRIS is currently available only via Mitra Finpay. Check the Mitra Finpay page for details. {% endhint %} ### Customer Presented Mode (CPM) 1. The customer generates a QR using their issuer/bank/e-money app. 2. The merchant scans the QR using their device. 3. The merchant sends the transaction details to Finpay via API. 4. Finpay requests the issuer/bank/e-money provider to debit the customer for the transaction. ## Operations ### Settlement Settlement timing depends on your configuration. See [Settlement and Refund](/payment-gateway/settlement-and-refund). ### Refunds Refund support depends on QRIS rules and your configuration. ## Limits and key rules See [Limit & Terms](broken://spaces/wdWV5w9iOXHhU6klMx61/pages/31c9RZ6c5C90qsqfyGxx). ## Reporting and reconciliation See [Payment Statuses](/report/payment-statuses). # Virtual Account (VA) ## Overview **Virtual Account (VA)** is a virtual account number used to identify a customer or a payment. The number embeds identifiers (for example, a customer ID and a unique suffix). This makes payments easier to match and confirm. ## Types VA types are commonly grouped by amount type and billing mechanism. By **amount**, there are 2 types: * **Open** * The merchant does not set the bill amount. * The customer enters the amount when paying. * **Closed** * The merchant sets the bill amount. * The customer must pay the exact amount. By **billing mechanism**, there are 2 types: * **Static** * The VA number can be reused for multiple payments. * **Dynamic** * The VA number is valid for a single payment. ## Available VA providers Finpay supports the following VA providers: * [BCA Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bca-virtual-account) * [BRI Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bri-virtual-account) * [BNI Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bni-virtual-account) * [BSI Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bsi-virtual-account) * [Mandiri Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/mandiri-virtual-account) * [BTN Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/btn-virtual-account) * [Permata Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/permata-virtual-account) * [Maybank Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/maybank-virtual-account) * [OCBC Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/ocbc-virtual-account) * [Muamalat Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/muamalat-virtual-account) * [Bank Nagari Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bank-nagari-virtual-account) * [Bank DKI Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bank-dki-virtual-account) * [BJB Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bjb-virtual-account) * [Bank Neo Commerce (BNC) Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bank-neo-commerce-bnc-virtual-account) * [BPD Jatim (Jawa Timur) Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/bpd-jatim-jawa-timur-virtual-account) * [Mega Virtual Account](/payment-gateway/payment-channels/payment-channel-details/virtual-account-va/mega-virtual-account) ## Requesting Prefix Each VA provider has its own rules for issuing VAs and allocating a dedicated prefix to a merchant. Check each provider page for details. # BCA Virtual Account ## Overview BCA Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min -, Max - * Off-us: Min Rp 10.000, Max Rp 50.000.000 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BRI Virtual Account ## Overview BRI Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 1, Max Rp 9.999.999 * Off-us: Min Rp 1, Max Rp 9.999.999 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BNI Virtual Account ## Overview BNI Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 1, Max Rp 50.000.000 * Off-us: Min Rp 1, Max Rp 50.000.000 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BSI Virtual Account ## Overview BSI Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 1, Max Rp 50.000.000.000 * Off-us: Min Rp 1, Max Rp 50.000.000.000 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Mandiri Virtual Account ## Overview Mandiri Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * No limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BTN Virtual Account ## Overview BTN Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 10.000, Max - * Off-us: Min Rp 10.000, Max - {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Permata Virtual Account ## Overview Permata Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 10.000, Max Rp 9.999.999.999 * Off-us: Min Rp 10.000, Max follows the sender bank limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Maybank Virtual Account ## Overview Maybank Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min -, Max Rp 9.999.999.999 * Off-us: Min -, Max Rp 9.999.999.999 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # OCBC Virtual Account ## Overview OCBC Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min -, Max Rp 9.999.999.999 * Off-us: Min -, Max Rp 9.999.999.999 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Muamalat Virtual Account ## Overview Muamalat Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min Rp 10.000, Max Rp 9.999.999.999 * Off-us: follows the sender transfer method limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Bank Nagari Virtual Account ## Overview Bank Nagari Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min -, Max Rp 9.999.999.999 * Off-us: Min -, Max Rp 9.999.999.999 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Bank DKI Virtual Account ## Overview Bank DKI Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * On-us: Min -, Max Rp 9.999.999.999 * Off-us: Min -, Max Rp 9.999.999.999 {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BJB Virtual Account ## Overview BJB Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * No limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Bank Neo Commerce (BNC) Virtual Account ## Overview Bank Neo Commerce (BNC) Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * No limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # BPD Jatim (Jawa Timur) Virtual Account ## Overview BPD Jatim (Jawa Timur) Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * No limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # Mega Virtual Account ## Overview Mega Virtual Account lets customers pay by transferring to a dedicated VA number. ## Processing and settlement * Processing time: Instant * Settlement time: T+1 ## Transaction limits * No limitation {% hint style="info" %} Limits can vary by transfer method and your merchant configuration. {% endhint %} # e-Money # Shopee Pay # OVO # LinkAja # DANA # Retail Outlet # Direct Debit # Paylater # Payment Instruction ## Cards ## QRIS ## Virtual Account
BCA #### Mobile Banking #### ATM #### Klik BCA
BRI #### Mobile Banking #### ATM #### Klik BCA
Mandiri #### Mobile Banking #### ATM #### Klik BCA
BNI #### Mobile Banking #### ATM #### Klik BCA
BTN #### Mobile Banking #### ATM #### Klik BCA
PERMATA #### Mobile Banking #### ATM #### Klik BCA
BJB #### Mobile Banking #### ATM #### Klik BCA
BSI #### Mobile Banking #### ATM #### Klik BCA
CIMB #### Mobile Banking #### ATM #### Klik BCA
Sinarmas #### Mobile Banking #### ATM #### Klik BCA
Maybank #### Mobile Banking #### ATM #### Klik BCA
Mega #### Mobile Banking #### ATM #### Klik BCA
Muamalat #### Mobile Banking #### ATM #### Klik BCA
DKI #### Mobile Banking #### ATM #### Klik BCA
CIMB #### Mobile Banking #### ATM #### Klik BCA
OCBC #### Mobile Banking #### ATM #### Klik BCA
## E-Money ## Retail Outlet ## Direct Debit ## Paylater # Integration Method # Core API (Host-to-Host) ## Overview **Core API (Host-to-Host)** lets your system talk directly to Finpay Payment Gateway via API. You keep the payment UI and data input inside your website or app. You do not redirect customers to a Finpay-hosted checkout page. This model does not require you to store cardholder data. Card data should never be stored on your servers. ## When to use Core API Use Core API when you need: * Full control over checkout UI and UX. * A single API integration across multiple payment channels. * Deeper control over retries, reconciliation, and custom business logic. Use [Hosted Payment](/payment-gateway/integration-method/hosted-payment) when you want the fastest go-live. ## Key integration concepts ### Authentication and access Core API access depends on your merchant configuration. Review the [Security](/security/overview) requirements early. ### Idempotency and retries Network retries happen. Design your integration to avoid duplicate charges and duplicate order creation. {% hint style="warning" %} If you are unsure how idempotency is implemented in your environment, align with Finpay before go-live. {% endhint %} ## Supported payment channels Channel availability depends on your merchant profile and configuration. See [Payment Channels](/payment-gateway/payment-channels) for the current list and limits. # Hosted Payment ## Overview **Hosted Payment** is a Finpay-hosted checkout page. You redirect the customer to Finpay to choose a payment method and complete payment. Use this when you want a fast integration with minimal checkout UI work. ## When to use Hosted Payment Hosted Payment is a good fit when you: * Want to go live quickly. * Prefer a Finpay-managed payment UI. * Need one flow for multiple payment channels. * Want Finpay to handle channel-specific payment channel instructions. {% hint style="info" %} Consider **Core API (Host-to-Host)** when you need full control of the checkout UI. {% endhint %} ## Customer experience 1. Customer starts checkout in your app or website. 2. You redirect the customer to the Finpay hosted payment page (URL). 3. Customer selects a payment method on the Finpay page. 4. Customer completes payment using the chosen channel. 5. Finpay returns the customer to your site/app (redirect). 6. You confirm the final result using the transaction status. {% hint style="info" %} Always treat the redirect as a **customer navigation event**, not a final payment confirmation. Use transaction status for reconciliation. {% endhint %} ## Supported payment methods Payment methods depend on your merchant profile and configuration. See the full list in [Payment Channels](/payment-gateway/payment-channels). ## Common pitfalls * **Assuming redirect = paid**. Redirect is not a final confirmation. * **Not handling pending states**. Some channels confirm instantly, others can take time. * **Not handling expiry**. Unpaid transactions can expire based on channel rules. * **Not showing a clear “payment in progress” state** after redirect back to your site/app. {% hint style="warning" %} If you need exact redirect parameters, expiry behavior, or status mapping, align with Finpay for your environment configuration. {% endhint %} # No Integration (Payment Link) ## Overview **Payment Link (Finpay Link)** is a shareable URL for collecting a payment. You create the link for a specific invoice or transaction. Customers open the link and pay on a Finpay-hosted page. Use this when you want to accept payments without building checkout UI. ## When to use Payment Link Payment Link is a good fit when you: * Sell via chat, social, or manual invoicing. * Need a fast way to collect one-off payments. * Do not want to integrate checkout into your site or app yet. Consider alternatives when you need tighter checkout control: * Use [Hosted Payment](/payment-gateway/integration-method/hosted-payment) for a redirect checkout from your app/site. * Use [Core API (Host-to-Host)](/payment-gateway/integration-method/core-api-host-to-host) for a fully native checkout UI. ## Customer experience 1. You generate a payment link for an invoice or order. 2. You share the link with the customer. 3. Customer opens the link and chooses a payment method. 4. Customer completes the payment on the Finpay page. 5. You confirm the final result using transaction status. {% hint style="info" %} Treat the link page as a **payment UI**. Use transaction status as the source of truth. {% endhint %} ## Workflow ![Payment Link workflow](https://hub.finpay.id/assets/images/workflow_invoice-5dc9fb1e4cbb78b7da728e585620495c.webp) ## Common use cases * Invoice payment links. * Payment reminders via email, SMS, or WhatsApp. * Collecting deposits and down payments. * Offline-to-online payments (store staff shares a link). # Settlement and Refund # Fraud Handling # Chargeback Handling ## Overview This page summarizes chargeback and refund policies for merchants accepting **credit card** payments. Chargeback handling follows the relevant **acquirer / principal / issuer (source of funds)** rules. ## Chargeback Actions for Merchant ### Repay approved outcomes If a refund and/or chargeback occurs, the merchant must repay amounts previously paid by **Finpay**. ### Respond to Finpay requests Finpay will send an official notice. The merchant must respond within **3 business days** and include: * Transaction data * Transaction log files ### Follow rules and cooperate on fraud cases The merchant must comply with applicable regulations (including Bank Indonesia) and Finpay/acquirer/principal/issuer rules. The merchant must share information related to suspicious and/or suspected fraud transactions when required. ## What Finpay can do ### Hold or deduct settlement Finpay may debit, delay, and/or deduct settlement (including placing a **hold amount**) while a chargeback is in progress. ### If a chargeback/refund is approved If the chargeback/refund is approved by the source of funds, Finpay may: * Bill the merchant and require repayment * Deduct settlement payable to the merchant * Return funds to the cardholder/customer (including via the merchant) ### Restrict refund/chargeback eligibility Finpay may determine transaction types that are not eligible for refund and/or chargeback. ### Hold transactions for risk control Finpay may hold transactions during communication issues or when fraud indicators are detected. ## Common triggers Finpay may require repayment and/or settlement deductions when: * A proven payment error occurs from Finpay to the merchant. * A dispute is caused by merchant negligence. * Card network/acquirer/issuer rules require a refund or chargeback. * The cardholder denies making the transaction. * The merchant or cardholder/customer violates applicable laws or network rules. ## Penalties and losses The merchant bears: * chargeback-related losses suffered by Finpay, and * penalties/fines imposed by the principal/acquirer/issuer, including tolerance-limit penalties. Finpay may pass through penalties related to internet transactions on the merchant’s website. ## After termination Agreement termination does not remove chargeback obligations. The merchant remains responsible for at least **90 calendar days** after the agreement ends. # Overview Finpay **Disbursement** helps you send money to your users, partners, and suppliers. Use it for payouts, refunds, commissions, payroll, and vendor payments. ### What you can do * Send single or bulk transfers. * Track transfer status from initiation to completion. * Integrate via API or run transfers without integration. ### Typical use cases * Marketplace seller payouts. * Cashback, incentives, and affiliate commissions. * Refunds and customer compensation. * Vendor and operational payments. ### Next steps * Check supported destinations in [Supported Disbursement Destination](/disbursement/supported-disbursement-destination). * Pick your approach in [Integration Method](/disbursement/integration-method). # Supported Disbursement Destination ## Overview Finpay Disbursement supports transfers to bank accounts via multiple transfer method, including * BI-Fast * Real Time Online * RTGS ## Destination types ### Bank transfer (to bank accounts) Use this destination for standard payouts to a recipient bank account. You typically need: * Bank name * Account number * Account holder name ## Supported bank destinations
View supported banks * Indonesia Eximbank * Bank Mandiri * Bank Negara Indonesia (BNI) * Bank Danamon * Bank Permata * Bank Central Asia (BCA) * Bank MayBank Indonesia * Bank Panin * Bank CIMB Niaga * Bank UOB * OCBC Indonesia * CitiBank * JPMorgan Chase Bank * Bank of America NA * Bank CHINA CONSTRUCTION Bank * Bank Artha Graha International * Bank Bangkok * Bank HSBC * Bank of Tokyo Mitsubishi UFJ, LTD. (MUFG) * Bank DBS * Bank Resona Perdania * Bank Mizuho Indonesia * Standard Chartered Bank * Bank Capital Indonesia * Bank BNP Paribas * Bank ANZ Indonesia * Deutsche Bank A.G * Bank Woori Indonesia * Bank of China (Hong Kong) Limited * Bank Bumi Arta * Bank Antar Daerah * Bank Interim Indonesia * Bank Jtrust Indonesia * Bank Mayapada * BPD Jabar Banten * Bank DKI * Bank Pembangunan Daerah DIY * Bank Jateng * Bank Jatim * BPD JAMBI * BPD Aceh * Bank SUMUT * Bank Pembangunan Daerah Sumatera Barat * Bank Riau Kepri * Bank Pembangunan Daerah Sumsel dan Babel * BPD Lampung * Bank Pembangunan Daerah Kalsel * Bank Pembangunan Daerah Kalbar * BPD KALIMANTAN TIMUR * BPD KALIMANTAN TENGAH * Bank BPD SULAWESI SELATAN * Bank SULUT * BPD NUSA TENGGARA BARAT * Bank BPD Bali * Bank NTT * BPD MALUKU * Bank Papua * BPD BENGKULU * BPD Sulawesi Tengah * BPD SULAWESI TENGGARA * Bank Nusantara Parahyangan * Bank of India Indonesia * Bank Mestika Dharma * Bank Shinhan * Bank Sinarmas * Bank Maspion * Bank Ganesha * Bank ICBC Indonesia * Bank QNB Indonesia * Bank BTN * Bank Woori Saudara Indonesia 1906 * Bank BTPN * Bank Mega * Bank Bukopin * Bank Bisnis Internasional * Bank Jasa Jakarta * Bank KEB Hana * MNC Bank Internasional * Bank Neo Commerce * Bank Mitraniaga * Bank Raya * Bank SBI Indonesia * Bank Digital BCA * Bank National Nobu * Bank Ina Perdana * Bank Prima Master * Bank Sahabat Sampoerna * Bank OKE * Bank Amar Indonesia * Bank SeaBank Indonesia * Bank Jago * Bank Multi Artha Sentosa * Bank Mayora * Bank Index Selindo * Bank Eksekutif * Centratama National Bank * Super Bank Indonesia * Bank Mandiri Taspen dhi Bank Sinar Harapan Bali * Bank VICTORIA INTERNASIONAL * Bank Allo dhi Bank Harda International * Bank AGRIS * Bank CTBC Indonesia * Bank Commonwealth * Bank Danamon Syariah * Bank Permata Syariah * Bank Maybank Syariah Indonesia * Bank CIMB Niaga, TBK Syariah * Bank OCBC NISP Syariah * Bank DKI Syariah * Bank Pembangunan Daerah DIY Syariah * Bank Jateng Syariah * Bank Jatim Syariah * BPD Jambi Syariah * Bank BPD Aceh Syariah * Bank Sumut Syariah * Bank Nagari Syariah * Bank Pembangunan Daerah Sumsel dan Babel Syariah * Bank Pembangunan Daerah Kalsel Syariah * Bank Pembagunan Daerah Kalbar Syariah * BPD Kalimantan Timur Syariah * Bank SULSELBAR Syariah * Bank NTB Syariah * Bank Muamalat Indonesia * Bank Sinarmas Syariah * BTN Syariah * Bank TABUNGAN PENSIUNAN NASIONAL Syariah * Bank Victoria Syariah * Bank BJB SYARIAH * Bank Syariah Indonesia (BSI) * Bank SYARIAH MEGA INDONESIA * Bank Panin Syariah * Bank Syariah Bukopin * BCA Syariah * Bank Jago Syariah * Bank ALADIN SYARIAH * PT. BPD BANTEN
# Integration Method Finpay Disbursement supports two ways to create transfers. Pick the one that matches your volume and how much automation you need.
OptionDocs
Core API (Host-to-Host)
Trigger disbursements directly from your system.		/spaces/wdWV5w9iOXHhU6klMx61/pages/KnM1tBWgjaNlUu253g96
No Integration (Dashboard)
Run single or batch transfers from the dashboard.		/spaces/wdWV5w9iOXHhU6klMx61/pages/Kz2fqYOTCkXzLDEFyltl
### How to choose Use **Core API (Host-to-Host)** when you: * Need automated payouts from your product or back office. * Send transfers at high volume or on a schedule. * Want your system to track transfer status end-to-end. Use **No Integration (Dashboard)** when you: * Want a no-code setup. * Only need occasional payouts. * Have an ops team that runs transfers manually. {% hint style="info" %} Many teams start with **Dashboard** to validate operations, then move to **Core API** for scale. {% endhint %} ### Next steps * Confirm supported banks and transfer rails in [Supported Disbursement Destination](/disbursement/supported-disbursement-destination). * Continue to [Core API (Host-to-Host)](/disbursement/integration-method/core-api-host-to-host) or [No Integration (Dashboard)](/disbursement/integration-method/no-integration-dashboard). # Core API (Host-to-Host) ## Overview **Core API (Host-to-Host)** lets you trigger disbursements directly from your system via API. Use it to send money to users, partners, or suppliers without using a manual portal. ## What you need before you start * A Finpay Disbursement account and active credentials. * A configured destination list for your use case. See [Supported Disbursement Destination](/disbursement/supported-disbursement-destination). * Sufficient balance in your disbursement account (top-up model). ## Getting started {% stepper %} {% step %} ### Set up your account Sign up and complete the required activation steps so you can start disbursing. {% endstep %} {% step %} ### Test in your environment Use the API to test disbursement flows end-to-end. Validate status updates and reconciliation in your system. {% endstep %} {% step %} ### Top up your disbursement balance Disbursement uses a **top-up balance** model. You maintain funds in your Finpay balance. Finpay holds the funds securely until you instruct a payout. Top up via bank transfer based on your agreed settlement instructions. {% endstep %} {% step %} ### Start disbursing Once your balance is available, create transfers via API. Track results using transfer statuses. {% endstep %} {% endstepper %} {% hint style="info" %} If you need a no-code option, use the **No Integration** flow under Disbursement Integration Method. {% endhint %} # No Integration (Dashboard) ## Overview **No Integration (Dashboard)** lets you send money without building an API integration. Use the [Finpay dashboard](https://dashboard.finpay.id) to run **single transfers** or **batch transfers** (via file upload). ## When to use No Integration Use this option when you: * Want a no-code setup. * Only need occasional payouts. * Have an ops team that runs transfers manually. * Want to start quickly before moving to API automation. For automated payouts from your system, use [Core API (Host-to-Host)](/disbursement/integration-method/core-api-host-to-host). ## What you need before you start * A Finpay Disbursement account with dashboard access. * A configured destination list for your use case. See [Supported Disbursement Destination](/disbursement/supported-disbursement-destination). * Sufficient balance in your disbursement account (top-up model). ## Getting started {% stepper %} {% step %} ### Set up your account Register your business account and complete the required activation steps. {% endstep %} {% step %} ### Log in to the dashboard Use the dashboard to access: * [Single Disbursement](/disbursement/integration-method/no-integration-dashboard/single-disbursement) * [Batch Disbursement](/disbursement/integration-method/no-integration-dashboard/bulk-disbursement) {% endstep %} {% step %} ### Top up your disbursement balance Disbursement uses a **top-up balance** model. You maintain funds in your Finpay balance. Finpay holds the funds securely until you instruct a payout. {% endstep %} {% step %} ### Send transfers * Use **Single Disbursement** for one-off transfers. * Use **Batch Disbursement** to upload a file for bulk payouts. {% endstep %} {% endstepper %} {% hint style="info" %} Batch transfers are done via spreadsheet upload. Follow the format shown in the dashboard. {% endhint %} # Single Disbursement ## Single Disbursement (Dashboard) Use **Single Disbursement** to send one transfer from the Finpay dashboard. ### Request a disbursement {% hint style="info" %} You need a dashboard user with the role **Merchant Disburse Requestor**. {% endhint %} {% stepper %} {% step %} ### Open the request screen 1. Log in to the dashboard. 2. Go to **Finpay Disbursement** → **Disbursement Request**. 3. Select **Single Disbursement** (top of the page). {% endstep %} {% step %} ### Select the merchant 1. Pick the merchant you want to use. 2. Click **Add+**.

Select a merchant and click Add+

{% endstep %} {% step %} ### Fill in transfer details Fill in the required fields: * Recipient (destination account) * Amount * Note (if required) Validate the destination account number if the dashboard asks you to.

Fill recipient, amount, and notes

{% endstep %} {% step %} ### Submit the request Click **Submit** to send the disbursement request for approval. {% endstep %} {% endstepper %} ### Approve a disbursement {% hint style="info" %} You need a dashboard user with the role **Merchant Disburse Approver**. {% endhint %} {% stepper %} {% step %} ### Open the approval screen 1. Log in to the dashboard. 2. Go to **Finpay Disbursement** → **Disbursement Approval**. 3. Select **Single Disbursement** (top of the page). {% endstep %} {% step %} ### Review and take action Review the request details, then: * Click **Approve (**:white\_check\_mark:**)** to continue the disbursement. * Click **Reject (** :x: **)** to reject the request.
{% endstep %} {% step %} ### What happens next Finpay continues processing based on your approval decision. {% endstep %} {% endstepper %} # Bulk Disbursement ## Bulk Disbursement (Dashboard) Use **Bulk Disbursement** to send multiple transfers from the Finpay dashboard. ### Request a disbursement {% hint style="info" %} You need a dashboard user with the role **Merchant Disburse Requestor**. {% endhint %} {% stepper %} {% step %} ### Open the request screen 1. Log in to the dashboard. 2. Go to **Finpay Disbursement** → **Disbursement Request**. 3. Select **Bulk Disbursement** (top of the page). {% endstep %} {% step %} ### Select the merchant 1. Pick the merchant you want to use. 2. Click **Add+**.

Select a merchant and click Add+

{% endstep %} {% step %} ### Fill in transfer details Fill in the required fields
{% endstep %} {% step %} ### Submit the request Click **Submit** to send the disbursement request for approval. {% endstep %} {% endstepper %} ### Approve a disbursement {% hint style="info" %} You need a dashboard user with the role **Merchant Disburse Approver**. {% endhint %} {% stepper %} {% step %} ### Open the approval screen 1. Log in to the dashboard. 2. Go to **Finpay Disbursement** → **Disbursement Approval**. 3. Select **Single Disbursement** (top of the page). {% endstep %} {% step %} ### Review and take action Review the request details, then: * Click **Approve (**:white\_check\_mark:**)** to continue the disbursement. * Click **Reject (** :x: **)** to reject the request.
{% endstep %} {% step %} ### What happens next Finpay continues processing based on your approval decision. {% endstep %} {% endstepper %} # Overview Finpay **Bill Payment** lets you sell bill payments and digital products inside your app or channel. Offer common billers such as utilities, telco, and e-money top up. ### What you can do * Provide a bill payment experience via widget or API. * Support multiple bill categories and billers in one integration. * Reconcile transactions using reports and statuses. ### Typical use cases * Super-app bill payment menu. * Agent / outlet-based bill payment sales. * Employee benefit and internal bill payment programs. ### Next steps * Choose your implementation in [Integration Method](/bill-payment/integration-method). * Browse billers in [Available Billers](/bill-payment/available-billers). # Integration Method # Bill Payment Widget Finpay Widget Bill Payment is a solution that enables the use of widgets to integrate bill payment and purchases. It is possible to incorporate this widget into websites or applications to facilitate payments for users without requiring them to exit the platform they are now using. # Core API (Host-to-Host) Finpay Billing provides payment collection and processing for various service and biller providers. Finpay Billing provides customers with a wide range of options to conveniently make transactions. Finpay Billing API (Application Programming Interface) is a set of protocols, tools, and rules that allow different software applications to communicate and exchange information with our API. Finpay Billing serves as a bridge between channel (your Business) and the Biller (Billing Provider). Finpay Billing API enables developers to integrate our Finpay Billing API into your own applications, websites, or systems. # Available Billers ## Overview This page lists billers available in Finpay Bill Payment. Availability depends on your merchant profile and configuration. ## Categories ### Multifinance * Adira Roda Dua * Astra Credit Company (ACC Finance) * BNI Finance * Bussan Auto Finance * CIMB Auto Finance * Clipan Finance * Mega Finance * Mitra Pinastika Mustika Finance * Pegadaian * Smart Finance * Toyota Astra Finance * Woka Finance Details: [Multifinance](/bill-payment/available-billers/multifinance) ### Insurance * BPJS Kesehatan * BPJS Kesehatan - Denda * BPJS Kesehatan - VA * BPJS Ketenagakerjaan * BPJS Ketenagakerjaan - BPU (Bukan Penerima Upah) * BPJS Ketenagakerjaan - PMI (Perlindungan Migran Indonesia) * BPJS Ketenagakerjaan - PU (Penerima Upah) Details: [Insurance](/bill-payment/available-billers/insurance) ### Utilities * PLN Prepaid * PLN Postpaid * PDAM Details: [Utilities](/bill-payment/available-billers/utilities) ### Telco * Telkomsel Prepaid * Telkomsel Halo (Postpaid) * XL Postpaid Details: [Telco](/bill-payment/available-billers/telco) ### Travel * (No billers listed yet) Details: [Travel](/bill-payment/available-billers/travel) ### Transportation * KAI * Garuda Airlines * Signal Samsat Details: [Transportation](/bill-payment/available-billers/transportation) ### Property * Jaya Real Property Details: [Property](/bill-payment/available-billers/property) ### Internet/TV * ICONNET * by.U * MNC Play * MNC Vision * IndiHome * Transvision Details: [Internet/TV](/bill-payment/available-billers/internet-tv) ### e-Money Top Up * DANA Top Up * ShopeePay Top Up * OVO Top Up * GoPay Top Up Details: [e-Money Top Up](/bill-payment/available-billers/e-money-top-up) ## Notes * Biller names are customer-facing labels. * Exact biller codes and required fields depend on the API/product configuration. # Utilities ## Overview Utility billers support payments for electricity and water services. Availability depends on your merchant profile and configuration. ## Supported billers * PLN Prepaid * PLN Postpaid * PDAM ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Electricity (PLN) ## Overview PLN billers support electricity payments. Availability depends on your merchant profile and configuration. ## Supported billers * [PLN Prepaid](/bill-payment/available-billers/utilities/electricity-pln/pln-prepaid) * [PLN Postpaid](/bill-payment/available-billers/utilities/electricity-pln/pln-postpaid) ## Related * See the full list in [Utilities](/bill-payment/available-billers/utilities). # PLN Prepaid ## Overview Prepaid PLN electricity token purchase. Availability depends on your configuration. ## Related * [Electricity (PLN)](/bill-payment/available-billers/utilities/electricity-pln) * [Utilities](/bill-payment/available-billers/utilities) # PLN Postpaid ## Overview PLN postpaid electricity bill payment. Availability depends on your configuration. ## Related * [Electricity (PLN)](/bill-payment/available-billers/utilities/electricity-pln) * [Utilities](/bill-payment/available-billers/utilities) # PDAM ## Overview PDAM billers support water utility bill payments. Availability depends on your configuration. ## Related * [Utilities](/bill-payment/available-billers/utilities) # Telco ## Overview Telco billers support mobile prepaid and postpaid payments. Availability depends on your merchant profile and configuration. ## Supported billers ### Prepaid * Telkomsel Prepaid ### Postpaid * Telkomsel Halo * XL Postpaid ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Prepaid ## Overview Prepaid telco billers support airtime/data purchases. ## Supported billers * [Telkomsel Prepaid](/bill-payment/available-billers/telco/prepaid/telkomsel-prepaid) ## Related * [Telco](/bill-payment/available-billers/telco) # Telkomsel Prepaid ## Overview Telkomsel prepaid top up / purchase. Availability depends on your configuration. ## Related * [Telco](/bill-payment/available-billers/telco) # Postpaid ## Overview Postpaid telco billers support monthly bill payments. ## Supported billers * [XL Postpaid](/bill-payment/available-billers/telco/postpaid/xl-postpaid) * [Telkomsel Halo](/bill-payment/available-billers/telco/postpaid/telkomsel-halo) ## Related * [Telco](/bill-payment/available-billers/telco) # XL Postpaid ## Overview XL postpaid bill payment. Availability depends on your configuration. ## Related * [Telco](/bill-payment/available-billers/telco) # Telkomsel Halo ## Overview Telkomsel Halo postpaid bill payment. Availability depends on your configuration. ## Related * [Telco](/bill-payment/available-billers/telco) # Multifinance ## Overview Multifinance billers support installment and financing payments. Availability depends on your merchant profile and configuration. ## Supported billers * Adira Roda Dua * Astra Credit Company (ACC Finance) * BNI Finance * Bussan Auto Finance * CIMB Auto Finance * Clipan Finance * Mega Finance * Mitra Pinastika Mustika Finance * Pegadaian * Smart Finance * Toyota Astra Finance * Woka Finance ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Astra Credit Company (ACC) Finance # Bussan Auto Finance # CIMB Niaga Auto Finance # Clipan Finance # Mega Finance # Page 2 # Insurance ## Overview Insurance billers support BPJS and related insurance payments. Availability depends on your merchant profile and configuration. ## Supported billers * BPJS Kesehatan * BPJS Kesehatan - Denda * BPJS Kesehatan - VA * BPJS Ketenagakerjaan * BPJS Ketenagakerjaan - BPU (Bukan Penerima Upah) * BPJS Ketenagakerjaan - PMI (Perlindungan Migran Indonesia) * BPJS Ketenagakerjaan - PU (Penerima Upah) ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # BPJS Ketenagakerjaan ## Overview BPJS Ketenagakerjaan bill payments. Availability depends on your configuration. ## Variants * BPU (Bukan Penerima Upah) * PMI (Perlindungan Migran Indonesia) * PU (Penerima Upah) ## Related * [Insurance](/bill-payment/available-billers/insurance) # BPJS Kesehatan ## Overview BPJS Kesehatan bill payments. Availability depends on your configuration. ## Variants * BPJS Kesehatan - Denda * BPJS Kesehatan - VA ## Related * [Insurance](/bill-payment/available-billers/insurance) # Travel ## Overview Travel billers support travel-related payments. Availability depends on your merchant profile and configuration. ## Supported billers * (No billers listed yet) ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Property ## Overview Property billers support payments related to property services. Availability depends on your merchant profile and configuration. ## Supported billers * Jaya Real Property ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Internet/TV ## Overview Internet/TV billers support internet and TV subscription payments. Availability depends on your merchant profile and configuration. ## Supported billers * ICONNET * by.U * MNC Play * MNC Vision * IndiHome * Transvision ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Transvision ## Overview Transvision subscription payments. Availability depends on your configuration. ## Related * [Internet/TV](/bill-payment/available-billers/internet-tv) # e-Money Top Up ## Overview e-Money Top Up billers let customers top up their wallet balance. Availability depends on your merchant profile and configuration. ## Supported billers * DANA Top Up * ShopeePay Top Up * OVO Top Up * GoPay Top Up ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # DANA ## Overview DANA wallet top up. Availability depends on your configuration. ## Related * [e-Money Top Up](/bill-payment/available-billers/e-money-top-up) # Gopay ## Overview GoPay wallet top up. Availability depends on your configuration. ## Related * [e-Money Top Up](/bill-payment/available-billers/e-money-top-up) # OVO ## Overview OVO wallet top up. Availability depends on your configuration. ## Related * [e-Money Top Up](/bill-payment/available-billers/e-money-top-up) # ShopeePay ## Overview ShopeePay wallet top up. Availability depends on your configuration. ## Related * [e-Money Top Up](/bill-payment/available-billers/e-money-top-up) # Transportation ## Overview Transportation billers let customers pay for transport-related services. Availability depends on your configuration. ## Supported billers * KAI * Garuda Airlines * Signal Samsat ## Related * See the full list in [Available Billers](/bill-payment/available-billers). # Test Scenarios # Settlement # e-Money Linkage Finpay **e-Money Linkage** connects your system with Finpay Money for specific payment or top-up flows. Use it when you need linkage-style interaction rather than standard checkout. ### What you can do * Enable select e-money linkage use cases based on agreement scope. * Support a consistent experience across channels. {% hint style="warning" %} This product is typically enabled per partnership agreement. Flow availability may differ by merchant category and channel. {% endhint %} ### Next step If you are unsure whether you need Finpay Money linkage or standard acceptance, contact us. # Payment Statuses # Disbursement Report # Transfer Statuses # Bill Payment Report # Overview # 2FA Authentication Protect your dashboard access with two-factor authentication. Finpay supports Google Authenticator-based 2FA for merchant users. After you enable it, users must enter both their password and a time-based verification code when they sign in. {% hint style="info" %} Use 2FA for all users with dashboard access. This is especially important for administrator, finance, and approval roles. {% endhint %} ### Enable 2FA {% stepper %} {% step %} ### Sign in Sign in to the Finpay Dashboard with your user account. {% endstep %} {% step %} ### Open your profile settings Go to **Settings → User Profile**. {% endstep %} {% step %} ### Start 2FA setup Click **Activate Google Two-factor Authentication**. {% endstep %} {% step %} ### Pair your authenticator app Open Google Authenticator on your mobile device. Scan the QR code shown on the screen. {% endstep %} {% step %} ### Verify activation Enter the verification code from Google Authenticator. Click **Send OTP** to confirm activation. {% endstep %} {% endstepper %} After setup is complete, 2FA is active for your account. ### What users need Each user needs: * An active Finpay dashboard account * Access to their registered sign-in credentials * Google Authenticator installed on a mobile device ### Recommended security practices * Require 2FA for all internal dashboard users. * Review 2FA use during onboarding and offboarding. * Restrict administrator access to trusted personnel only. * Combine 2FA with [IP Whitelist](/security/ip-whitelist) for stronger dashboard protection. ### Troubleshooting If a user cannot complete setup: * Confirm the mobile device can open Google Authenticator * Rescan the QR code and use the latest generated code * Make sure the verification code is entered before it expires If the issue continues, ask your internal administrator to review the user account and retry the setup process. # IP Whitelist Restrict API access to trusted network addresses with IP whitelisting. When IP whitelist is enabled, Finpay only accepts API requests from registered IP addresses that use your credentials. This reduces the risk of unauthorized API access. {% hint style="info" %} Use IP whitelist for production credentials. Review the list whenever your infrastructure changes. {% endhint %} ### Before you enable IP whitelist Make sure you have: * A user account with permission to manage API credentials and IP whitelist * The public IP addresses used by your server or gateway * A rollback plan in case your network address changes {% hint style="warning" %} If you whitelist the wrong IP address, your API requests can fail until the list is corrected. {% endhint %} ### Add an IP address to the whitelist {% stepper %} {% step %} ### Sign in Sign in to the Finpay Dashboard. {% endstep %} {% step %} ### Open IP whitelist settings Go to **Settings → IP Whitelist**. {% endstep %} {% step %} ### Add the address Click **+ Add**. Enter the public IP address you want to allow. {% endstep %} {% step %} ### Save the change Click **Submit** to save the new whitelist entry. {% endstep %} {% step %} ### Verify API access Send a test API request from the registered IP address. Confirm the request is accepted. {% endstep %} {% endstepper %} After the IP is registered, only listed IP addresses can send API requests with your Finpay credentials. ### When to update the whitelist Update the whitelist when: * You move your application to a new server or cloud environment * Your internet provider changes your public IP address * You add a new production or failover endpoint Remove IP addresses that are no longer in use. ### Recommended security practices * Whitelist only fixed and trusted public IP addresses. * Keep production and non-production environments separate. * Review the whitelist after infrastructure changes. * Combine IP whitelist with [2FA Authentication](/security/2fa-authentication) for stronger account security. * Control admin access with [User & Roles](/security/user-and-roles). ### Troubleshooting If API requests fail after enabling IP whitelist: * Confirm the request comes from a registered public IP address * Check whether your server IP has changed * Review the whitelist entry for typing errors * Retry the request after saving the latest change If the issue continues, review your current network path and update the whitelist with the correct public IP address. # User & Roles Manage dashboard access with role-based permissions. Assign each user the minimum access they need to do their job. This page explains how to add users, choose the right role, and apply basic access control practices for your team. {% hint style="info" %} Only **Administrator Merchant** can manage team members and access. {% endhint %} ### Before you add a user Use these principles for a safer setup: * Grant the lowest access level that still lets the user do their work. * Separate request and approval duties for disbursements. * Review user access regularly and remove unused accounts. {% hint style="warning" %} For disbursement workflows, assign **Disbursement requestors** and **Disbursement approval** to different users. {% endhint %} ### Add a new user {% stepper %} {% step %} ### Open user management Sign in to the Finpay Dashboard. Go to **User → Merchant User**. {% endstep %} {% step %} ### Create the account Click **+ Add**. Enter the required user details. {% endstep %} {% step %} ### Assign a role Choose the role that matches the user's responsibility: * Administrator Merchant * Operation Merchant * IT Merchant * Disbursement requestors * Disbursement approval * Finance Merchant * Finance Operation {% endstep %} {% step %} ### Save and verify access Save the new user. Ask the user to sign in and confirm the expected menu access. {% endstep %} {% endstepper %} ### Update an existing user's role To change a user's responsibilities: 1. Go to **User → Merchant User**. 2. Select the user account you want to update. 3. Change the assigned role. 4. Save the change. 5. Confirm the updated access is correct. {% hint style="warning" %} Apply role changes immediately when a user changes function, team, or approval scope. {% endhint %} ### Role guide | Role | Best for | Key access | Notes | | --------------------------- | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | | **Administrator Merchant** | Business owners or senior administrators | Manage users and access. View reports, balances, settlements, and top-ups. Manage settings, API credentials, IP whitelist, and disbursement setup. | Broadest dashboard access. | | **Operation Merchant** | Operations or support teams | View transaction, payment, disbursement, and invoice reports. Export report data. Resend payment notifications. | Cannot manage settings or move funds. | | **IT Merchant** | Developers and technical integration teams | Manage API credentials. Manage the IP whitelist. Resend notifications. | No finance or reporting access. | | **Disbursement requestors** | Staff who prepare payout requests | Create and manage disbursement requests. View beneficiaries and balance. View and export disbursement reports and details. | Maker role. Cannot approve its own requests. | | **Disbursement approval** | Supervisors who approve outgoing payments | Review and approve disbursement requests. Manage beneficiaries. View balances, payment reports, and disbursement reports. | Checker role. Does not create disbursement requests. | | **Finance Merchant** | Finance and reconciliation teams | View transaction, payment, invoice, and disbursement reports. View settlement summaries and balance. Create void transaction requests. View disbursement requests and approvals. | Focused on financial monitoring. | | **Finance Operation** | Senior finance users with broader operational needs | Manage invoices and payment links. Request disbursements. View reports, settlements, balances, and top-ups. Manage recipients and beneficiaries. | Grant only when broad cross-functional access is needed. | ### Permission summary
PermissionAdministrator MerchantOperation MerchantIT MerchantDisbursement requestorsDisbursement approvalFinance MerchantFinance Operation
Create and manage invoices or payment links✔✔✖✖✖✔✔
Manage recipients✔✖✖✖✖✖✔
View, export, and schedule transaction reports✔✔✖✔✔✔✔
View payment reports✔✔✖✖✔✔✔
Process refunds and voids✔✖✖✖✖✔✔
Resend payment notifications✔✔✔✖✖✖✔
Request disbursements✖✖✖✔✖✔✔
Approve disbursements✖✖✖✖✔✔✖
Manage beneficiaries✔✖✖✔✔✖✔
View disbursement reports and details✔✔✖✔✔✔✔
View balance, top-up, and settlement✔✖✖✔✔✔✔
Configure payment and business settings✔✖✖✖✖✖✖
Manage team members and access✔✖✖✖✖✖✖
Manage API credentials and IP whitelist✔✖✔✔✖✖✖
Complete KYC and manage profile✔✔✔✔✔✔✔
### Access management best practices * Limit **Administrator Merchant** accounts to trusted personnel. * Use separate maker and checker roles for disbursement control. * Review access after organizational or process changes. * Remove access immediately for inactive or departed users. If you also manage network restrictions, see [IP Whitelist](/security/ip-whitelist). # Overview ![Finpay](https://storage.googleapis.com/finpay-pg-assets/merchant/ic_finpay-new.png) Finpay is the product brand of PT Finnet Indonesia. It started operating in 2006 as a financial technology provider. Finpay helps businesses accept and manage digital payments. Finpay provides a Payment Gateway for secure, efficient transaction processing. It supports credit cards, bank transfers, virtual accounts, e-money, and retail cash payments. Finpay also offers money transfers, disbursements, and bill payments. Bill payment currently supports **524 billers** (service providers issuing bills). ### Get started in 3 steps {% stepper %} {% step %} ### 1) Register Create a Sandbox account to access APIs and Finpay services. [Register your account](https://dashboard.finpay.id/register) {% endstep %} {% step %} ### 2) Integrate Sign in to Sandbox to start integration and run simulations. [Sandbox integration pages](https://dashboard.finpay.id/login) {% endstep %} {% step %} ### 3) Monitor Track transactions in real time from the dashboard. [Transactions monitoring](https://dashboard.finpay.id/login) {% endstep %} {% endstepper %} Need a tailored payment flow or value-added features? Contact [Finpay Care](https://hub.finpay.id/#contact). # Getting Started ### Register Sandbox Finpay Welcome to Finpay! Before integrating with Finpay, you need to Create your Finpay Account by following this simple ways 1. Click Sign Up on [Finpay Sandbox](https://dashboard.finpay.id/register). 2. Enter Business Name, Full Name, Business Email, Business Phone Number, and Password. 3. Click Submit. 4. After completing the registration, you will able to Login into [Finpay Sandbox](https://dashboard.finpay.id/login) ![Finpay Sandbox](https://hub.finpay.id/assets/images/merchant_register-31153fb58a7cb91f00c56e3684a5fbba.webp) ### Sign In Sandbox Finpay To access Sandbox Finpay, follow the steps given below. 1. Go to [Finpay Sandbox](https://dashboard.finpay.id/login). 2. Enter your Email and Password. 3. Click Continue to Sign In. ![Finpay Sandbox](https://hub.finpay.id/assets/images/merchant_login-64caac7919eadc653828644c65ad9e22.webp) ### Getting Credential Access Now you can start integrating to Finpay API by following the steps given below. 1. Sign In to [Finpay Sandbox](https://dashboard.finpay.id/login). 2. Select **Settings** menu on the sidebar 3. Choose **Credential Access** ![Finpay Credential](https://hub.finpay.id/assets/images/merchant_credential-4a0653412405a6c5156909a863255f42.webp) # Payment Gateway Overview Finpay will help your bussiness to accept payment from various methods such as : credit card, bank transfer, emoney, cash payments through retail outlets etc. Differences integration methods :
Integration MethodFeatureSample Use Case
Hosted PaymentSimple and easy intregation, just one process to connect with all payment methods provide by FinpayFor all merchant who need easy and quick integration.
Redirect customer to payment page hosted by FinpaySuitable for merchant who already have website or mobile application so can be embed payment page directly
Customizable payment method in quick way without any enhancement in your system
Customizable merchant or brand name and logo
Core APICustomize your own UI/UXMerchants who want specifix UI/UX to suit their experience flow
Customize parameter for each payment methodsUsed by partners who have a website or mobile application but also can be implemented on a POS or vending machine
Can be enhance with additional features such as: Autodebet service
Finpay InvoiceNo technical integrationQuick and easy to used, no programming skills are needed (No Coding)
Create payment invoice for your customer through Finpay DashboardSuitable for Small and Medium Enterpris online shop owners who don't have a website or mobile application
payment link that is shareable through Email, SMS WhatsApp, etc
[
](https://hub.finpay.id/docs/getting-started) # Authorization & Headers For backend based API request/call, Finpay API requires HTTP(s) headers that will be explained below. ### Content-Type and Accept Header Finpay API uses JSON format for input and output, hence it is required to specify JSON as content-type & accept JSON as response. The header specification is as shown below. * Content-Type: application/json * Accept: application/json ### Authorization Header The Finpay API utilizes the merchant ID and basic authorization header for processing requests. The Merchant ID and Merchant Key are used in conjunction to create the Authorization Header, which is a security measure to prevent unauthorized access to the API. * For **Development** environment, obtain Merchant Id & Merchant Key in [Sandbox Dashboard](https://dashboard.finpay.id/pages/access-keys) * For **Production** environment, obtain Merchant Id & Merchant Key in [Dashboard](https://dashboard.finpay.id/pages/access-keys) To generate Authorization header value, follow the steps given below. 1. Follow the format of Basic Authentication. (example: Username:Password) 2. Username and password are separated by : character. 3. Merchant Id is used as Username and Merchant Key as Password. * For example, if your Merchant Id is FINPAY770 and Merchant Key is SoSecret123 then Username:Password would be `FINPAY770:SoSecret123`. 4. Encode this value into base64 format. * For example, base64 of FINPAY770:SoSecret123 is `RklOUEFZNzcwOlNvU2VjcmV0MTIz`. 5. Add the word Basic as prefix. * The above value would be `Basic RklOUEFZNzcwOlNvU2VjcmV0MTIz`. 6. Your Authorization header is ready. * `Authorization: Basic RklOUEFZNzcwOlNvU2VjcmV0MTIz` # Hosted Payment ### Introduction **Hosted Payment** is one of the recomended products that allows Merchants to easily and quickly integrate with Finpay Payment Gateway to start accepting payments with any of payment method options. Hosted Payment uses a Web Page URL redirect mechanism with single integration process, Hosted Payment allow to choose various payment methods in Finpay Page. This mechanism is suitable for every business scale from small businesses to enterprises. This is an overview of how Hosted Payment works :

Preview Hosted Payment UI

### Transaction Flow The overall end-to-end payment process in Hosted Payment is illustrated in following sequence diagram: ```mermaid sequenceDiagram Actor Customer as End Customer participant Merchant participant Finpay participant Mobile Apps participant Provider as Payment Channel Provider Merchant->>Finpay: Request Hosted Payment API Finpay->>Merchant: Response Hosted Payment API Merchant->>Finpay: Redirect to Hosted Payment Page Finpay Customer->>Finpay: Choose Payment Method Customer->>Finpay : Input Customer ID Customer-->>Customer: Pay on selected provider Provider->>Finpay : Callback Notification Finpay->>Merchant : Callback Notification Merchant->>Customer : Notify transaction status ``` ### API Request | Environment | Method | URL | | ----------- | ------ | ---------------------------------------------------- | | Development | POST | | | Production | POST | | ### Body Request | No | Name | Type | Mandatory | Min Length | Max Length | Description | | -- | ------------- | -------------------------------------------------------------------- | --------- | ---------- | ---------- | ----------------------- | | 1 | order | [Object](/api-reference/appendix/json-object/order-object) | M | 1 | 12 | Detail of Order | | 2 | customer | [Object](/api-reference/appendix/json-object/customer-object) | M | 1 | 8 | Detail of Customer | | 3 | url | [Object](/api-reference/appendix/json-object/url-object) | M | 1 | 4 | Detail of Url | | 4 | billing | [Object](/api-reference/appendix/json-object/billing-object) | O | 1 | 1 | Detail of Billing | | 5 | shipping | [Object](/api-reference/appendix/json-object/shipping-object) | O | 1 | 4 | Detail of Shipping | | 6 | meta | [Object](/api-reference/appendix/json-object/meta-object) | O | 1 | 1 | Detail of MetaData | | 7 | card | [Object](/api-reference/appendix/json-object/card-object) | O | 1 | 7 | Detail of Card | | 8 | recurring | [Object](/api-reference/appendix/json-object/recurring-object) | O | 1 | 11 | Detail of Recurring | | 9 | sourceOfFunds | [Object](/api-reference/appendix/json-object/source-of-funds-object) | O | 1 | 11 | Detail of SourceOfFunds | | 10 | device | [Object](/api-reference/appendix/json-object/device-object) | O | 1 | 7 | Detail of Device | #### Sample Request ``` { "customer": { "email": "hajar.finnet@gmail.com", "firstName": "Hajar", "lastName": "Ismail", "mobilePhone": "+6281286288844" }, "order": { "id": "order123", "amount": "1000", "description": "Testing" }, "url": { "callbackUrl": "https://sandbox.finpay.co.id/simdev/finpay/result/resultsuccess.php" } } ``` ### Body Response | No | Name | Type | Mandatory | Min Length | Max Length | Description | | -- | --------------- | -------------------------------------------------------------- | --------- | ---------- | ---------- | ---------------- | | 1 | responseCode | [Enum](/api-reference/appendix/enumeration/response-code-list) | M | 1 | 7 | Response Code | | 2 | responseMessage | String | M | 1 | 500 | Response Message | | 3 | paymentCode | String | O | 1 | 30 | Payment Code | | 4 | redirecturl | String | M | 1 | 320 | Redirect URL | | 5 | expiryLink | String | M | 1 | 19 | Expiry Link | | 6 | processingTime | Number | M | 1 | 20 | Processing Time | | 7 | appurl | String | O | 1 | 320 | App URL | | 8 | imageurl | String | O | 1 | 320 | Image URL | | 9 | accountList | Array | O | 1 | 4 | Account List | #### Sample Response ``` { "responseCode": "2000000", "responseMessage": "Success", "redirecturl": "https://devo.finpay.id/pg/payment/card/v2/access/ebb8367ac6a3efcb2498766234a528536df37e01db10831523dc03c67234ef82", "expiryLink": "2023-05-18 14:55:24", "processingTime": 0.5706689357757568 } ``` --- [Next Page](/llms-full.txt/1)