OVO Partner Integration Documentation

Payment Acceptance Online PTP H2H

OVO Integration Scope

PAYMENT
ONLINE MERCHANT
WEBSITE
APPS
POS

Payment Integration

The Customer Journey of Online Push To Pay



Customer login to merchant’s apps/ website and proceed to checkout


Customer select OVO as the payment method in merchant's app/ website


User submit their phone numbers that has registered in OVO account


Customer will receive Push to Pay Notification in their device


Customer check the payment summary, the amount, and source of fund


Customer input their security number


Transaction status in OVO App


Merchant’s app/ website shows complete/failed transaction by RC Code

When user submit their phone numbers in merchant’s app

Merchant should be able to inform the user that the number should be registered in OVO

Guidance
  1. Merchant should be able to put a clear instruction on how to submit customer’s phone number correctly
    1. Please only allow Indonesian phone number and use 08xx phone number format.
    2. Avoid pre-filled phone numbers on any platform.
    3. Educate the users to input the correct phone number format to complete the payment from their OVO application. Please use the instruction below:

      Instruction for user:
      Enter your registered phone number in the OVO application with the 08xxx format.

  2. Please put clear a instruction guide on how user can finish their transaction with OVO

    1. First sentence:
      1. Open your OVO application and click the bell icon complete the payment.
      2. Make sure you complete the payment with a specified time limit to avoid transaction timeout.

      Second sentence:
      Open your OVO application and click the bell icon to complete the payment. Make sure you complete the payment with a specified time limit to avoid transaction timeout.

When merchant has received the response from OVO

Merchant should be able to inform the completion status to user

Guidance

Please put clear error message for every response that will be given by OVO

Response Code (RC) / HTTP Status
 Description / Message
RC 00 Payment successful.
RC 14 The phone number isn’t registered to any OVO account. Please try again.
RC 17 Transaction canceled by User.
RC 26 Failed Push notif to users, please make sure users login to OVO app first.
Timeout / Merchant not get Response Transaction failed due to timeout. Please try again.

Mock Up

Sample of the expected implementation on online integration

RC 00 Payment Successful

RC 17 Canceled Payment

RC 14 Invalid phone number


Timeout/Merchant not get Response

API Integration

API Integration for Push To Pay

Merchant will need to add the requirement API for online Push To Pay

API Push To Pay (mandatory)
API that will be using for sending the payment with OVO as the payment method
API Reversal Payment (mandatory)
API that will be using for reversed the payment. Usually it happens when the merchant does not get any response back from OVO within 60 second
API Check Payment Status (optional)
The API that will be using to check Push To Pay request for payment status
API Void Payment (optional)
API that will be using for void the previous successful transaction within 1 day (before end of day transaction recap)
API Inquiry Phone Number (optional)
The API that will be using to check Phone number availability, before go to the Push to Pay API

API Integration for Push To Pay

Online Payment Technical Flow

API Push To Pay & API Reversal Payment

API Void Payment


Notes : Void feature only allowed to call before end of day or 23:59:59

API Check Payment Status


Notes : Please set the interval for check payment status request on 15s if you are not received the response

Check Payment Status


OVO Settlement Flow

Settlement on SLA

Settlement Report Email

Settlement Report

If you need a sample settlement report template, please contact the OVO Business team.


Issue Handling

Issue Handling Flow

Issue Handling Contact

CS OVO (For Customer)
1500 696
cs@ovo.id
Merchant Support OVO (For Merchant)
1500 167
merchant.support@ovo.id

Integration Procedure

Requirement & Procedure

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 for staging/sandbox credentials.
  4. OVO team will share the staging credentials for development and integration purposes.
  5. After development in merchant side done, OVO team will conduct testing / SIT & UAT process and will do review for SIT & UAT result.
  1. Signing Commercial Agreement.
  2. Merchant fill Merchant registration form.
  3. Merchant share public key in production.
  4. OVO team will share the production credentials to merchant.
  5. Conduct Go Live preparation meeting with OVO Business team, OVO CS, etc.
  6. Merchant can deploy the production credentials from OVO and Go Live with Push to pay.

SLA

Push to Pay Integration Phase SLA PIC
API Development TBD Merchant
UAT 1 Working Day OVO & Merchant
Review UAT Result Up to 2 Working Days OVO
Create Production Credentials (app-id & app-key) Up to 3 working days OVO
Go Live Preparation (Go To Market Meeting) 1 Working Day OVO & Merchant
Deployment Production TBD* Merchant
Go Live TBD* Merchant

*To be defined