home

Zuora Payments

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora Payments

Implement OVO on Adyen Integration v2.0

Adyen gateway instance configuration for OVO payments

This document provides instructions for configuring an Adyen gateway instance specifically for OVO payments, highlighting the requirements and settings that can be skipped.

To configure an Adyen gateway instance for processing OVO transactions, follow the instructions in Set up and configure an Adyen Integration v2.0 gateway instance .

In particular, you can skip the following requirements and settings as they do not apply to OVO transactions.

Prerequisites

The last two prerequisites are not applicable to OVO:

  • The setting for recurring fields in the API response must be enabled…(See this article for a full description)

  • To ensure the network transaction ID (NTI) is returned...(See this article for a full description)

Credentials

  • Merchant Account for Payouts User Account

  • API Key for Payouts User Account

  • Merchant Account for Review & Confirm Payouts User Account

  • API Key for Review & Confirm Payouts User Account

Rules

  • Enable gateway reconciliation

  • Reconciliation Username

  • Reconciliation Password

  • Enable Level 2 Processing

  • Enable Level 3 Processing

  • ShipFrom Postal Code API Name

  • ProductCode Custom Field API Name

  • CommodityCode Custom Field API Name

  • Skip Risk Rules

  • Soft Descriptor

  • Shopper Interaction

  • Recurring Processing Model

  • Auto-capture IP Address

  • Submit Card Payments with RecurringDetailReference

  • Tokenize payment method

Additional Metadata

Additional Metadata is not supported by OVO.

Last updated: February 12, 2026