Skip to main content
HighRiskPaymentProvider.comPayment provider reviews
Codapay

Company overview

About Coda

What the company provides

  • Acquirer
  • Processor
  • Merchant of Record
  • Payment processing and orchestration provider

Merchant accounts, gateway access, transaction processing and funds handling depend on the selected product.

Coda provides digital-commerce payment products whose legal and funds roles depend on the contract.

Codapay connects a publisher to local and global payment channels through one API and supports arrangements in which either the publisher or an applicable Coda entity is Merchant of Record. Codashop and Coda-operated web stores can use a Coda reseller sale in which the named Coda entity sells the digital product to the buyer. Coda Payments Pte. Ltd. separately holds a Singapore Major Payment Institution licence that includes merchant acquisition, but that permission does not make it the acquirer for every Coda product, market or transaction.

Founded 2011coda.coUpdated Aug 15, 2026

Selected product

Codapay

Codapay payment processing, orchestration and collection

Merchant account & merchant review

  1. Publisher sale & payment-channel setup

    The Coda operating entity assigned to the publisher and market processes and collects buyer payments; The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record when the agreement assigns that role

  2. Publisher, content & payment-route acceptance

    The Coda operating entity assigned to the publisher and market publisher and route review plus the selected payment channel, bank, card aggregator, wallet or mobile operator authorization

    The approved publisher owns the digital product, fulfilment and product support. The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record for the products, markets and transactions identified in the publisher agreement.

Primary legal entity

Coda Payments Pte. Ltd.

Jurisdiction
Singapore
Registration number
201136158E
Company type
Private limited company

Legal entities by jurisdiction

3 legal entities across 2 jurisdictions

  • Singapore2 entities
  • Philippines1 entity

Operating scale

Payment methods
≥400 payment methods
Operating markets
≥70 markets
Publisher partners
≥300 publisher partners

The legal entity supplying a product can differ by product and country.

Product portfolio

Coda products

Compare publisher payment processing and orchestration and Merchant of Record services by account setup, approval, payment or data flow, and contract terms.

Codapay

Role in this product

  • Payment processing and orchestration provider
  • Payment processing orchestration and collection

A single publisher API for approved local and global payment methods.

Coda processes, orchestrates and collects payments under the contracted route, while the publisher agreement determines whether the publisher or an applicable Coda entity is Merchant of Record. Merchant acquisition can be supplied by Coda Payments Pte. Ltd. where its Singapore licence and agreement apply, or by a connected provider on another route.

Related services
Alternative payment methodsChargeback managementDirect API
Features
ChargebacksCheckoutFraud and riskGatewayOnboardingPayment operationsPricingReportingSupport

Codashop and Coda-operated web stores

Role in this product

  • Merchant of Record
  • Authorized digital product reseller
  • Buyer payment processing tax compliance and transaction support
  • Merchant settlement

A consumer marketplace and publisher web-store route for approved digital products.

In the Coda reseller configuration, the applicable Coda entity is the buyer-facing seller and Merchant of Record, processes the order and handles the transaction-tax and payment-risk layer; the publisher remains responsible for the game or app and fulfils or redeems the purchased content.

Related services
Alternative payment methodsChargeback managementFraud preventionHosted checkoutMerchant of Record
Features
CheckoutFraud and riskSeller onboardingPayment operationsPricingSupport

Selected product

Codapay

Related services
Alternative payment methodsChargeback managementDirect API
Features
ChargebacksCheckoutFraud and riskGatewayOnboardingPayment operationsPricingReportingSupport

Publisher sale, payment-channel authorization & settlement

Who is the buyer-facing seller for the selected transaction, who processes and collects the payment, which payment channel controls the instrument and how the publisher receives funds.

01 · Role in this product
Payment processing and orchestration provider · Payment processing orchestration and collection
02 · Publisher sale & payment-channel setup
The Coda operating entity assigned to the publisher and market processes and collects buyer payments; The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record when the agreement assigns that role
03 · Publisher, content & payment-route acceptance
The Coda operating entity assigned to the publisher and market reviews the publisher, content, integration and route; the selected payment channel, bank, card aggregator, wallet or mobile operator authorizes its payment instrument
04 · Buyer payment collection & publisher remittance
The selected payment channel, bank, card aggregator, wallet or mobile operator authorizes the payment; the Coda operating entity assigned to the publisher and market processes and collects on behalf of the approved publisher; the Coda operating entity assigned to the publisher and market remits the publisher proceeds

