OVO Payment Acceptance
SNAP Dynamic QRIS Integration

Integration Scope

OVO SNAP Dynamic QRIS can be implemented on

• Online platform:
  • Merchant Website (Desktop)
• Offline platform:
  • POS Machine
  • Vending Machine
  • And other physical payment platforms

Payment Integration

Features

Features	Status	Remarks
QR Scan/Payment	✓	QR expiry time in 75s
Pay with OVO Cash	✓
Pay with OVO Points	✓
Pay with Off Us (Issuer non OVO)	✓
Point Earning (Cashback)	✓
QR Refund	✓
Refund OVO Cash - (Full Amount)	✓	Same day
Refund OVO Point - (Full Amount)	✓	Same day
Refund Off Us (Issuer non OVO) - (Full Amount)	✓	Same day

Customer Journey UI

Merchant show payload dynamic QRIS (OVO as acquirer) with predefined amount to user via Web/VM/POS Machine

Users can scan with others PJSP, If users using OVO choose Scan in OVO app

Users check the merchant name, amount, and choose SOF and click “Bayar”

Submit OVO Security code / PIN

Payment success in OVO app

Payment success in Merchant platform

Customer Journey Flow

OVO Settlement Flow

Settlement Process

Settlement Report

• For reconciliation using var "refNo" auto generated by OVO after the QR success generated, in settlement report file var “refNo” auto generate to MerchantInvoice column.
• Transaction type, QRIS ISS PURCHASE ON US = On us transaction and QRIS ISS PURCHASE = Off us transaction

Issue Handling

Issue Handling Flow

Contact of OVO Merchant Support

Integration Procedure

Process of Integration

Merchant Start Development/Integration

Merchant Go Live

Signing of NDA. OVO team will share the technical documents for the integration. Merchant share public key (X509 & PKCS1), callback URL staging/sandbox. OVO team will share the staging credentials (sandbox) for development and integration purposes. After development in merchant side done, merchant do the BI Submission testing (Devsite and Functionality Testing) then merchant and OVO team will conduct testing / UAT process and will do review for UAT result.

Signing Commercial Agreement. Merchant fill Merchant registration form. Merchant share public key, callback URL, and IP to be whitelisted in production. OVO team will share the production credentials to merchant. Merchant can deploy the production credentials from OVO and Go Live with Dynamic QRIS OVO as acquirer.

SLA

Integration Phase	SLA	PIC	Remarks
Created Staging Credentials	Up to 3 working days	OVO
API Development	TBD	Merchant
Devsite BI Test
Functionality Test
Get ASPI Verification
UAT	1 working days/platforms	OVO
Review UAT Result	Up to 4 working days	OVO
Created Production Credentials	Up to 6 working days	OVO	Can Parallel create if administration & technical requirements done, this process is including PTEN register
Go Live Preparation	1 working days	OVO	Can parallel before go live, meeting with Operational team OVO & merchant
Deployment Production	TBD	Merchant
Go Live	TBD	Merchant