diff --git a/images/acceptingPayments/api-account-linking/dashboard-b7c4b022.webp b/images/acceptingPayments/api-account-linking/dashboard-b7c4b022.webp new file mode 100644 index 00000000000..70c86ca016f Binary files /dev/null and b/images/acceptingPayments/api-account-linking/dashboard-b7c4b022.webp differ diff --git a/images/acceptingPayments/api-account-linking/payment-flow-api-account-linking-35af88f7.webp b/images/acceptingPayments/api-account-linking/payment-flow-api-account-linking-35af88f7.webp new file mode 100644 index 00000000000..6d8a84dad92 Binary files /dev/null and b/images/acceptingPayments/api-account-linking/payment-flow-api-account-linking-35af88f7.webp differ diff --git a/images/acceptingPayments/api-account-linking/payment-flow-api-get-e-wallet-balance-f2c38604.webp b/images/acceptingPayments/api-account-linking/payment-flow-api-get-e-wallet-balance-f2c38604.webp new file mode 100644 index 00000000000..dd2b412263f Binary files /dev/null and b/images/acceptingPayments/api-account-linking/payment-flow-api-get-e-wallet-balance-f2c38604.webp differ diff --git a/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-api-accoung-linking-de7f8728.webp b/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-api-accoung-linking-de7f8728.webp new file mode 100644 index 00000000000..5356f36e416 Binary files /dev/null and b/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-api-accoung-linking-de7f8728.webp differ diff --git a/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-e-wallet-app-0626d2b9.webp b/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-e-wallet-app-0626d2b9.webp new file mode 100644 index 00000000000..2be4f4a1201 Binary files /dev/null and b/images/acceptingPayments/api-account-linking/payment-flow-unlink-account-via-e-wallet-app-0626d2b9.webp differ diff --git a/images/acceptingPayments/api-e-wallet-aggragator/dashboard-callback-bcf25c8b.webp b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-callback-bcf25c8b.webp new file mode 100644 index 00000000000..e68df532bc4 Binary files /dev/null and b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-callback-bcf25c8b.webp differ diff --git a/images/acceptingPayments/api-e-wallet-aggragator/dashboard-developer-option-bd6f0c58.webp b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-developer-option-bd6f0c58.webp new file mode 100644 index 00000000000..9e4e987623b Binary files /dev/null and b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-developer-option-bd6f0c58.webp differ diff --git a/images/acceptingPayments/api-e-wallet-aggragator/dashboard-selesai-b9e19cf7.webp b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-selesai-b9e19cf7.webp new file mode 100644 index 00000000000..67ebd7649ad Binary files /dev/null and b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-selesai-b9e19cf7.webp differ diff --git a/images/acceptingPayments/api-e-wallet-aggragator/dashboard-waiting-payment-1e0d2b5e.webp b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-waiting-payment-1e0d2b5e.webp new file mode 100644 index 00000000000..c255b998e78 Binary files /dev/null and b/images/acceptingPayments/api-e-wallet-aggragator/dashboard-waiting-payment-1e0d2b5e.webp differ diff --git a/images/acceptingPayments/api-e-wallet-aggragator/payment-flow-18638d05.webp b/images/acceptingPayments/api-e-wallet-aggragator/payment-flow-18638d05.webp new file mode 100644 index 00000000000..9ffddc04437 Binary files /dev/null and b/images/acceptingPayments/api-e-wallet-aggragator/payment-flow-18638d05.webp differ diff --git a/images/acceptingPayments/api-payment-routing/dashboard-6d75985b.webp b/images/acceptingPayments/api-payment-routing/dashboard-6d75985b.webp new file mode 100644 index 00000000000..8c58c3593f9 Binary files /dev/null and b/images/acceptingPayments/api-payment-routing/dashboard-6d75985b.webp differ diff --git a/images/acceptingPayments/api-payment-routing/payment-flow-with-ui-scheme-be2e6199.webp b/images/acceptingPayments/api-payment-routing/payment-flow-with-ui-scheme-be2e6199.webp new file mode 100644 index 00000000000..ba50a75de9d Binary files /dev/null and b/images/acceptingPayments/api-payment-routing/payment-flow-with-ui-scheme-be2e6199.webp differ diff --git a/images/acceptingPayments/api-payment-routing/payment-flow-without-ui-scheme-33101543.webp b/images/acceptingPayments/api-payment-routing/payment-flow-without-ui-scheme-33101543.webp new file mode 100644 index 00000000000..913a66c169e Binary files /dev/null and b/images/acceptingPayments/api-payment-routing/payment-flow-without-ui-scheme-33101543.webp differ diff --git a/images/acceptingPayments/payment-link/creating-payment-link/creation-0e917947.webp b/images/acceptingPayments/payment-link/creating-payment-link/creation-0e917947.webp new file mode 100644 index 00000000000..af92cdedcd2 Binary files /dev/null and b/images/acceptingPayments/payment-link/creating-payment-link/creation-0e917947.webp differ diff --git a/images/acceptingPayments/payment-link/features/copy-link-67320eff.webp b/images/acceptingPayments/payment-link/features/copy-link-67320eff.webp new file mode 100644 index 00000000000..d249d9f5d3e Binary files /dev/null and b/images/acceptingPayments/payment-link/features/copy-link-67320eff.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-customized-payment-link-24fe2480.webp b/images/acceptingPayments/payment-link/features/dashboard-customized-payment-link-24fe2480.webp new file mode 100644 index 00000000000..beb3a2090d7 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-customized-payment-link-24fe2480.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-developer-option-4f22358b.webp b/images/acceptingPayments/payment-link/features/dashboard-developer-option-4f22358b.webp new file mode 100644 index 00000000000..b27112d28b7 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-developer-option-4f22358b.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-notif-for-receiver-891a0205.webp b/images/acceptingPayments/payment-link/features/dashboard-notif-for-receiver-891a0205.webp new file mode 100644 index 00000000000..1c8bb7335b3 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-notif-for-receiver-891a0205.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-notif-for-sender-7a17222e.webp b/images/acceptingPayments/payment-link/features/dashboard-notif-for-sender-7a17222e.webp new file mode 100644 index 00000000000..3fec69c11e1 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-notif-for-sender-7a17222e.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-resend-callback-e87dc14e.webp b/images/acceptingPayments/payment-link/features/dashboard-resend-callback-e87dc14e.webp new file mode 100644 index 00000000000..439cd09c666 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-resend-callback-e87dc14e.webp differ diff --git a/images/acceptingPayments/payment-link/features/dashboard-view-1f9e3f76.webp b/images/acceptingPayments/payment-link/features/dashboard-view-1f9e3f76.webp new file mode 100644 index 00000000000..306e3266031 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/dashboard-view-1f9e3f76.webp differ diff --git a/images/acceptingPayments/payment-link/features/default-config-f8ce3eef.webp b/images/acceptingPayments/payment-link/features/default-config-f8ce3eef.webp new file mode 100644 index 00000000000..8d79f7cdd95 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/default-config-f8ce3eef.webp differ diff --git a/images/acceptingPayments/payment-link/features/payment-link-after-changes-ff8e0830.webp b/images/acceptingPayments/payment-link/features/payment-link-after-changes-ff8e0830.webp new file mode 100644 index 00000000000..187f9633ac1 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/payment-link-after-changes-ff8e0830.webp differ diff --git a/images/acceptingPayments/payment-link/features/preview-payment-link-267897d7.webp b/images/acceptingPayments/payment-link/features/preview-payment-link-267897d7.webp new file mode 100644 index 00000000000..e8fad80c779 Binary files /dev/null and b/images/acceptingPayments/payment-link/features/preview-payment-link-267897d7.webp differ diff --git a/images/acceptingPayments/payment-link/flow/payment-flow-one-time-7b9a2821.webp b/images/acceptingPayments/payment-link/flow/payment-flow-one-time-7b9a2821.webp new file mode 100644 index 00000000000..5b4ac945d0b Binary files /dev/null and b/images/acceptingPayments/payment-link/flow/payment-flow-one-time-7b9a2821.webp differ diff --git a/images/acceptingPayments/payment-link/flow/payment-flow-reusable-2b6e0bc0.webp b/images/acceptingPayments/payment-link/flow/payment-flow-reusable-2b6e0bc0.webp new file mode 100644 index 00000000000..5c4e0839caa Binary files /dev/null and b/images/acceptingPayments/payment-link/flow/payment-flow-reusable-2b6e0bc0.webp differ diff --git a/images/acceptingPayments/payment-link/flow/preview-payment-link-267897d7.webp b/images/acceptingPayments/payment-link/flow/preview-payment-link-267897d7.webp new file mode 100644 index 00000000000..e8fad80c779 Binary files /dev/null and b/images/acceptingPayments/payment-link/flow/preview-payment-link-267897d7.webp differ diff --git a/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-flow-2bfe35be.webp b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-flow-2bfe35be.webp new file mode 100644 index 00000000000..eecc1cc69bc Binary files /dev/null and b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-flow-2bfe35be.webp differ diff --git a/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-link-view-5bbf25ca.webp b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-link-view-5bbf25ca.webp new file mode 100644 index 00000000000..efc162e26d5 Binary files /dev/null and b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/payment-link-view-5bbf25ca.webp differ diff --git a/images/acceptingPayments/payment-methods/bank-transfer-unique-code/simulating-callback-fc2bd338.webp b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/simulating-callback-fc2bd338.webp new file mode 100644 index 00000000000..fc885e2b9de Binary files /dev/null and b/images/acceptingPayments/payment-methods/bank-transfer-unique-code/simulating-callback-fc2bd338.webp differ diff --git a/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/payment-flow-04ea48ce.webp b/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/payment-flow-04ea48ce.webp new file mode 100644 index 00000000000..aeb8b613a63 Binary files /dev/null and b/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/payment-flow-04ea48ce.webp differ diff --git a/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/simulating-callback-9c527136.webp b/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/simulating-callback-9c527136.webp new file mode 100644 index 00000000000..da4cee8c1f3 Binary files /dev/null and b/images/acceptingPayments/payment-methods/bank-transfer-virtual-account/simulating-callback-9c527136.webp differ diff --git a/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-link-fcb00887.webp b/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-link-fcb00887.webp new file mode 100644 index 00000000000..8a09e5269f5 Binary files /dev/null and b/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-link-fcb00887.webp differ diff --git a/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-routing-4ecb5b12.webp b/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-routing-4ecb5b12.webp new file mode 100644 index 00000000000..c2b1d05b5a7 Binary files /dev/null and b/images/acceptingPayments/payment-methods/cards/payment-flow-via-payment-routing-4ecb5b12.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/payment-flow-direct-payment-7c69dcb2.webp b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-direct-payment-7c69dcb2.webp new file mode 100644 index 00000000000..ac764238b6b Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-direct-payment-7c69dcb2.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-push-notification-19416371.webp b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-push-notification-19416371.webp new file mode 100644 index 00000000000..80fbf276a32 Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-push-notification-19416371.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-redirection-7e2809ed.webp b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-redirection-7e2809ed.webp new file mode 100644 index 00000000000..091b1a8794f Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/payment-flow-single-payment-redirection-7e2809ed.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/payment-link-view-49f188c7.webp b/images/acceptingPayments/payment-methods/e-wallet/payment-link-view-49f188c7.webp new file mode 100644 index 00000000000..77f2d0a43d3 Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/payment-link-view-49f188c7.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/preview-dashboard-8443778f.webp b/images/acceptingPayments/payment-methods/e-wallet/preview-dashboard-8443778f.webp new file mode 100644 index 00000000000..fa9ae8d9386 Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/preview-dashboard-8443778f.webp differ diff --git a/images/acceptingPayments/payment-methods/e-wallet/simulating-callback-067bf3c1.webp b/images/acceptingPayments/payment-methods/e-wallet/simulating-callback-067bf3c1.webp new file mode 100644 index 00000000000..055ca8c9979 Binary files /dev/null and b/images/acceptingPayments/payment-methods/e-wallet/simulating-callback-067bf3c1.webp differ diff --git a/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-flow-ce2938df.webp b/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-flow-ce2938df.webp new file mode 100644 index 00000000000..84965d09a2c Binary files /dev/null and b/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-flow-ce2938df.webp differ diff --git a/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-link-view-5fb142f5.webp b/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-link-view-5fb142f5.webp new file mode 100644 index 00000000000..d105bd55f97 Binary files /dev/null and b/images/acceptingPayments/payment-methods/qr-code-(qris)/payment-link-view-5fb142f5.webp differ diff --git a/images/acceptingPayments/va-aggregator/payment-flow-807bf7e9.webp b/images/acceptingPayments/va-aggregator/payment-flow-807bf7e9.webp new file mode 100644 index 00000000000..f7d9176b46b Binary files /dev/null and b/images/acceptingPayments/va-aggregator/payment-flow-807bf7e9.webp differ diff --git a/images/acceptingPayments/va-aggregator/use-cases-913bd8d5.webp b/images/acceptingPayments/va-aggregator/use-cases-913bd8d5.webp new file mode 100644 index 00000000000..ae8e1e38b12 Binary files /dev/null and b/images/acceptingPayments/va-aggregator/use-cases-913bd8d5.webp differ diff --git a/images/acceptingPayments/va-aggregator/viewing-list-of-created-va-0c29596b.webp b/images/acceptingPayments/va-aggregator/viewing-list-of-created-va-0c29596b.webp new file mode 100644 index 00000000000..771985a92c9 Binary files /dev/null and b/images/acceptingPayments/va-aggregator/viewing-list-of-created-va-0c29596b.webp differ diff --git a/images/acceptingPayments/va-aggregator/viewing-list-of-incoming-payment-2b590d39.webp b/images/acceptingPayments/va-aggregator/viewing-list-of-incoming-payment-2b590d39.webp new file mode 100644 index 00000000000..a38f35b601c Binary files /dev/null and b/images/acceptingPayments/va-aggregator/viewing-list-of-incoming-payment-2b590d39.webp differ diff --git a/index.html b/index.html index 73341547561..c9ca841285e 100644 --- a/index.html +++ b/index.html @@ -5349,7 +5349,7 @@