Selected product: Codapay.

Payment processing

Codapay: processing, approval & settlement

Review the payment services included with this product and which companies approve the account, process payments and send merchant settlement.

Selected product: Codapay payment processing, orchestration and collection

Included in Codapay

Features included with this product.

Solutions
Alternative payment methodsChargeback managementDirect API
Capabilities
ChargebacksCheckoutFraud and riskGatewayOnboardingPayment operationsPricingReportingSupport

Account approval, payment processing & settlement

Who approves the account, processes payments and sends merchant settlement for Codapay; any separate merchant account or acquirer is shown only when identified.

Included

Payment gateway, PSP and acquirer connections

Integration options, connected PSPs and acquirers, tokenization, 3DS and merchant tools.

Fraud & authentication connections

Screen → authenticate → return decision

Merchant funds
Handles merchant funds at one or more stages
Merchant funds
Yes
Transaction processing
Yes
Merchant account model
Codapay gives the publisher one Coda integration to activated payment channels. Whether a merchant-acquisition service, merchant account or MID is supplied by Coda Payments Pte. Ltd. or a connected provider is contract-, entity-, market- and method-specific; the public product material does not establish one universal model.
Seller funds model
Coda collects the buyer payment under the contracted route. The publisher agreement, Merchant-of-Record allocation, market-specific Coda entity and any connected payment provider determine deductions, settlement currency, timing, reserves and the route by which the publisher receives funds.
Gateway availability
Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.
  1. 01Merchant integrationIntegration options and connected payment providers
  2. 02Payment securityTokenization, authentication and transport security
  3. 03Development & operations

Gateway connections

Merchant integration, PSP and acquirer connections

Integration options

Integration options
  • API
  • Redirect or provider payment flow

Gateway

Payment technology

Connected payment provider

Types of connected payment providers
  • Acquirer
  • Bank
  • Digital wallet
  • Payment processor
  • PSP

Security controls

Tokens and payment authentication

Operations

Webhooks, Control Panel and test environment

Tools used to test an integration and manage live payments.

Webhooks
Yes
Merchant control panel
Yes
API-oriented
Yes
Gateway included
Yes
Onboarding included
Yes
Consumer support included
No
Merchant support included
Yes
Gateway features
  • Single payment API
  • Local and global payment channel routing
  • Direct carrier billing
  • Wallet card bank transfer voucher and cash network connections
  • Payment status reporting
Webhook events
  • Transaction completed
  • Transaction failed
  • Chargeback created
  • Dispute sent
  • Dispute lost
  • Dispute won
  • Early fraud warning
Role in this product
Payment processing and orchestration provider
Account relationship
Approved digital-content publisher whose seller and Merchant-of-Record arrangement is set by the applicable Coda agreement
Payment processing model
Coda receives the purchase request, presents or routes the approved payment method and processes and collects the payment under the contracted sale model. The selected payment channel or contracted acquirer controls the consumer payment instrument and can decline or limit the transaction.
Questions to confirm

Which connectors apply to Codapay payment processing, orchestration and collection?

Connectors are not specified for Codapay payment processing, orchestration and collection.

Is Codapay payment processing, orchestration and collection available?

Available is not specified for Codapay payment processing, orchestration and collection.

Which tokenization types apply to Codapay payment processing, orchestration and collection?

Tokenization types are not specified for Codapay payment processing, orchestration and collection.

Does Codapay payment processing, orchestration and collection support 3-D Secure, and which payment flows are covered?

3-d secure is not specified for Codapay payment processing, orchestration and collection.

Is a sandbox available for Codapay payment processing, orchestration and collection?

Sandbox is not specified for Codapay payment processing, orchestration and collection.

Platform account · Codapay payment processing, orchestration and collection

Can this business open an account for this product?

The Coda operating entity assigned to the publisher and market reviews the publisher, content, integration and route; the selected payment channel, bank, card aggregator, wallet or mobile operator controls payment-channel authorization.

Company eligibility

Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

The approved publisher owns the digital product, fulfilment and product support. The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record for the products, markets and transactions identified in the publisher agreement.

Platform account review

The Coda operating entity assigned to the publisher and market publisher and route review plus the selected payment channel, bank, card aggregator, wallet or mobile operator authorization

