OVO Partner Integration Documentation

OVO Top up / Disbursement SNAP Integration

Integration Scope

OVO Disbursement / Top up can be implemented on:

  • Online platform:
    • Merchant Website
    • Merchant App
  • Offline platform:
    • POS Machine
    • Vending Machine
    • And other physical payment platforms

Integration

Feature

Product Description

Top Up Inventory (TUI) is a capability for partners to be able to top up OVO cash from merchant own channels.

Features Status Remarks
Generate AccessToken (B2B) for execute OVO Cash disbursement / top up ✓
OVO Cash Disbursement / Top up ✓
Deposit Control ✓ The API can read merchant’s remaining deposit, so it will reject a top up request when merchant deposit is below the top up amount.
Inquiry Customer Exist ✓
Check transaction status ✓

Suggested Technical Flow

Happy path flow UI for Top Up

Partner E-Wallet Menu
Option to top up OVO Cash and input phone number format must 08xxx


Partner OVO Top Up Menu
Choose amount Top Up, fee will be deducted


Checkout Page
Reconfirm for Top Up amount and to destination OVO account


Success Top Up
Success top up page with details Top up


Receipt
Merchant can create a receipt for users


Happy path flow UI for Disbursement (1)

Partner Disbursement Page
Disburse page details and input OVO phone number format must 08xxx and amount of disbursement


Inquiry Phone number page
Result of inquiry OVO Phone number partner will getting OVO Account name


Happy path flow UI for Disbursement (2)

Partner Disbursement Page
Disburse page details and input OVO phone number format must 08xxx and amount of disbursement


Inquiry Phone number page
Result of inquiry OVO Phone number partner will getting OVO Account name


Unhappy path flow UI for Disbursement

Inquiry Phone number page
Disburse above limit 10 mio and execute to disburse


Failed to Disburse
Partner show the specific error message


Transaction Report

Sample of Transaction Report

  • For reconciliation using var “partnerReferenceNo”, in settlement report file var “partnerReferenceNo” auto generate to the MerchantInvoice column.
  • The transaction will send daily D+1 (in workdays), the transactions will correspond to a reduction in the deposit

Issue Handling

Issue Handling Flow

Contact of OVO Merchant Support

Integration Procedure

Process of Integration

Merchant Start Development/Integration Merchant Go Live
  1. Signing of NDA.
  2. OVO team will share the technical documents for the integration.
  3. Merchant share public key, staging/sandbox.
  4. OVO team will share the staging credentials (sandbox) for development and integration purposes.
  5. After development in merchant side done, OVO team will conduct testing / UAT process and will do review for UAT result.
  1. Signing Commercial Agreement.
  2. Merchant fill Merchant registration form.
  3. Merchant share public key, and IP to be whitelisted in production.
  4. OVO team will share the production credentials to merchant.
  5. Merchant can deploy the production credentials from OVO and Go Live.

Integration Process SLA

Integration Phase SLA PIC Remarks
Create Staging Credentials Up to 2 working days OVO
API Development TBD Merchant
Devsite BI Test TBD Merchant
Functional Test TBD Merchant
UAT with OVO 1 working day / platform OVO
Review UAT Result Up to 2 working days OVO
Create Production Credentials Up to 6 working days OVO Can parallel create if administration & technical requirements done
Go Live Preparation 1 working day OVO Can parallel before go live, meeting with Operational team OVO & merchant
Deployment Production TBD Merchant
Go Live TBD Merchant