Produc

Payment Flow

-

Bank Transfer Virtual Account Flow

+

Bank Transfer Virtual Account Flow

Activation

  1. Banks non BCA @@ -5462,7 +5462,7 @@

    Simulat
  2. You may use this feature for all your VA transactions across all of OY! Receive Money products (VA Aggregator, Payment Link, and Payment Routing)

-

Bank Transfer - Virtual Account Simulate Payment

+

Bank Transfer - Virtual Account Simulate Payment

Bank Transfer - Unique Code

Intro

Unique Code is a type of bank transfer payment that adds/subtracts a unique amount (between Rp 1-999) to your billed amount. The unique amount acts as an identifier to complete transactions. Unlike virtual accounts where each customer gets a different account number, unique code always uses the same account number for all transactions. The destination account is under OY! Indonesia’s name (PT. Dompet Harapan Bangsa) and you can not modify the destination account with your account. Unique code also has operational hours where you can only create unique code transactions between 3 AM - 8.30 PM GMT+7.

@@ -5552,7 +5552,7 @@

Tran

Payment Flow

-

Bank Transfer - Unique Code Flow

+

Bank Transfer - Unique Code Flow

Activation

You can only use one type of bank transfer (virtual account / unique code) per bank. By default, all banks use virtual accounts. In order to accept payments using unique code, you need to submit a request to OY! via your business representative or our business support.