The approved publisher owns the digital product, fulfilment and product support. The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record for the products, markets and transactions identified in the publisher agreement.

Account review
Platform account review
Product
Codapay payment processing, orchestration and collection
Regulated-business license
Required license type and issuing jurisdiction are not specified
01Company eligibility & restrictions

Which businesses can open this platform account?

Platform account eligibility and merchant-account approval are separate decisions.

Restricted activity

Business restrictions

Product · MCC · jurisdiction · sales practice

Product, MCC, sales-practice and jurisdiction restrictions are not specified for this product.

02Platform account application

What is needed to open the platform account?

The company, ownership, bank-account, license and integration information required before account activation.

Platform account application

Prepare company information → submit application → account review → activate

Missing company information can delay the platform account review.

Publisher, content & market inputs

Documents to prepare

  1. 01Publisher company and ownership information
  2. 02Digital product rights and catalogue
  3. 03Target markets and payment methods
  4. 04Consumer terms refund and support process
  5. 05Publisher settlement destination

Publisher integration & route activation

  1. 01

    Define the publisher, digital products, territories and target payment methods.

  2. 02

    Confirm the contracting Coda entity, Merchant-of-Record allocation, merchant-acquisition party and funds flow for each selected route.

  3. 03

    Complete publisher, content, compliance, payment-risk and payment-channel review.

  4. 04

    Integrate Codapay or configure the selected Coda-operated store route.

  5. 05

    Test payment, fulfilment, support, refund and settlement scenarios before activation.

Account application checks

Platform account requirements

Application and activation requirements.

Buyer offer & consumer disclosures

Required website pages, disclosures and policies are not specified

Publisher, content & payment-channel checks

  • Publisher, content & payment-channel checks

The approved publisher owns the digital product, fulfilment and product support. The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record for the products, markets and transactions identified in the publisher agreement.

Approved markets and payment routes

The onboarding tasks performed by the provider are not specified

Before applying

Application requirements to confirm

Company eligibility, account-review timing, activation steps and any separate payment-provider approval are not fully specified.

Approval & restrictions

Who reviews the business and which products, jurisdictions or MCCs are excluded.

  1. 01

    Which publisher entity, content, markets and integration will the Coda operating entity assigned to the publisher and market accept?

    Publisher and route acceptance is specific to the agreement and launch scope.

  2. 02

    Which party does the agreement assign as Merchant of Record for each market and transaction, and which sale, tax, fulfilment and support duties remain with the approved publisher?

    The seller and consumer-responsibility boundary is contract- and transaction-specific.

  3. 03

    Which the selected payment channel, bank, card aggregator, wallet or mobile operator routes are enabled, and what authorization and production requirements apply?

    Each payment channel retains its own instrument and route controls.

Payment methods & countries · Codapay payment processing, orchestration and collection

Where can the business process payments, and which methods are available?

Buyer markets and payment channels are activated for the approved publisher, content, market and integration.

Selected product

Codapay payment processing, orchestration and collection

Publisher agreement plus selected payment channels

Selected product

Business applying for processing

Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

The business registration country, acquiring countries and customer countries are separate requirements.

Activated payment channels

  • Agreement scoped payment channels

Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

Availability depends on

  • Product
  • Legal entity
  • Market
  • Configuration
  • Agreement

Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

01Payment-method availability

Card acceptance

Payment-method availability depends on the selected product, legal entity, merchant country, customer country, currency, merchant category and account configuration.

Card acceptance

Card types

  • Credit card
  • Debit card

Card brands

Card brands included with this product are not specified

Bank payment rails

Bank methods

Bank methods by customer country are not specified

Bank-transfer rails

Bank-transfer rails by currency are not specified

Digital wallets

Wallets

Wallet availability by country and currency is not specified

Card payouts

Card payout rails

Card-payout availability is not specified for this product

Connected payment providers

Connected payment providers are not identified for this product.

Connected payment provider
02Countries & availability

Where can the business be registered, where is acquiring available, and where can customers pay?

Business location, merchant-account coverage, acquiring countries and customer location can differ.

Country coverage

Merchant, acquiring, customer and product countries

  1. 01

    Business location

    Where can the business applying for processing be registered?

    Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

    This is where the business is registered; it does not determine acquiring-country or customer-country availability.

    Merchant application review
  2. 02

    Acquiring countries

    Where is merchant acquiring available?

    Handled by the payment provider

    The selected payment channel, bank, card aggregator, wallet or mobile operator

    The Coda operating entity assigned to the publisher and market processes and collects on behalf of the approved publisher; each payment channel controls its instrument and authorization.

    Connected payment provider
  3. 03

    Customer location

    Where can customers pay from?

    Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

    The selected payment channel, bank, card aggregator, wallet or mobile operator determine buyer availability; the publisher agreement defines content, markets and launch scope.

    Connected payment provider

Countries and payment methods

Countries and payment methods to confirm

  1. Which buyer countries, currencies and payment channels are activated for the publisher and content?

    Availability is publisher-, market- and route-specific.

  2. Which payment channel controls authorization, and how are collected funds remitted to the publisher?

    Authorization and remittance responsibilities vary by route.

Pricing & funds · Codapay payment processing, orchestration and collection

What does this product cost, and when are funds settled?

Publisher payment-processing price, collection deductions & remittance

Pricing

Publisher payment-processing price, collection deductions & remittance

Pricing method

Quote or contract specific; amounts not publicly disclosed

Provider, integration, transaction, payment-channel and managed-service charges in the publisher agreement.

01Commercial terms

What makes up the quoted price?

Review the pricing plan, pricing model, fees and contract duration.

Contracted price model

Not specified

Quote or contract specific; amounts not publicly disclosed

Provider, integration, transaction, payment-channel and managed-service charges in the publisher agreement.

02Publisher sale & deduction boundary

Which publisher sale & deduction boundary terms apply?

The publisher owns the digital product, fulfilment and product support; the agreement allocates seller, tax and consumer duties by market and transaction; the provider processes and collects.

Commercial responsibility split

The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction: Merchant of Record · The approved publisher: product and fulfilment · The Coda operating entity assigned to the publisher and market: processing and collection

Payment-instrument authorization and route controls remain with the selected payment channel, bank, card aggregator, wallet or mobile operator.

03Merchant settlement

When are sale proceeds settled, and who sends them to the merchant?

Settlement makes processed sale proceeds available to the merchant.

Merchant settlement

Sale proceeds and settlement responsibility

Collection & remittance

The Coda operating entity assigned to the publisher and market collects buyer payments and remits publisher proceeds under the agreement

Timing, currencies, deductions, reports and invoice requirements are publisher- and route-specific.

Pricing & settlement terms

Terms to confirm in the agreement

Publisher sale & deduction boundary

  1. Which processing, orchestration, collection, integration and support charges does the Coda operating entity assigned to the publisher and market apply?

    Publisher-specific prices and billable events are not fully public.

  2. Which payment-channel costs, refunds, disputes, taxes or other deductions affect publisher proceeds?

    The publisher agreement controls the economic allocation.

Other terms

  1. When and in which currencies are collected amounts remitted to the publisher, and which reports or invoices support the calculation?

    Remittance terms are publisher- and route-specific.

Payment lifecycle · Codapay payment processing, orchestration and collection

How do checkout, payment processing, settlement and reconciliation work?

Publisher integration, payment-channel orchestration & collection

Payment lifecycle

Checkout → authorization → settlement → reconciliation

The selected product determines the integration, transaction controls, payment processing, merchant settlement and reporting.

Selected product

Codapay payment processing, orchestration and collection

Integration, processing, merchant settlement and reporting for this product.

  1. Publisher & content integration

    The Coda operating entity assigned to the publisher and market publisher payment integration

  2. Activated payment channels

    The selected payment channel, bank, card aggregator, wallet or mobile operator

  3. Publisher, provider & payment-channel responsibilities

    The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction: Merchant of Record · The approved publisher: product & fulfilment · The Coda operating entity assigned to the publisher and market: processing & collection · The selected payment channel, bank, card aggregator, wallet or mobile operator: authorization

  4. Publisher reporting & remittance reconciliation

    The Coda operating entity assigned to the publisher and market collection records reconciled to publisher remittance

01

Publisher & content integration

Choose the integration option and who controls the payment page

The API and configuration for the approved publisher, content, markets, buyer offer and payment channels.

Integration path

The Coda operating entity assigned to the publisher and market publisher payment integration