Payment

@@ -5575,9 +5575,9 @@

Simulate Paym
  • Once you input all the fields, you can simulate the payment by clicking “Send Callback”. If the payment is successful, a success notification will be shown inside the dashboard. OY! will also send the callback to your specified callback URL. If for some reason you did not receive any callback, please contact the customer service to help you solve the problem.
    • -

    Bank Transfer - Unique Code Simulate Payment

    +

    Bank Transfer - Unique Code Simulate Payment

    -

    Bank Transfer - Unique Code Amount Detail

    +

    Bank Transfer - Unique Code Amount Detail

    QR Code (QRIS)

    Intro

    Quick Response Code Indonesian Standard (QRIS) is a standardized QR payments in Indonesia that are developed by Bank Indonesia. Payments are performed by the customers scanning the QR on their m-banking/e-wallet application. QR payments are highly suitable for low-value transactions since they offer an affordable price (0.7% per transaction).

    Feature Availability

    @@ -5613,7 +5613,7 @@

    Product AvailabilityTransaction Amount Details

    The maximum amount per transaction for QRIS is Rp 10,000,000. The minimum amount per transaction is Rp 10,000, both in Payment Link and Payment Routing. Should you have any request to receive payments below Rp 10,000, please contact your Business Representative

    Payment Flow

    -

    QRIS Flow

    +

    QRIS Flow

    Activation

    In order to accept payments using QRIS, you need to register your merchant to the QRIS providers first. You can do the registration via OY! Dashboard by opening the Payment Method page and clicking the Payment Method tab. OY! offers real time registration, so you can directly accept payments once you finish submitting your application.

    @@ -5910,15 +5910,15 @@

    Payment Type & FlowThere are two types of payment flow for Single Payment: Redirection (JumpApp) or Push Notification.

    -

    E-wallet Redirection Flow

    +

    E-wallet Redirection Flow

    -

    E-wallet Push Notification Flow

    +

    E-wallet Push Notification Flow

    Direct Payment

    Direct payment requires account linking, meaning that your customer must connect their e-wallet account to your system before completing payments. Direct payments offer a more seamless payment experience, as your customer does not need to open or get redirected to the e-wallet provider application to complete payments.

    Direct Payments offers both payment with and without authorization (auto-debit). Direct Payment with authorization requires the customer to input a PIN or OTP on every transaction, while Direct Payment without authorization allows your system to deduct your customers balance without the need to enter a PIN or OTP. Direct payment without authorization is suitable for subscription use cases.

    -

    E-wallet Direct Payment Flow

    +

    E-wallet Direct Payment Flow

    Activation

    In order to accept payments using e-wallets, you need to register your merchant to the e-wallet providers first. You can do the registration via OY! Dashboard by opening the Payment Method page, Payment Method - OY! Dashboard. OY! offers real time registration, so you can directly accept payments once you finish submitting your application.

    @@ -6230,12 +6230,12 @@

    Simulate Payments

  • Once you input all the fields, you can simulate the payment by clicking “Send Callback”. If the payment is successful, a success notification will be shown inside the dashboard. OY! will also send the callback to your specified callback URL. If for some reason you did not receive any callback, please contact our customer service to help you solve the problem.
    • -

    E-wallet Simulate Callback -E-wallet See Reference Number

    +

    E-wallet Simulate Callback +E-wallet See Reference Number

    Specifically for Payment Link transactions, you can directly simulate the payment on the Payment Link by clicking “Bayar Tagihan''.

    -

    E-wallet Simulate Callback Payment Link

    +

    E-wallet Simulate Callback Payment Link

    Cards

    Introduction

    OY! offers both debit and credit cards as a payment method for your customers. We currently accept VISA, Mastercard, and JCB.

    Feature Details

    @@ -6264,11 +6264,11 @@

    Transactions Declin

    Payment Flow

    Flow via Payment Link

    -

    Cards Flow via Payment Link

    +

    Cards Flow via Payment Link

    Flow via Payment Routing

    -

    Cards Flow via Payment Routing

    +

    Cards Flow via Payment Routing

    Activation

    If you need to accept payments from your end-users via debit and/or credit cards, you may contact your Business Representative for more information and assistance on the activation process.

    @@ -6350,10 +6350,10 @@ -

    Payment Link Preview

    +

    Payment Link Preview

    -

    Payment Link One Time Flow -Payment Link Reusable Flow

    +

    Payment Link One Time Flow +Payment Link Reusable Flow

    Set your Payment Link configurations depending on the use case of your transactions. There are several things that you can configure:

    @@ -6386,11 +6386,11 @@

    Monitoring transactions via OY! Dashboard

    All created Payment Link transactions are shown in the OY! Dashboard. Navigate to “Payment Link” → “One Time”/”Reusable” to see the list of created transactions. Inside the dashboard, you can see the details of the transactions, including all the transaction information inputted during creation, the status of transactions, and the payment reference number*. The dashboard also has a feature to search, filter, and export the list of transactions in various formats: Excel (.xlsx), PDF (.pdf), and CSV(.csv)

    -

    Payment Link Monitoring Transactions

    +

    Payment Link Monitoring Transactions

    *Payment Reference Number is an identifier of a payment attempt when the customer successfully completes a QRIS payment. The reference number is also stated in the customer’s receipt/proof of transaction. Only available for QRIS transactions.

    Customize theme

    @@ -6425,11 +6425,11 @@

    Customize theme

  • Save the changes. The changes will be applied to all payment links created in real-time. You can see when the last Payment Link Display was modified.
    • -

    Payment Link Customizing Theme

    +

    Payment Link Customizing Theme

    Here is the example of the Payment Link before and after it is customized. The header’s color is customized using brown color and the button’s color uses green color.

    -

    Payment Link Customized

    +

    Payment Link Customized

    You can share created Payment Link directly to your customers through multiple channels, including email, WhatsApp message, and copy link

    @@ -6465,7 +6465,7 @@

    Receipt for successful payments

    Customers can directly see the receipt of payments inside the Payment Link once payment is made. Customers can also receive the receipt via email(s) that you provided during Payment Link creation. Configure sending receipt via emails to your customers by going through this steps:

    @@ -6490,7 +6490,7 @@

    Receipt for succ
  • Your customer will receive successful receipt to the emails once payment is made
    • -

    Payment Link Notifications to Payer

    +

    Payment Link Notifications to Payer

    Note: If you do not put any of your customer’s email during Payment Link creation, OY! will not send any receipt via email even though you enabled the notification configuration

    @@ -6506,7 +6506,7 @@

    Receipt for succ
  • You will receive an email for every successful Payment Link payments made by your customers
    • -

    Payment Link Notifications to Merchant

    +

    Payment Link Notifications to Merchant

    Create a seamless payment experience for your customers by inserting a created Payment Link to your website or application. Customers can stay on your page without being redirected to another page to complete the payments. There are many ways that you can show a Payment Link inside your page, and here are several suggestions that you can use: Pop Up - Center, Pop Up - Right, Pop Up - Left, and Slide - Right. Please refer to Embed Payment Link in the API Docs to see detailed implementation of inserting Payment Link to your application.

    Refund payments to customer

    @@ -6588,7 +6588,7 @@
    Automatic Retry Callback

    Automatic Retry Callback allows you to receive another callback within a certain interval if the previous callback that OY! sent is not received successfully on your system. OY! will try to resend other callbacks up to 5 times. If your system still does not receive any callbacks after 5 retry attempts from OY, OY! will notify you via email. You can input up to 6 email recipients and it is configurable via OY! Dashboard.

    @@ -6614,7 +6614,7 @@
    Multi Entity Management

    Multi Entity Management is a feature that can help you handle multiple OY! accounts under one entity. The account that acts as an admin is called a Main Entity and the accounts that can be controlled by the admin are called Sub Entity.

    @@ -6662,7 +6662,7 @@

    Use Cases

    -

    VA Aggregator Use Case

    +

    VA Aggregator Use Case

    Registration and Set Up

    Here are the procedures to activate VA Aggregator feature:

    @@ -6998,14 +6998,14 @@

    How to Use

    1. You can monitor your created VA numbers through the “Receive Money” tab → Virtual Account → Created VA
    2. You can also see their payment status, amount, VA type, and count of completed transactions. You may also click to export these details to your device as PDF, Excel or CSV -VA Aggregator Monitor Created Transactions
      3. +VA Aggregator Monitor Created Transactions
  • Viewing list of VA Payment
    1. For all successful VA transactions, you can monitor them through the “Receive Money” tab → Virtual Account → Incoming Payment
    2. You can also see the transaction timestamp, status, amount, admin fee and other information. You may also click to export these details to your device as PDF, Excel or CSV -VA Aggregator Monitor Incoming Transactions
      3. +VA Aggregator Monitor Incoming Transactions

    • VA Bank Details

    @@ -7171,7 +7171,7 @@

    Available

    API E-Wallet Aggregator

    E-Wallet API allows clients to charge and receive payments directly from Indonesia's top e-wallet providers. With one integration, they are able to get access to all of OY’s available e-wallets.

    Flow

    -

    E-wallet Aggregator Flow

    +

    E-wallet Aggregator Flow

    Features

    Support multiple E-wallets

    Our E-wallet Aggregator product support e-wallet transactions from these issuers:

    @@ -7184,7 +7184,7 @@

    Features

    Monitor transactions via OY! Dashboard

    All created e-wallet transactions are shown in OY! Dashboard. Navigate to “E-Wallet” to see the list of transactions. Inside the dashboard, you can see the details of the transactions, including all the transaction information inputted during creation, status of transactions, and the payment reference number. The dashboard also has a feature to search, filter, and export the list of transactions in various formats: Excel (.xlsx), PDF (.pdf), and CSV (.csv)

    -

    Monitor E-wallet Aggregator Transaction

    +

    Monitor E-wallet Aggregator Transaction

    Receipt for successful payments

    Customers can receive receipt of successful payments via email(s) that you provided during the creation process. Configure sending receipt via emails to your customers by going through these steps:

    @@ -7209,7 +7209,7 @@

    Receipt for su
  • Your customer will receive successful receipt to the emails once payment is made
    • -

    Receipt for successful Payment

    +

    Receipt for successful Payment

    Note: If you do not put any of your customer’s email during transaction creation, OY! will not send any receipt via email even though you enabled the notification configuration

    Retry notification/callback for successful payments

    @@ -7233,7 +7233,7 @@
    Automatic Retry Callback

    Automatic Retry Callback allows you to receive another callback within a certain interval if the previous callback that OY! sent is not received successfully on your system. OY! will try to resend other callbacks up to 5 times. If your system still does not receive any callbacks after 5 retry attempts from OY, OY! will notify you via email. You can input up to 6 email recipients and it is configurable via OY! Dashboard.

    @@ -7259,7 +7259,7 @@
    Refund transactions to customer

    When your customer receives a defective product or the product is not delivered, they might request to refund the transaction. You can directly refund transactions to your customer’s account via OY! Dashboard. A refund can either be full or partial. A full refund gives your customers the entire amount back (100%). A partial refund returns the amount partially.

    @@ -7436,9 +7436,9 @@

    Use Cases

    Flow

    -

    Payment Routing Aggregator Scheme

    +

    Payment Routing Aggregator Scheme

    -

    Payment Routing Payment Link Scheme

    +

    Payment Routing Payment Link Scheme

    Features

    Support multiple payment methods

    OY! supports various payment methods in the Payment Routing API, including:

    @@ -7481,7 +7481,7 @@

    Crea

    Transaction tracking and monitoring capability

    All created Payment Routing transactions are shown in the OY! Dashboard. Navigate to “Payment Routing” to see the list of created transactions. Inside the dashboard, you can see the details of the transactions, including all the transaction information inputted during creation, the transaction status , and the payment reference number*. The dashboard also has a feature to search, filter, and export the list of transactions in various formats: Excel (.xlsx), PDF (.pdf), and CSV (.csv)

    -

    Payment Routing Monitoring Transactions

    +

    Payment Routing Monitoring Transactions

    *Payment Reference Number is an identifier of a payment attempt when the customer successfully completes a QRIS payment. The reference number is also displayed in the customer’s receipt/proof of transaction. Only available for QRIS transactions.

    Use the same Virtual Account number for different transactions

    @@ -7604,10 +7604,10 @@

    API Account Linkin

    Account linking feature is free of charge.

    Flow

    -

    Account Linking Flow -Get Account Balance Flow -Account Unlinking API Flow -Account Unlinking via App Flow

    +

    Account Linking Flow +Get Account Balance Flow +Account Unlinking API Flow +Account Unlinking via App Flow

    Registration and Setup

    Here are the steps to guide you through registration and set up for doing Account Linking.