Publisher, digital content, market, integration and each payment method require Coda and payment-channel acceptance. The Merchant of Record, acquiring party, contracting entity and settlement route must be confirmed in the transaction and publisher agreement.

02

Activated payment channels

Gateway integration, security and transaction tools

Channel-specific authorization, customer interaction, sensitive-data and production requirements.

Selected setup

Gateway entry point

How requests enter this product and which integration boundary applies.

Activated payment channels details are not specified.

Activated payment channels

Tokenization, 3-D Secure, webhooks and transaction controls

Gateway
01

Connected parties

Channel-specific authorization, customer interaction, sensitive-data and production requirements.

The selected payment channel, bank, card aggregator, wallet or mobile operator

Buyer payment, refund & dispute lifecycle

From customer consent to scheduled payments and retries

Stored-credential consent, payment scheduling and retry rules apply to each recurring-payment setup.

Other recurring-payment terms

Lifecycle

Buyer payment · channel authorization · provider collection · refund or dispute

Payment initiation, channel authorization, collection, status, refund and dispute events under the publisher agreement.

03

Publisher, provider & payment-channel responsibilities

Who processes transactions, settles merchant funds and controls authorization and capture?

The publisher owns the digital product, fulfilment and product support; the agreement allocates seller, tax and consumer duties; the provider processes and collects; each channel controls authorization.

Publisher, provider & payment-channel responsibilities

The publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction: Merchant of Record · The approved publisher: product & fulfilment · The Coda operating entity assigned to the publisher and market: processing & collection · The selected payment channel, bank, card aggregator, wallet or mobile operator: authorization

The agreement must state collection, remittance, refund, dispute, reporting and support responsibilities for each market and route.

04

Publisher reporting & remittance reconciliation

What reports and reconciliation tools are available?

Buyer payments, channel outcomes, deductions, refunds, disputes and publisher proceeds.

Additional operational terms

Additional reporting and operations terms for this product.

Records & reconciliation

The Coda operating entity assigned to the publisher and market collection records reconciled to publisher remittance

Buyer payments, channel outcomes, deductions, refunds, disputes and publisher proceeds.

Before integration

Integration details not specified

  1. 01

    Which API, checkout, callback, notification, testing and production requirements apply to the publisher and each channel?

    Integration requirements vary by channel and market.

  2. 02

    How are buyer payment states, refunds, disputes, failed delivery and consumer support coordinated?

    The publisher and provider responsibility split is agreement-specific.

  3. 03

    Which collection, deduction and remittance records are authoritative, and how are discrepancies resolved?

    Publisher proceeds must reconcile to provider and channel records.

Merchant funds, risk & support

Codapay: risk, licenses & support

Payment processing, merchant funds, reserves, chargebacks, contracting entity, regulated payment services and support.

CodapayService: Codapay payment processing, orchestration and collection
01 / Processing, reserves & chargebacks

Who can suspend payment processing or hold merchant funds?

Payment processing, reserve or other holds on merchant funds, fraud controls and chargeback handling.

Payment processing & funds

Publisher-agreement payment responsibility split

The Coda operating entity assigned to the publisher and market processes, orchestrates and collects buyer payments. The approved publisher owns the digital product, fulfilment and product support; the publisher or applicable Coda entity, according to the publisher agreement, product, market and transaction acts as Merchant of Record for the products, markets and transactions identified in the publisher agreement; the selected payment channel, bank, card aggregator, wallet or mobile operator retains payment-instrument authorization and payment-route controls.

Role in this product
Payment processing and orchestration provider · Payment processing orchestration and collection
Who receives and settles funds
The selected payment channel, bank, card aggregator, wallet or mobile operator authorizes the payment; the Coda operating entity assigned to the publisher and market processes and collects on behalf of the approved publisher; the Coda operating entity assigned to the publisher and market remits the publisher proceeds

Reserve or security deposit

Reserve amount and release terms are not specified

The reserve amount and release schedule are not specified for this product. A reserve may still be included in the final agreement.

Not specified
Before signingReserve, chargeback, settlement hold and suspension terms3 items to confirmReview contract terms
02 / Legal entity, license & registration

Which legal entity provides the service, and under which license or registration?

A company can use different legal entities, licenses or registrations for different payment products.

For this product

Contracting entity or authorization not specified

Contract-specific publisher payment roles. The contracting entity, applicable license or registration, and permitted services are not specified for Codapay.

The legal entity providing this product, its authorization or registration, and permitted payment services are not specified.

  1. 01 · Contracting entity

    Not specified for this product

  2. 02 · Authorization or registration

    Not specified for this product

  3. 03 · Permitted payment services

    Not specified for this product

Company legal entities, licenses & registrations

Company registrations and payment-services licenses do not identify the contracting entity for every product.

0 entities · license or registration not specified
Before signingContracting entity, payment services license and legal terms3 items to confirmReview contract terms
03 / Support

How can merchants reach support?

Company support hours and contact channels are available. It is not specified which ones cover Codapay payment processing, orchestration and collection and payment-processing or merchant-settlement issues. First-response and resolution targets are also not specified.

Support contacts

Company support hours and contacts

The contacts that cover this product and payment-processing or merchant-settlement issues are not specified.

Other company contacts

Support hours are not specified for these contacts.

Developer

docs.coda.co

Consumer support

global.support.codashop.com/hc/en-us

General

coda.co/terms-conditions
Before signingSupport contacts, hours and response times2 items to confirmReview contract terms
Codapay payment processing, orchestration and collection / Before signing

What should the merchant agreement include?

Confirm the contracting entity, approval conditions, processing fees, merchant funding, reserves, chargebacks, liability, support and termination.

Before signing

Codapay payment processing, orchestration and collection: terms to confirm

Confirm each material commercial, operating and legal term in the agreements that govern this product.

Commercial & funding terms

Processing fees, reserve or security deposit, merchant funding schedule and chargeback fees

Approval, liability & exit

Underwriting conditions, responsible entities, loss allocation, suspension, support and termination

Contract checklist

Terms to review by topic

Jump to the underlying product details

  1. 01Reserves & chargebacksReserve or security deposit, chargebacks, processing suspension and settlement holds.
  2. 02Legal entity & licenseContracting entity, license or registration, and regulated payment services.
  3. 03SupportSupport contacts, hours, response times and escalation.
Merchant agreement

Contract terms to confirm

Review processing fees, merchant funding, reserves, chargebacks, liability, support and termination.

Reserves & chargebacksReserve or security deposit, chargebacks, processing suspension and settlement holds.

  1. For each market and transaction, which party does the publisher agreement assign as Merchant of Record, and which sale, tax, refund, dispute and consumer duties remain with the approved publisher?

    The seller and consumer-responsibility allocation is contract- and transaction-specific.

  2. Which processing, collection, refund and remittance controls belong to the Coda operating entity assigned to the publisher and market, and which authorization controls belong to the selected payment channel, bank, card aggregator, wallet or mobile operator?

    Provider and payment-channel responsibilities differ by route.

  3. What happens to pending purchases, refunds, collected amounts and publisher remittance when a payment route is degraded or withdrawn?

    Route continuity and funds treatment are publisher- and method-specific.

Legal entity & licenseContracting entity, license or registration, and regulated payment services.

  1. When is the approved publisher the Merchant of Record, when is another contracted entity assigned, and how are tax and consumer duties allocated?

    The Merchant-of-Record boundary is agreement-, market- and transaction-specific.

  2. Which operating entity signs the publisher agreement for each market and payment route?

    The operating, seller and payment roles can differ by market and transaction.

  3. Which privacy, payment-data, authentication, incident, retention and audit terms apply to each channel?

    Payment-channel and publisher data duties require a route-specific allocation.

SupportSupport contacts, hours, response times and escalation.

  1. Which contacts, hours and response targets cover publisher integration, payment-route incidents, refunds, collected amounts and remittance?

    Publisher support spans the provider and selected payment channels.

  2. How are payment issues handed off among the Coda operating entity assigned to the publisher and market, the approved publisher and the selected payment channel, bank, card aggregator, wallet or mobile operator?

    Payment support, product support and route escalation belong to different parties.

Product summary

What this product already includes

What this product includes, which restrictions apply and which merchant-agreement terms are not specified.

Included capabilities

Capabilities included with Codapay payment processing, orchestration and collection.

  • A single publisher API for approved local and global payment methods. Coda processes, orchestrates and collects payments under the contracted route, while the publisher agreement determines whether the publisher or an applicable Coda entity is Merchant of Record. Merchant acquisition can be supplied by Coda Payments Pte. Ltd. where its Singapore license and agreement apply, or by a connected provider on another route.