# Explore our Products & Services Welcome to the Coda Docs, your primary resource for exploring our cutting-edge solutions that drive safe, successful, and seamless digital content monetization worldwide! ## Solutions Coda offers a full range of solutions that together form the Operating System for monetizing digital goods. Our solutions are dedicated to maximizing the impact of out-of-app monetization, helping Publishers drive D2C & channel commerce growth, expand payment acceptance, enhance conversion & loyalty, and grow their user base and market coverage. {% @gitbook-payment-search/coda-growth-suite-diagram %} Explore Coda’s solution guides, documentation, and examples, all crafted to help partners understand and integrate our best-in-class solutions. We also have dedicated teams to support every step of the way. Feel free to reach out to us at [Contact Us](/contact-us) Thanks for dropping by! # CODA PORTAL Coda Portal is your single access point to onboard, test integrations, manage agreements, and run operations across payments, distribution, and D2C commerce – making it easy to stay in control and keep things moving. Get started fast with guided onboarding – from setup to signing. Then manage products, promotions, and payments with confidence. Coda Portal puts everything in one secure, easy-to-use platform, so you stay in control from day one. To get started, visit [Coda Portal here](https://portal.coda.co/signup). ### With Coda Portal, you can: * **Complete onboarding seamlessly**, including reviewing agreements, signing contracts, and setting up your organization profile. * **Access and manage agreements** at any time, with full visibility into contract terms, statuses, and renewal timelines. * **Testing** Coda’s solutions using our sandbox tools for ensuring thorough testing * **Monitor performance in real-time**, including sales, transactions, and retention metrics — segmented by country, product, or partner. * **Manage products and offers**, from creating SKUs to setting up promotions and localized pricing. * **Oversee payments and payouts**, with clear reporting and reconciliation tools to stay compliant and organized. * Gain **data-driven insights** with dashboards covering conversion funnels, payer behavior, and market performance. ### This document walks you through how to: * **Navigate the Portal** and complete your organization’s onboarding steps. * **Review and sign agreements digitally**, ensuring compliance and readiness to launch. * **Manage SKUs and offers** to keep your product catalog current. * **Track performance and analytics** to optimize monetization and user engagement. * **Set up team roles and permissions** for secure collaboration across departments. ### Get started fast in 3 Steps 1. **Onboard and sign** – Review contracts, sign digitally, and set up your organization profile in minutes. 2. **Configure and connect** – Add products, localize offers, and fine-tune payments, reporting, and compliance with full settings access. 3. **Launch and grow** – Go live with Coda’s solutions, then track performance and scale with real-time insights. # Activate Your Account Below are all the guides that will assist you in getting started with Coda ## Guides


Complete Contract Signing	Complete Contract Signing
Submit KYB and Content Details	Complete Account Verification to Go Live
Submit Bank Ownership Proof	Submit Bank Ownership Proof
Self-Billing Option	Self-billing

# Complete Contract Signing Learn how to complete contract signing using the Coda Portal. Dear Publisher, Welcome! This document will guide you on how to access Coda’s Content monetization agreement and initiate e-signing on the Coda Portal. We’re thrilled to have you onboard! # 1. Review Publisher Contract/Agreement Click on the Verify Account button or Click on Profile icon and select the **Business Profile** tab.

Before sending the contract for e-signature, please carefully review the Contract/Agreement on this page on the Coda Portal. If you need to download the contract to share it internally, please click on the **Open in a new window** button to open the agreement in a new tab for downloading.

# 2. Send Contract and Initiate e-signing process When ready, please enter the following details of the Signatory 1. Enter the Full Name of the Signatory 2. Enter the email address of the Signatory When the above information is properly filled, click on the **Send Contract** button.

Once you confirm and click on **Confirm**, the contract will be sent to the email of the signatory for e-signing.

# 3. Completing the Contract e-signing Process Once the contract is sent, the status of the agreement will change to **Waiting to Sign.** Make sure that the authorized signatory signs the contract.

Once the authorized signatory signs the contract, the status will change to **Completed.**

That's it! Congratulations on e-signing your agreement with Coda. If you have any questions about the agreement, don't hesitate to reach out to your account manager or raise a ticket from the Coda Portal support tab. # Complete Account Verification to Go Live Submit KYC information on Coda Portal to Verify Account Dear Publisher, Welcome! This document will guide you on how to share your KYB and Content details on the Coda Portal for verification. KYB process is required to use Coda's solutions and comply with regulatory requirements. Let’s proceed. Note: In order to proceed with KYB verification process, you have to complete the Contract e-signing step first. Also, in case you have any queries or need clarification, please reach out to our team by raising a support ticket on the Coda Portal in the **Support** tab. # 1. Login on the Portal ## Logging into your Coda Portal account 1. Open Coda Portal here: [**https:/portal.coda.co**](https://portal.coda.co/) 2. Login using your email address\ \ If you are not sure if your email is registered, please contact your friendly Account Manager. S/he will be able to create a Coda Portal account for you.

## Go to 1. Click on your **Profile** icon at the bottom left, and select **Business Profile**. 2. Once you are on Business profile page, click on **Complete Verification** button on Account verification card

Next, onwards to providing us with more information about your Business details. # 2. Adding Business Details To start the KYB process, please submit the basic business details of your company. Please ensure that the details provided are accurate because you won’t be able to edit any information once the details are submitted. **Ensure that the legal business name and Business registration number exactly matches with the one provided on your incorporation certificate. In case the portal asks Business certificate, please provide any relevant proof that contains the names of all the Directors** In case you face any issues, please raise the support ticket on the [**Coda Portal**](https://bit.ly/4aNqHRf) or reach out to your account manager.

# 3. Adding Company Ownership and Director Details Once you submit the Business details, the next step is to share the Company Ownership and Director details of your company. As we will be dealing with financial transactions, this information is required to abide by the rules and guidelines shared by financial regulatory authorities of various countries. Please indicate information about all the **individuals or entities owning 25% or more equity** in the business. Ensure that you also **list down ALL the Directors**. You can click on the button at the bottom of the page to add multiple Owners/Directors information.

# 4. Final Step: Bank and Content Details **Bank Details** Ensure that you submit the Bank details of your **Company** and not of an individual

**Digital Content Details**

**Anti-Money Laundering Declaration**

Once you complete all the Steps, your KYC application will show as **Under Review**

Our compliance team will verify all the KYB and Content information and might reach out for any clarification or additional requirements. Once the process is successfully completed the status will be changed to **Verified.**

Congratulations! Your Coda Portal account is now verified! If you face any difficulties getting your account verified, don't hesitate to raise a support ticket on the **Coda Portal** # Submit Bank Ownership Proof Bank Ownership proof for smooth settlement process In order to ensure that you receive your settlement amount on time and wihout any delays, please ensure that you upload your Bank ownership proof on Coda Portal and get it Verified Bank Ownership Proof upload section is under Business Profile tab

Upload the Ownership Proof document and our Compliance team will verify it.\ \ **PLEASE NOTE: Your Bank Account name should exactly match with your Legal entity name** Once your Account is fully verified, you are now eligible to process and receive transactions using Coda's solutions without any restrictions or hassle.

# Self-billing Self-billing is an optional feature designed to simplify your administrative workflow. Instead of you creating and sending us an invoice every month, **Coda does the heavy lifting for you**. We generate the invoice on your behalf based on your final settlement figures. #### How It Works 1. **Authorization**: By opting in, you authorize Coda to issue invoices for your content sales. You agree not to send separate invoices for these transactions 2. **Timeline**: Within 10 days after the end of each month, Coda will deliver your self-billed invoice covering the previous month's aggregate sales 3. **Review**: You have 7 business days to review the invoice and notify us of any discrepancies 4. **Payment**: Once the invoice is finalized, Coda will process payment according to the timeline specified #### Benefits of Self-Billing * **Reduced Administrative Burden:** No need to manually generate, format, or send monthly invoices. * **Faster Reconciliation**: Because the invoice is based on final settlement data, it reduces the risk of calculation errors between our two systems. * **Guaranteed Compliance**: Our invoices are designed to meet standard regulatory requirements, and we provide templates for your records. * **Better Organization**: All your billing history is generated in a consistent format, making auditing and tax season much easier. *** #### Your Responsibilities To keep things running smoothly, we ask our partners to: * **Review Records:** Regularly reconcile Coda’s invoices against your own internal records. * **Keep Us Updated:** Please notify us immediately if there are changes to your: * Bank account details. * Tax registration status (e.g., GST registration or cancellations). * Tax treatment or compliance status. > Important Note for Singapore (SG) GST-Registered Publishers: By using self-billing, you agree to remit the GST (in SGD) shown on the invoice as output tax to the Comptroller of GST and confirm you will not issue your own separate invoices for these sales. #### A Note on Accuracy & Records * **Precision**: Coda ensures the accuracy of all self-billed invoices. If an error is found, we will work with you to resolve it per our Agreement terms. * **Record Keeping**: We retain copies of all invoices for auditing and verification. * **Payment Security:** Please note that failure to comply with these obligations (such as updating bank details or tax status) may result in payment delays. *** # Key Features Coda Portal is a comprehensive platform designed to help publishers optimize their out-of-app growth strategy. This documentation provides an overview of key features, benefits, and capabilities that enable you to maximize your growth with Coda ## Guides


Data Insights	Data Insights
Finance Reporting	Finance Reporting
Automate Price Optimization	Automate Price Optimization
Personalized Sales	Personalized Sales

# Data Insights Get Deeper analytics on your title's performances using Publisher Portal! Dear Publisher, Welcome! This document will guide you through using various analytics dashboards on the Insights tab so that you get deeper analytics to improve your title performance and grow with Coda. This is a new feature we are offering to enable your business teams to plan and strategize better. Thank you for joining us in this beta program. Get ready to enter the world of DATA! # 1. Navigating the Insights Tab You can find the **Insights** link on the left panel of your Publisher Portal main screen. There are three different types of dashboards, let's start by looking at the **Overview** dashboard.

# 2. Overview of the Dashboard Details Page ## Overview Once inside the **Overview** dashboard, you will see a range of filters at the top.\ Select the start and end date to view your data within a specific time period.

## Filters There are many filters to assist you in slicing through the messy data and finding valuable insights. You can view the TPV by country, top-performing payment types, top-performing payment methods, and Payment Success rates over a time period. By using the filters properly, you can discover insights about your customers such as being able to check how the new payment methods are performing from the date of launching!

Happy exploring! # 3. Transaction Failures Dashboard Details Page The Transaction failure dashboard gives an overview of payment success rates and error code analytics for your transactions. You can easily identify the most frequent error codes that are encountered in a given period and dive deeper to analyze the reasons for the failed transactions. We also provide Coda’s average payment success rate trendline as a benchmark for comparison.

You can also check the daily error code analysis using the below chart and identify the days with the highest failures for a deeper analysis.\ \ *For example here, Sep 24th Go-Pay experienced the highest number of failed transactions.*

# 4. Period on Period Overview Dashboard Details Page Period-on-period overview dashboard shows you the TPV revenue trends (daily, monthly, and annually.) You can also slice the data using different filters to check the revenue trends across various time periods.

That's it! You have now mastered the basics of the Insights tab! If you have other data points that you'd like to see on the dashboard but it's not available, do not hesitate to reach out to your account manager! # Finance Reporting Invoices, Purchase Orders, and Payment Notices using the Publisher Portal Dear Publisher, Welcome! This document will guide you on how to use the Finance tab in order to download monthly invoices, Purchase Orders, and Payment notices as well as access to Coda's Finance guide to understand settlement and reconciliation processes. Note: Invoices, POs & Payment Notices tabs can be accessed by **Admin Role** and **Finance Role** users only. If you have access to the Publisher Portal but cannot access the Finance tabs, please contact your assigned account manager or your finance team for access. # 1. Navigating to the Finance Tab Upon logging in, you can find the **Finance** tab on the left side of your screen. There are three sub-tabs: Invoices, Payment Notices, and Finance Guide.

First, let's go through **Invoices****.** # 2. Changing the Date Range Once you are inside the Invoice section, you will see monthly invoices and purchase orders. You can browse the data for specific months by using the date range options on the right side of the screen.

# 3. Downloading Invoices & Purchase Orders It is possible to download multiple invoices & purchase orders. You can do so by selecting the checkboxes for desired time periods, and then clicking on the **Download from ... period** button. All documents will be downloaded in a single zip format.

# 4. Browsing Payment Notices Once you are inside the Payment Notices section, you will see monthly payment notices. You can select the date range to browse data for a specific time period.

# 5. Downloading Payment Notices It is possible to download multiple Payment Notices at the same time. You can do so by selecting the checkboxes for desired time periods, and then clicking on the **Download from ... period** button. Each month will represent one Payment Notices file.

# 6. Referencing from the Finance Guide If you require more information about our taxes, reconciliations, and settlement processes. Please visit the **Finance Guide** located on the left panel within the Publisher Portal. It provides a complete overview of the above-mentioned information.

That is all from this guide. If you have any questions about our Finance tab, don't hesitate to reach out to your account manager for a short discussion. # Coda Transaction Report Delivery Options ## Introduction This document provides publishers with an overview of Coda’s transaction reporting options and the specific steps required to access and set up the delivery of these reports. To help publishers stay up-to-date with transaction details, we offer reporting with flexible frequencies: * **Daily** * **Weekly** * **Monthly** ## Sample of Report The report will be sent through a CSV file. Please find the sample of the report below: {% file src="/files/WcMdNu85NyyS1SsPp90I" %} ## Data Points & Types The transaction report provides a comprehensive set of data points, offering publishers detailed insights into each transaction. **By default, the report is generated separately for each country**. For example, if transactions occur in four different countries, you will receive four separate report files.\ \ The following fields are returned in each report: | Field Name | Description | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Transaction Completed Time |

The date and time when the transaction was successfully completed.

It is always based on the transaction’s local timezone.

| | Coda Transaction ID | A unique identifier is assigned by Coda to each transaction for tracking and reference. | | Merchant Order ID | The identifier generated by the publisher or merchant for each order is used to match transactions in their system. | | Merchant ID | The unique identifier associated with the publisher or merchant account within the Coda system. | | Payment Channel | The payment channel name used for the transaction. | | Processing Status |

The status of the transaction.

It is always shown as ‘Successful’, as only successful transactions are returned.

| | Item Name | The name or description of the item (SKU) purchased in the transaction. | | Currency | The currency used for the transaction, represented by its three-letter ISO code (e.g., USD, SGD, IDR). | | Publisher Base Amount | The base amount or item price provided by the publishers. | | Publisher Used Reward Amount |

The value of any rewards or discounts applied by the publisher to the transaction if they choose to co-fund a sponsorship with Coda.

By default, this should be 0.

| | Final Transaction Amount | The total gross amount of the transaction after rewards deduction (excluding the Coda’s fee). | | Publisher Applicable Tax | The amount of tax applied to the transaction based on publisher's tax settings. | | End User Tax Surcharge (US / CA) | A surcharge amount applied specifically to end users in the United States or Canada to cover tax obligations. | | Fee Basis |

The basis or structure of the fee.

Values can be 'Transaction value exclusive of any tax' or 'Transaction value inclusive of any tax'.

| | Percentage-based fee | The fee (in percentage) applied as a percentage of the transaction amount. | | Per-transaction fee | A fixed fee amount charged per transaction, regardless of the transaction amount. | | Publisher Applicable WHT | The amount (in percentage) of Withholding Tax (WHT) applicable to the publisher for this transaction. | | Transaction Structure |

The overall structure or type of the transaction.

Values can be 'Sale of Digital Content' or ''Payment Orchestration Service'.

| ## Report Schedule Our system generates and delivers reports based on the selected frequency. Below is the schedule for report delivery: * **Daily Report**: Sent on the next day at approximately **3 PM SGT**. * **Weekly Report**: Sent on the **first day of the following week**. * **Monthly Report**: Sent on the **2nd day of the following month**. ## Delivery Methods There are three different methods for receiving Coda’s monthly transaction reports: 1. **Email** – Direct report delivery to your inbox. 2. **SFTP** – Secure File Transfer Protocol for automated retrieval. 3. **Webhook Notifications** – Notifications when a report is ready. Each method has specific setup requirements, which this guide will walk you through in detail to ensure smooth and accurate delivery of transaction data. With this documentation, you’ll have all the information needed to configure your preferred reporting method, receive timely reports, and integrate them seamlessly into your workflows. *** ### 1. Delivery via Email #### Overview The daily/weekly/monthly transaction report can be sent directly to your email inbox. This is a simple and straightforward delivery method, suitable for those who prefer to receive and manage reports via their email system. #### Steps to Set Up Email Delivery: 1. **Contact Information**: Provide us with the email address(es) where the monthly transaction report should be sent. You can specify multiple recipients if needed. 2. **Report Format**: The report will be delivered in a **CSV** format. 3. **Frequency**: The email will be sent on the 2nd day of each month and cover all transactions from the previous month. 4. **Subject Line**: The email subject will typically follow this format: * Subject: Codapay Transaction Report(s) for **\[Your Settlement Entity Name] - \[Month Year]** #### Key Considerations * Add our email domain to your safe sender list to avoid reports being sent to spam/junk folders. *** ### 2. Delivery via SFTP (Secure File Transfer Protocol) #### Overview SFTP is a secure method for transferring the monthly transaction report directly to your server. This option is ideal for organizations that want to automate the ingestion of data into internal systems or need higher security for sensitive data. #### Steps to Set Up SFTP Delivery 1. **Server Setup**: You must have an active SFTP server where we can upload the monthly transaction report. This server should be configured to accept connections and allow file uploads. 2. **Provide Server Information**: Our Publisher Support team will ask for details regarding this information below * **IP Address**: Supply the IP address of your SFTP server & port number. * **Username**: Create and provide a username that will be used to access the server. * **Password or SSH Key**: You can either provide a password or set up an SSH key for authentication. We recommend SSH key authentication for higher security. 3. **Whitelist Coda’s IP Address:** Please whitelist these IP addresses to ensure we’re able to send the file to your system.\ 54.251.135.133 52.76.92.206 52.221.161.77 52.221.30.252 13.228.212.196 4. **Folder Path**: Indicate the specific directory path on your SFTP server where the file should be placed. Ensure that the directory has sufficient permissions to allow file uploads. 5. **Test Connection**: Before the first report is sent, a test connection will be established to verify that our system can securely connect to your SFTP server. 6. **File Naming Convention**: The file will be named using the following structure: * \[Settlement Entity Name]*(Settlement Id)*\[Merchant Group Id]*\[Country]Transaction\_Report\[Month]*\[Year].csv #### Key Considerations * Ensure your server has adequate storage for the monthly report files. * Make sure to keep your server credentials updated, especially if password rotation policies are in place. * If using SSH key authentication, ensure that you store and manage the key securely. *** ### 3. Delivery via Webhook Notification #### Overview Webhook notifications provide a method of alerting your system when the monthly transaction report is available. Instead of retrieving the report from email or SFTP, a webhook will notify your system, which can then download the report from a secure URL. #### Steps to Set Up Webhook Delivery 1. **Webhook URL**: You need to provide a webhook endpoint (URL) where we will send a POST request once the monthly report is generated and ready for download. 2. Whitelist Coda’s IP Address. Please whitelist these IP addresses to ensure we’re able to send the file to your system\ Production IPs: "52.221.161.77", "52.221.30.252", "13.228.212.196" 3. **Authentication**: * Optionally, the webhook can include an **authentication header** (such as a bearer token or API key) for security. * If you require this, provide the necessary credentials for the authentication process. **Webhook Payload**: When the report is ready, we will send a POST request to your webhook URL with the following JSON payload: **Sample payload for report notification:** ```json { "notificationType": "report", "data": { "reportCycle": "daily"|"weekly"|"monthly", "reportUrl": "finance-files.codapayments.com/fileurl", "reportName": "[Settlement Entity Name]_(Settlement Id)_[Merchant Group Id]_[Country]_Transaction_Report_[Month]_[Year].csv ", "reportPeriodStart": "yyyymmdd", "reportPeriodEnd": "yyyymmdd", "reportEnvironment": "all"|"codapay"|"distribution"|"codashop"|"xshop"|"custom-commerce" } } ``` **Report notification parameters:**

Parameter Name	Type	Description
notificationType	string	Type of notification. Will be “report”
data	object	Contains payload of the notification
data.reportCycle	string	Frequency of the report sent: daily / weekly / monthly
data.reportUrl	string	File address of the report
data.reportName	string	Name of the report
data.reportPeriodStart	string	starting transaction date in local country timezone
data.reportPeriodEnd	string	ending transaction date in local country timezone
data.reportEnvironment	string	Environment solution of the transaction

**Sample payload for invoice notification:**

{
    "notificationType": "invoice",
    "data": {
        "reportCycle": "monthly",
        "reportUrl": "finance-files.codapayments.com/fileurl",
        "reportName": "PublisherName_Invoice_date.csv",
        "reportPeriodStart": "yyyymmdd",
        "reportPeriodEnd": "yyyymmdd",
        "reportEnvironment": "all"
    }
}

**Invoice notification parameters**

Parameter Name	Type	Description
notificationType	string	Type of notification. Will be “invoice”
data	object	Contains payload of the notification
data.reportCycle	string	Frequency of the report sent: monthly
data.reportUrl	string	File address of the report
data.reportName	string	Name of the report
data.reportPeriodStart	string	Invoice date
data.reportPeriodEnd	string	Invoice due date
data.reportEnvironment	string	Environment solution of the transaction

**Responses** No **Response** **body** is required for the response, the status code must be **200**. | **Code** | **Description** | | -------- | --------------- | | 200 | OK | #### Key Considerations * Ensure your webhook URL is accessible from external sources and secured with authentication to avoid unauthorized access. * The URL provided for the report download will expire after a certain period (typically 30 days), so make sure to download the file in a timely manner. * Implement logging in your system to track webhook notifications and any potential errors in the report retrieval process. *** ## Comparison of Delivery Methods

Method	Delivery Time	Setup Complexity	Security Level	Automation Potential
Email	2nd day of each month	Low	Moderate (email security depends on the recipient)	Low
SFTP	2nd day of each month	Moderate	High (secure transfer)	High (automated file handling)
Webhook	2nd day of each month	Moderate	High (requires secure endpoint)	High (full automation of report retrieval)

## Conclusion We offer three flexible methods to deliver your monthly transaction report, each tailored to different needs in terms of security, automation, and ease of use. Whether you prefer a simple email delivery, a secure file transfer via SFTP, or an automated system triggered by webhook notifications, we can accommodate your requirements. If you have any questions or need assistance setting up any of the delivery methods, please contact our support team for guidance.
### FAQ This section provides answers to commonly asked questions about our reporting system, including report types, delivery schedules, file formats, and webhook handling. If you need further clarification, please refer to the FAQs below or reach out to our support team for assistance.

What types of reports do you provide?

We currently provide transaction reports on a daily, weekly, and monthly basis. You can choose the option that best suits your needs.

What is the format of the transaction report?

The report will be delivered in CSV format. By default, the file will be separated by country. If you have transactions from five countries, you will receive five separate files accordingly.

What data points are included in the transaction report?

The transaction report includes a comprehensive set of data points, such as Transaction Completion Time, Coda Transaction ID, Payment Channel, and more. Refer [to this section](#report-data-points) to see the details.

What is the estimated size of each report?

Each report will follow the limit of a single CSV file, which can contain up to 900,000 records. If the total number of records exceeds this limit, multiple CSV files will be generated and bundled together in a single ZIP file for easy access.

How can we automate the process of sending transaction reports to our system?

You can use SFTP delivery or Webhook Notifications. SFTP delivery transfers transaction reports directly to your server while Webhook Notifications notify your system when a transaction report is available, allowing you to download it from a secure URL

For webhook notification, how many webhook notifications can be sent in parallel?

Does the webhook always need to return a 200 OK status?

Yes, currently only the 200 OK status is recognized and processed. We will update the status accordingly once we introduce more status

How long is the report download URL valid?

The report download URL is valid for 12 months before it expires.

Are the reports processed in real-time?

No, reports are not processed in real-time. The daily report is generated and sent the following day at around 3 PM SGT. The monthly report is sent on the 2nd day of the following month.

## Version History | Version | Date | Changelog | | ------- | ----------- | ----------------------- | | 1.0.0 | 22 Oct 2024 | First Draft Version | | 1.0.1 | 03 Jan 2025 | Adding Data Points | | 1.0.2 | 18 Feb 2024 | Adding Sample of Report | | 1.0.3 | 25 Feb 2024 | Adding FAQ Section | # Automate Price Optimization ## What is 'Automate Price Optimization' in the Publisher Portal? * An easy way for Publishers to set the price automation with Coda’s Publisher Portal * Once the Publisher configures the Codashop price to be the same or less than legacy app stores, our system will monitor the prices regularly and ensure that they meet the configuration settings. ## Why enable 'Automate Price Optimization' on Publisher Portal? For all Publishers, automating Price Optimization provides the following benefits * Maintain the price based on defined rules whenever there is a price disparity between Codashop vs legacy app stores * Allows you to always **remain competitively priced** on Codashop which charges much lower fees than the legacy app stores. * Receive more price optimization insights to maximize your TPV with Codashop. * **Improve ARPU** and users’ **stickiness** with the platform. * Generate comprehensive price reports showcasing how you are growing revenues with Coda # Step 1: Click on the Price Optimization Banner Select **Codashop titles** on the left navigation menu and click on **Configure automation** on the Price Optimization banner.

# Step 2: Select Automation Option ### Click on the **Automation Option**

### Set the **Automation Option** as: * Lower than Google/Apple store (or) * Same as the Google/Apple store {% hint style="info" %} Automation tip: Coda charges \~50% less than legacy app stores. Keeping the prices lower than Google/Apple stores will earn you higher margins! {% endhint %}

# Step 3: Select the Titles If you select the automation option - **Lower than Google/Apple store,** specify the **% percentage** by which you want to lower the prices.

Once you select the **% percentage**, the next step is to **Select the Title** for which you would like to make price changes.

# Step 4: Price Optimization Automated Once the configuration is activated, the prices are constantly monitored and changed accordingly to match the automation settings defined by you.

You can always automate the configuration by clicking on the **Edit Configuration** button. If you have any questions or require further clarification, please contact our [Partner Support team](/contact-us). # Coda Portal Appendix


Coda's Pricing Template	Coda’s Pricing Template
Additional Info Template (Optional)	Additional Info Template (Optional)
Title Content Submission Best Practices	Title Content Submission Best Practices
SKU/Product Images Guidelines	SKU/Product Images Guidelines

# Coda’s Pricing Template The Bulk SKU Upload template is a CSV file used to create and update multiple SKUs (in‑app purchase items) for a title in a single upload. You can export your title's current SKUs to this format, edit prices, availability, and localized text in a spreadsheet, then re‑upload the file to apply the changes in bulk. Each **row** represents one SKU (product). Each **column** represents one attribute of that SKU. Column names are case‑sensitive and must match exactly. > This reference describes the general template structure. Column availability may vary slightly by title configuration — if a column described here doesn't appear in your export, contact your Coda account manager. A sample file, `sample_bulk_sku_upload_template.csv`, is included alongside this page. It uses placeholder SKUs and dummy translations to illustrate each pricing scheme and field combination described below — download it as a starting point for your own upload. *** ### 1. How the template works 1. **Export** — Download your title's current SKUs as a CSV from the portal. Every existing SKU appears as one row, pre‑filled with its current values. 2. **Edit** — Update values directly in the CSV (e.g. change a price, extend a sale window, add a new SKU as a new row). 3. **Re‑upload** — Upload the edited CSV back into the portal. Rows are matched to existing SKUs by `ProductID`; a `ProductID` not already in the system creates a new SKU. 4. **Review** — The portal validates the file and reports any row‑level errors before changes go live. *** ### 2. Core SKU fields These columns appear once per row and control the SKU's identity, pricing model, availability window, and purchase limits. | Column | Required | Type / Format | Description | | --------------------------- | -------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ProductID` | Yes | String | The unique identifier for the SKU. Used to match the row to an existing SKU on upload — **do not change this value for an existing SKU**, or the upload will create a duplicate instead of updating it. | | `Pricing_Scheme` | Yes | Enum: `Real Currency`, `Freebie`, `Loyalty Currency`, `Loyalty Milestone` | Determines how the SKU is "paid for." See Section 3 for how this affects the other pricing fields. | | `Price_US_Default` | Yes | Decimal (USD) | The SKU's base/list price in US dollars. Used as the reference price even for non‑cash schemes (set to `0.00` for `Freebie`, `Loyalty Currency`, and `Loyalty Milestone` rows). For `Real Currency` SKUs this should match the `Price_US` column. | | `Price_` | No | Decimal, one column per country | Per‑country override price in local currency. Only meaningful when `Pricing_Scheme = Real Currency`. See Section 5. | | `Main_IconPath` | Yes | String (relative file path) | Path/filename of the SKU's storefront icon image, matched against the image assets uploaded for the title (e.g. `festivefixtures/Loyalty_Offer.webp`). | | `Start_Time` | No | ISO‑8601 datetime, `YYYY-MM-DDTHH:MM:SS` | When the SKU becomes available for purchase. Leave blank for "available immediately." | | `End_Time` | No | ISO‑8601 datetime, `YYYY-MM-DDTHH:MM:SS` | When the SKU stops being available. Leave blank, or use the sentinel value `2100-01-01T00:00:00`, for "no end date." | | `Web_Store_Exclusive` | Yes | Enum: `Yes`, `No` | Whether the SKU is sold only through the web store, as opposed to also being purchasable in‑app. | | `Sku_Purchase_Limit` | No | Integer | Maximum number of times a single player can purchase this SKU within one refresh window (see `Refresh_Rate`). Leave blank for no limit. | | `Refresh_Rate` | No | Integer (days) | Length, in days, of the purchase‑limit window. E.g. `1` = daily limit, `7` = weekly, `30` = monthly. Very large values (e.g. `100000` or more) are used as a "never refreshes" sentinel — i.e. the limit applies once, for the lifetime of the SKU. Only meaningful together with `Sku_Purchase_Limit`. | | `Purchase_Limit_Start_Date` | No | ISO‑8601 datetime | The anchor date the purchase‑limit window counts from. Typically set equal to `Start_Time`. | | `Loyalty_Currency_Earned` | Yes | Decimal | Amount of loyalty currency the player earns from purchasing this SKU. For `Real Currency` SKUs this is typically **\~100× the USD price** (e.g. a $0.99 SKU earns ≈99 points); some promotional/bonus SKUs earn at a higher multiplier (e.g. 200×). Set to `0.00` when not applicable. | | `Loyalty_Currency_Burned` | Yes | Decimal | Amount of loyalty currency a player must redeem to acquire this SKU. Only meaningful when `Pricing_Scheme = Loyalty Currency`; set to `0.00` otherwise. | *** ### 3. Pricing Scheme and related fields `Pricing_Scheme` determines which of the pricing columns actually apply to a given row: | `Pricing_Scheme` | What it means | Fields that apply | | ------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `Real Currency` | Standard paid purchase, charged in real money. | `Price_US_Default`, `Price_` columns. `Loyalty_Currency_Earned` is typically populated (points earned per purchase); `Loyalty_Currency_Burned` = `0.00`. | | `Freebie` | Free item, no charge. | `Price_US_Default` = `0.00`, all `Price_` blank. `Loyalty_Currency_Earned`/`Burned` = `0.00`. Commonly paired with a `Sku_Purchase_Limit` of `1` and a large `Refresh_Rate` (one‑time claim). | | `Loyalty Currency` | Redeemed using the player's loyalty/points balance instead of cash. | `Loyalty_Currency_Burned` is populated with the redemption cost. `Price_US_Default` = `0.00`. | | `Loyalty Milestone` | Reward automatically granted at a loyalty milestone (not directly purchased). | Pricing fields are typically all `0.00`; availability is controlled by `Sku_Purchase_Limit` / `Refresh_Rate` rather than price. | *** ### 4. Localized text columns Five text fields — **Title**, **Description**, **Category**, **Item\_Main\_Title**, and **Item\_Sub\_Title** — each repeat once per supported language, using the pattern: ``` _ ``` For example: `Title_en`, `Title_fr`, `Title_ja`, `Description_en`, `Category_en`, `Item_Main_Title_en`, `Item_Sub_Title_en`, etc. | Field prefix | Required | Description | | ------------------------ | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | `Title_` | `_en` required; others recommended | The SKU's display name shown in storefront listings. | | `Description_` | No | Longer descriptive text for the SKU. Optional and frequently left blank — not all storefront surfaces display it. | | `Category_` | Recommended | The category/grouping label the SKU is shown under in the storefront (e.g. "FC Point Offer Permanent"). | | `Item_Main_Title_` | `_en` required; others recommended | The primary title shown on the item itself (as opposed to the storefront listing) — commonly the same value as `Title_`. | | `Item_Sub_Title_` | No | A secondary line of text shown under `Item_Main_Title_` on the item. | Leave a language's column blank to fall back to the default/English text on that surface (behavior may vary by title configuration). #### Supported language codes | Code | Language | Code | Language | | ---- | --------- | ---- | ---------- | | `en` | English | `ru` | Russian | | `zh` | Chinese | `da` | Danish | | `ar` | Arabic | `fi` | Finnish | | `ro` | Romanian | `lo` | Lao | | `tr` | Turkish | `pt` | Portuguese | | `pl` | Polish | `km` | Khmer | | `th` | Thai | `es` | Spanish | | `sv` | Swedish | `de` | German | | `nl` | Dutch | `sk` | Slovak | | `ms` | Malay | `el` | Greek | | `mn` | Mongolian | `id` | Indonesian | | `ja` | Japanese | `it` | Italian | | `my` | Burmese | `cs` | Czech | | `no` | Norwegian | `hu` | Hungarian | | `fr` | French | | | *** ### 5. Per‑country pricing columns For SKUs using `Pricing_Scheme = Real Currency`, price can be overridden per country using columns named: ``` Price_ ``` using the country's ISO 3166‑1 alpha‑2 code. If a country's column is left blank, the storefront falls back to a computed/default price derived from `Price_US_Default`.

Full list of supported country codes

| Code | Country | Code | Country | Code | Country | | ---- | ------------- | ---- | -------------------- | ---- | -------------- | | `US` | United States | `IE` | Ireland | `KZ` | Kazakhstan | | `DE` | Germany | `EC` | Ecuador | `TH` | Thailand | | `HK` | Hong Kong | `MM` | Myanmar | `LA` | Laos | | `TW` | Taiwan | `MN` | Mongolia | `PE` | Peru | | `PT` | Portugal | `EG` | Egypt | `CZ` | Czech Republic | | `DK` | Denmark | `AE` | United Arab Emirates | `PH` | Philippines | | `PY` | Paraguay | `UY` | Uruguay | `TL` | Timor‑Leste | | `HU` | Hungary | `IN` | India | `PK` | Pakistan | | `QA` | Qatar | `ZA` | South Africa | `PL` | Poland | | `MA` | Morocco | `IQ` | Iraq | `TR` | Turkey | | `ID` | Indonesia | `IT` | Italy | `LK` | Sri Lanka | | `MX` | Mexico | `MY` | Malaysia | | | | `ES` | Spain | `AR` | Argentina | | | | `AT` | Austria | `AU` | Australia | | | | `NG` | Nigeria | `RO` | Romania | | | | `NL` | Netherlands | `NO` | Norway | | | | `BD` | Bangladesh | `NP` | Nepal | | | | `BE` | Belgium | `FI` | Finland | | | | `BH` | Bahrain | `JP` | Japan | | | | `FR` | France | `NZ` | New Zealand | | | | `BO` | Bolivia | `SA` | Saudi Arabia | | | | `BR` | Brazil | `SE` | Sweden | | | | `SG` | Singapore | `SK` | Slovakia | | | | `KE` | Kenya | `GB` | United Kingdom | | | | `KH` | Cambodia | `CA` | Canada | | | | `CH` | Switzerland | `CL` | Chile | | | | `GR` | Greece | `CO` | Colombia | | | | `KW` | Kuwait | `GT` | Guatemala | | |

*** ### 6. Reserved / internal columns The following columns may appear in your export but are reserved for specific configurations and are typically left blank: | Column | Notes | | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `EventPackage` | Links a SKU to a specific promotional event/package grouping. Only used for titles running event‑based bundles — leave blank unless your Coda account manager has instructed you to set a specific package ID for a campaign. | | `Active_Cogs` | Internal cost‑of‑goods‑sold tracking flag. Leave blank; contact your Coda account manager if you need COGS tracking enabled for a SKU. | | `Cogs_Currency` | Currency code paired with `Active_Cogs`. Leave blank unless directed otherwise. | *** ### 7. Sample rows The included sample CSV covers the following illustrative SKUs: | ProductID | Pricing Scheme | What it demonstrates | | ------------------------ | ----------------- | ------------------------------------------------------------------------------------------------ | | `GEMPACK_100` | Real Currency | A basic, always-available currency pack with no purchase limit. | | `GEMPACK_2500_BONUS` | Real Currency | A limited-time promo with a bonus loyalty multiplier (earns 200× instead of the usual \~100×). | | `FOUNDERS_BUNDLE` | Real Currency | A web-store-exclusive, one-time-only bundle (`Sku_Purchase_Limit = 1`, sentinel `Refresh_Rate`). | | `WELCOME_GIFT` | Freebie | A one-time free gift for new players, capped for the SKU's lifetime. | | `DAILY_LOGIN_REWARD` | Freebie | A free reward that resets daily (`Refresh_Rate = 1`). | | `LOYALTY_SKIN_COMMON` | Loyalty Currency | A low-cost item redeemed with loyalty points, no purchase limit. | | `LOYALTY_SKIN_LEGENDARY` | Loyalty Currency | A higher-cost redemption capped at 3 per month. | | `MILESTONE_REWARD_TIER5` | Loyalty Milestone | A reward auto-granted at a loyalty milestone rather than purchased. | | `SEASON_PASS_PREMIUM` | Real Currency | A seasonal pass limited to one purchase per season window. | | `GEMPACK_50` | Real Currency | A minimal row with only the required fields populated. | To keep the file readable, only `en`, `fr`, `es`, `de`, `ja`, and `zh` are filled in for the localized text columns, and only `US`, `GB`, `SG`, `JP`, `BR`, and `DE` are filled in for per‑country pricing — every other language/country column is present (per the full template) but left blank, exactly as most real exports leave the majority of these optional columns blank. *** ### 8. Tips and common errors * **Don't change `ProductID`** for existing SKUs — this is the match key. Changing it creates a duplicate SKU rather than updating the original. * **Keep the sentinel end date** (`2100-01-01T00:00:00`) or leave `End_Time` blank for SKUs that shouldn't expire. * **Real Currency SKUs should always have `Price_US` populated** — it's used as the fallback reference price alongside `Price_US_Default`. * **`Sku_Purchase_Limit` and `Refresh_Rate` work as a pair** — setting one without the other may produce unexpected results. * Column headers are **case‑sensitive** — don't rename them when editing in Excel/Sheets. Here’s the [Sample Google Sheet (Pricing template)](https://docs.google.com/spreadsheets/u/0/d/1QBehJqAGAtEnOdZcqrxkkFYWJnhQCSTkc8HOVoPYFtU/edit). Download and create a copy to submit the pricing information. Convert the Price & SKU info tab in the sheet in CSV format and upload it to the Coda Portal. You can also download and view the sample or from the Coda Portal. {% file src="/files/c32Iw4HSXmApDPfuN9Mf" %} Coda Product (SKU) Price Template {% endfile %} The sample file contains an example product. Your import file probably contains many more products and variants. If you use the sample file to create your own import file, then make sure that you create a copy of the file and remove all the example products. # Additional Info Template (Optional) You can also download and view the sample from here or from the Coda Portal. {% file src="/files/vLXUSwcTSQcDsQ9MU92X" %} The sample file contains an example package. Your import file probably contains many more package items and variants. If you use the sample file to create your own import file, then make sure that you create a copy of the file and remove all the example packages.

Title	Description
ProductID	- Product ID or SKU ID - Product ID is mandatory (max 100 characters)
EventPackage	- Used as an identifier by the Publisher to deliver correct package items associated with a product. If the Publisher can identify the package items using Product ID then this field is not mandatory. - Integer Value - Not mandatory
Value	- Number of reward items - Integer Value
Title_LanguageCode	- Product package item Name. The default language code is en for English. Please add additional columns if you want to provide translations in other languages. - The column header should be Title_LanguageCode - Refer to the table in the sample Google sheet for Language Codes. - At least one language is required for every package item else it will be discarded
Description_LanguageCode	- Product package item description. The default is en for English. Please add additional columns if you want to provide translations in other languages. - The column header should be Description_LanguageCode - Refer to the table in the sample Google sheet for Language Codes. - Not mandatory
IconPath	- Image icon path or URL for identifying images of product package items from the zip folder - Not mandatory

# Title Content Submission Best Practices ## Best Practices Info

Field name	Description	Validation
Tile Image	Icon for your title to be shown on Codashop country homepage	Dimensions: 178px (w) × 178px (h) The file type should be JPG or PNG The size must be less than 25kb The image must not have rounded corners
Banner Image	Banner image for your title, to be shown on Codashop product page	Dimensions must be 640px (w) x 241px (h) The file type should be JPG or PNG The size must be less than 100kb
Links for your title	Types of links supported, to be shown on Codashop product page: - Apple App Store - Google Play Store - Direct Android Download - PC Download - Website URL	Any links provided must be in valid full URL format
User ID input	For Codashoppers to provide their in-game User IDs & do top-up. To be shown on Codashop product page Our Integration team will set up these input fields based on your specifications.	Validation Type: select from options: - User ID - User ID + Server (Dropdown) - User ID + Server (Input) Others User ID field name: free text input with a 1,000-character limit. User ID validation: free text input with a 1,000-character limit.
Helper Image	Helper image to assist Codashoppers to find their in-game User IDs. To be shown on Codashop product page as a tooltip next to the User ID input	The file type should be JPG, PNG, or GIF. For static images, the file size must be less than 150kb. For GIFs, the file size must be less than 1 MB.
Helper text	A quick note to guide on how users can obtain their in-game User ID and Server ID/Name if applicable. To be shown on Codashop product page below User ID input	Latin characters only We recommend one sentence only for your helper text.
Title Description	A description of your title. To be shown on Codashop product page below the top-up form	Maximum 4,000 characters.
Voucher Redeem Button URL	If you are selling a voucher code, this is the link Codashoppers can click to open the website where they can redeem the voucher code they just bought. To be shown on Codashop Order Summary page (after a transaction is completed), embedded in the “Redeem Now” widget	Any links provided must be in valid full URL format.
Voucher Redemption instructions	Any additional instructions you would like to give Codashoppers about redeeming their voucher codes. To be shown on Codashop Order Summary page (after a transaction is completed), under the “Redeem Now” widget	We recommend using a maximum of 1,000 characters.
Order details product image	A specific image Codashop will show as part of the Order details section of the Order Summary page, next to the item name.	The file type should be in JPG or PNG
Important Note	Any important note or instruction you would like to give Codashoppers who have just purchased an item for your title. To be shown on Codashop Order Summary page (after a transaction is completed), it will be shown under “Order details.”	We recommend using a maximum of 1,000 characters.

## Tile Image

## Banner Image

## Links for your Title

## User ID input field, dropdown, and server input field

## Helper Image

## Helper Text

## Title Description

## Voucher Redeem Button URL

## Redemption Instructions

## Order Details Product Image

## Important Note

# SKU/Product Images Guidelines ## SKU/Product Image Guideline | Category | Response | | ---------------- | -------------------------------------- | | Image format | PNG | | Image dimension | 150px by 150 px (aspect ratio 1:1) | | Image background | Image background has to be transparent | | Resolution (PPI) | 72 PPI | ## Examples of Good Image Content

Image content should not exceed 150px by 150px

Image content should cover at least 85% of one dimension (128px by 128px)

Image content should follow an aspect ratio of at least 0.65

## Examples of Poor Image Content

Image content should not be stretched horizontally or vertically

Image content must adhere to the minimal dimensions provided or it will not be eligible to users

# Onboarding Compliance # Security Overview In this section, you will gain insights into how **Coda consistently achieves a 99.99% security uptime through continuous 24/7 real-time monitoring**. Below, you'll find quick links to each relevant section:


Data Privacy			Broken link
Application Security			Broken link
Network Security			Broken link
Security Operations			Broken link
Access Control Management			Broken link
Human Resource Security			Broken link

# Data Privacy

Data Privacy	Context
Personal Identifiable Information	Personal data points that Coda Payments collects from Codashop users in its capacity as an independent data controller Personal and contact details of the players such as first name, last name, email address, and phone number (depending upon the product/service/use case); Account details of the players such as in-app/in-game ID/publisher affiliation; Device data such as IP address; Correspondence data; Order data such as transaction ID etc. Cookies and/or statistical/analytical data; Documentation that helps us verify the accuracy of the information provided by our users if it is required for fulfilling certain obligations or for providing certain services; Social media links or public profiles of our users if they submit it; and User account passwords. Personal data points that Coda Payments may share with the publishers (Depending upon the terms of the Data Processing Agreements and the relevant data privacy regulations as well as the purpose/requirement): Personal and contact details of the players such as first name, last name, email address, and phone number; Account details of the players such as in-app/in-game ID/publisher affiliation; Device data such as IP address; Correspondence data; Order data such as transaction ID etc. Personal data points that Coda Payments collects from publishers 1. Professional and contact details of the publisher’s authorized signatories and employees; 2. KYC and compliance information
Coda Payments's role as a Data Controller	1. Coda Payments's role in the data processing arrangement is that of an independent data controller, as such, our template reflects a controller-to-controller arrangement along with a provision for controller-to-processor transfers (Coda Payments as a processor) on the off chance that data is transferred to Coda Payments by the publisher in the capacity of a data controller and to safeguard the publisher interests therein. 2. This is owing to the hybrid nature of Coda Payments' business model, wherein Codapay is provided as a bundled service along with Codashop. In a normal payment service provider model, Coda Payments would have been a data processor. 3. Codashop is an independent e-commerce website/marketplace operated by Coda Payments through which Coda Payments provides content monetisation services to publishers. It has its own user base, these users visit Codashop to purchase content or top up their in-game accounts with in-game currencies (digital goods) which are posted for sale on the Codashop website. 4. While doing so, these end users accept Coda Payments' terms and conditions and privacy policies and become Codashop customers to avail the digital goods. In this user journey, user data is directly collected by Coda Payments for its own purposes mentioned in its privacy policy which is displayed on the Codashop website. The publishers of the game titles do not come into the picture from a data privacy/collection or transfer perspective in this user journey. 5. As such, both parties are independent controllers of the data they collect directly from the end users.
Data Security	Coda Payments adopts an insight-driven framework for the implementation of our data security program. A data dictionary/glossary is consolidated to record all types of sensitive data, which will cross-reference the policies and procedures required in the data classification. This is used in conjunction with a data loss prevention platform to detect and block leakage of sensitive data, followed by continuous assessment and updates of the underlying controls to ensure the relevancy and effectiveness of changing threats, business practices, and landscape.
Encryption	Coda Payments implements encryption standards based on industry best practices and to meet regulatory/compliance requirements such as AES-256 database encryption algorithms to protect the sensitive data at rest and where applicable, TLS1.2 and above, with reputed certificate authority signed certificates with 2048-bit RSA keys to secure the sensitive data in transit.

# Application Security | Application Security | Context | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Penetration Testing** | Coda Payments performs both manual and automated penetration testing to identify any vulnerabilities in our Internet-facing and internal applications. This also includes API-specific testing of vulnerabilities to include business logic and transaction flows. | | **Static Code Analysis** | Coda Payments performs static source code scanning at the development and deployment stage to identify any vulnerabilities at the code level. | | **Secure Software Development Lifecycle** | Coda Payments implements a secure software development lifecycle and provides secure coding training to all engineers to enhance secure coding practices. | # Network Security | Network Security | Context | | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Network Monitoring** | Coda Payments network is placed behind a zero-trust network, integrated with the use of security services to continuously monitor, audit, and analyze any suspicious or malicious network traffic. | | **Network Vulnerability Scanning** | Coda Payments performs regular network vulnerability scanning to discover any vulnerable ports or unused services to reduce exposure to network exploits and attacks. | | **Denial of Service Mitigation** | Coda Payments employs DDoS mitigation to block external DDoS attacks with edge networks, reliable infrastructure, and a variety of mitigation systems. | # Security Operations | Security Operations | Context | | --------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Website Phishing and Social Media Impersonation** | Coda Payments engages a dedicated security partner who specializes in website phishing and fake social media impersonation to perform continuous detection of these Internet threats and perform enforcement action to remove them. | | **Malware Protection** | Coda Payments implements a behavioral-based anti-malware system integrated with endpoint detection response capability to detect different types of malware attacks and perform incident response procedures. | | **Infrastructure Monitoring** | Coda Payments implements infrastructure monitoring to detect different types of infrastructure threats ranging from network intrusion, unauthorized access, exfiltration, privilege escalation, and other types of anomalous activity. | # Access Control Management | Access Control Management | Context | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **2-Factor Authentication** | Coda Payments implements multi-factor authentication via different channels across various systems and platforms. | | **Access Controls** | Coda Payments defines authorization role-based access controls to grant different roles with respective permissions according to the responsibilities of each user. | | **Auditing and Logging** | Coda Payments logs all user access and user management activities for proper accountability, audit, and investigation purposes. | # Human Resources Security | Human Resources Security | Context | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Security Awareness Training** | Coda Payments conducts continuous security awareness training for all staff to educate them on real-life scenarios and case studies. This ensures secure responses to various daily, security-related events. | | **Data Privacy Training** | Coda Payments conducts continuous data privacy training for all staff including contractors, consultants, and interns on an annual basis to educate and prepare them to handle personal data in different day-to-day situations that they could come across in their work. Besides, focused training is also provided to certain staff members from certain functions who are engaged in significant data processing activities. | | **Phishing Exercises** | Coda Payments conducts continuous internal email phishing exercises to increase awareness of the latest phishing attacks and methods to ensure the secure handling of these emails. | # Onboarding Welcome to the Compliance Documentation provided by Coda Payments. This section is designed to provide you with comprehensive information regarding compliance requirements. Here, you will find all the relevant details to ensure a clear understanding of our compliance standards. Should you have any inquiries, please feel free to contact your dedicated account manager. We are here to assist you. # Compliance Certifications

Certification	Details
PCI DSS	Coda Payments processes fewer than the threshold of 6 million credit and debit card transactions required for the PCI DSS Level 1 compliance level which constitutes a minority of the transactions processed by our Codashop users. Coda Payments self-assesses its PCI DSS compliance with the SAQ A-EP form and self-attests to that compliance annually. Hence Coda Payments do not have any independent PCI certification as we work with a number of major card payments PSPs that are PCI certified.
Data Privacy regulations - GDPR, CCPA, PDPA, LGPD, etc.	Coda Payments has the required technical and organizational measures as well as policies and procedures in place such as those to provide for data subject rights requests, personal data breach notification, etc. In line with the requirements of the various data privacy regulations including EU-GDPR, Singapore PDPA, and the US CCPA
ISO 27001, SOC 2 Type II	Coda Payments is currently not certified with ISO 27001 or SOC 2.
Monetary Authority of Singapore (MAS) Technology Risk Management (TRM)	Coda Payments is pursuing MAS technology risk management compliance certification for fintech companies based in Singapore.

# General Compliance | General Compliance | Context | | ------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Codashop's business model is compliant with Google and Apple's 3rd party payment policy.** |

Apple’s guidelines state that if an app operates across multiple platforms, users can access content acquired in the app, including consumable items in multi-platform games, provided that those items are also available as in-app purchases within the iOS version. This means that publishers should just ensure that content available for sale through Codashop can also be available for purchase using Apple’s in-app purchases.

Google’s payments policy also recognizes that developers can use alternative payment methods outside of an app. Within an app, users cannot be led to alternative payment methods for in-app purchases of digital goods and services distributed on Google Play, but publishers are free to communicate with users about alternative payment options outside of an app.

These policies may become more permissive in the future as more jurisdictions expressly legislate in favor of clarifying that other in-app payment methods can be used. Some countries and regions have already done so; for example, South Korea, the Netherlands, and the European Union.

In short, publishers that monetize using Codashop and do not communicate with users about this option inside the versions of their apps distributed through the Apple App Store and Google Play Store are compliant with Google and Apple’s policies.

| # Finance Guide Welcome to the Finance Documentation provided by Coda Payments. This document is intended to assist our Partners in business and financial departments in gaining a clear understanding of Coda Payments’ rate card, associated service fees, and tax considerations. We will also walk you through the essential steps involved in the reconciliation, invoicing, and settlement process, as well as the various payment channels available for collecting payments. # Taxes **Singapore Withholding Tax:** Coda Payments is a Singapore company, and in accordance with the Inland Revenue Authority of Singapore, “Payments for software or digitized goods that do not involve the transfer of the copyright rights embedded in the goods will be considered as payments for copyrighted articles and are not subject to withholding tax.”As such, Coda does not apply any withholding tax on its payouts to partners, regardless of which country they are based in. # Singapore GST For Partners addressed in Singapore: | | Transactions are processed by a payment channel for which Coda sends partner invoices for transaction processing | Transactions are processed by a payment channel for which the partner sends Coda invoices for content | | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Partner is GST registered | Coda will charge partners the specified percentage and per-transaction fee(s) for transaction processing, plus 9% GST on these fees, and will reduce its settlement payment to the partner accordingly. The partner will be able to claim back this GST from IRAS.Partners should charge 9% GST on sales to end users in Singapore and comply with [IRAS rules with respect to the display of pricing](https://www.iras.gov.sg/taxes/goods-services-tax-$gst$/basics-of-gst/invoicing-price-display-and-record-keeping/displaying-and-quoting-prices). | Publishers should include 9% GST on the value of their invoices to Coda and Coda will increase its settlement payment to the partner accordingly. | | Partner is not GST registered | Coda will charge partners the specified percentage and per-transaction fee(s) for transaction processing, plus 9% GST on these fees, and will reduce its settlement payment to the partner accordingly. The partner will be unable to claim back this GST from IRAS, so should consider GST registration | GST does not apply | # Sales Tax Charged to End Users Coda Payments (Coda) is required to determine, charge, and remit 9% GST to the appropriate tax authority on transactions processed in Singapore. In this case, Coda will deduct the GST amount from the settlement payment and remit it to the appropriate tax authority. You don’t need to calculate and send GST separately for purchases made by customers in Singapore. **Sales Tax:** Depending on the local tax law, Partners may be required to include sales tax in the price offered to customers for digital content purchases in some countries. If you offer content in tax-inclusive countries, the amount that we charge to customers will include the applicable taxes (i.e. when a partner’s charge request is submitted to Coda via API for Rp. 100.000, we will charge the customer Rp. 100.000, of which Rp. 9.910 will be deducted as sales tax (in the case of Indonesia as an illustration)) to be remitted to the appropriate tax authority by either the payment channel, Coda, or Partner. Currently, Coda supports the transmission of sales taxes to the responsible tax authority on the Partner’s behalf for selected channels. Please contact your corresponding Coda contact for more details. # Reconciliation, Invoicing, and Settlement There are four steps in the payment cycle that finance teams should understand when working with Coda: (1) transactions are processed during a particular month (the “Transaction Period”), and then (2) a sales report is generated by Coda (the “Sales Report” or “S.R.”) and sent by email to the partner, and then (3) an invoice (“the Invoice” or “Inv.”) is sent from Coda to the Partner or from the Partner to Coda, depending on the payment channel (as illustrated below), and then (4) Coda makes payment to the Partner (“Pay”). On the next page, you will find a table illustrating this flow and when each of these steps takes place. # Payment Cycle Flow | Transaction Structure | Who sends the invoice? | Payment Term | Month-1 | Month-2 | Month-3 | Month-4 | | -------------------------- | ---------------------- | ------------ | -------------------- | -------------------------------------------- | ------------- | ------------- | | Partners sell to Coda | Partner | 30 | “Transaction Period” |

Week 3: “Invoice”

Week 4: “Pay”

Week 3: “Invoice”

Week 4: “Pay”

| | | | | | 60 | “Transaction Period” | Week 3: “Invoice” | Week 4: “Pay” | | | | | 90 | “Transaction Period” | Week 3: “Invoice” | | Week 4: “Pay” | # Finance FAQs ***Why are invoices sent from Coda to the Partner for certain payment channels and from Partner to Coda for others?*** * When the Annex or E-annex for a payment channel indicates that sales made by Partners are to Coda, Partner agrees to sell to Coda content that is accessed by End Users at a discount. Partner will invoice Coda each settlement cycle for the Transaction Value of all Successful Transactions made during the month when transactions were processed less the agreed-upon discount. * When the Annex or E-annex for a payment channel indicates that sales made by the Partner are to End Users, Coda shall provide transaction-processing services to the Partner and invoice the Partner each settlement cycle for the fees described in the Annex or E-annex. ***Here are two examples to illustrate how the invoicing flow works:*** 1. **Scenario A: a payment channel where the Partner sends an invoice to Coda (i.e. where the Partner agrees to sell content to Coda at a discount).** Suppose a Partner processes transactions in the month of January. The Sales Report would be automatically generated by Coda and sent by email to the Partner on 1 February. For channels with a settlement period of 60 days, the Partner would then be responsible for sending an invoice to Coda’s finance team no later than the 25th of March. Provided the invoice is in order, the payment would then be sent by Coda to the Partner before 31 March. 2. **Scenario B: a payment channel where Coda sends an invoice to Partner (i.e. where Coda agrees to provide transaction-processing services to Partner.)** Suppose a partner processes transactions in the month of January. The Sales Report would be automatically generated by Coda and sent by email to the Partner on 1 February. For channels with a settlement period of 60 days, Coda would then be responsible for sending an invoice to the Partner’s finance team no later than the 25th of March. The payment would then be sent by Coda to the Partner before 31 March. ***How is the settlement process handled?*** \ We send transaction reports to the partner on the **2nd** of each month. By the **10th**, we provide invoices, purchase orders, and self-billing PDFs to the Partner as a summary of the net settlement amount for the previous month. The Partner is required to send us invoices for their content transactions by the 24th of each month. On the last working day of the month, we process the settlement and send a payment details notice summarizing the transactions. ***What’s the procedure for issuing an invoice?***\ We issue invoices for transactions that fall under the transaction processing structure. When a Partner sells content to Coda (under the sale of content structure), we issue a purchase order (PO). The Partner can then use the PO amounts to send an invoice to Coda for the content sold. ***When will we receive our settlement?***\ Settlements occur on the last working day of the month through telegraphic transfer/SWIFT. Depending on the processing times of the intermediary and beneficiary banks, it may take 1 to 5 working days for the funds to reach your bank account. ***Should tax be included in my invoice?***\ Yes, if the Partner is a GST-registered entity in Singapore. ***How can I check if I need to issue an invoice? / How do I verify my payment structure?***\ **Coda uses two transaction structures:** * Coda sends an invoice: When the Partner sells directly to end-users. Coda provides transaction processing services for these purchases via the Coda platform. * Coda sends a purchase order when the Partner sells content to Coda. Coda then resells this content to end-users or through affiliates or designated payment channel partners. ***Why wasn’t the settlement automatically credited to our account?***\ There might be an issue with the recipient bank. If Coda confirms the funds have been sent, we suggest contacting your bank directly for further investigation ***Can the settlement be made in a different currency (e.g., X currency)?*** \ Currently, settlements are processed only in USD. For special requests, please contact our Treasury team. ***Why haven’t I received my settlement yet?*** \ Settlements are made on the last working day of the month via telegraphic transfer/SWIFT. It may take 1-5 working days to reach your bank account. If you haven’t received it after 5 working days, we will check with our bank for any bounce-back issues. ***Is it possible to settle at any time?*** \ Currently, settlements are processed in monthly and mid-week cycles (T+15 and bi-weekly). For specific requests, please contact the GPT team for discussion. ***Random settlement discrepancy issues:*** 1. Amount discrepancies 2. Missing transactions Please report these to the Coda finance team at **. Finance will investigate the discrepancies. ***How long does it take to receive a response from the Coda Finance Team via email?***\ I’ve sent my invoice but haven’t received a reply. The Coda finance team will respond to invoice-related queries by the end of the month at the latest. ***Can I change the bank account where the settlement is made?*** \ For support regarding bank change requirements, please reach out to our customer success team at ****** ***Which of my accounts is being used for the settlement?*** \ Settlements are made to the bank account stated in the agreement. Any addendums or changes will refer to the latest information. ***What is my outstanding balance? / How do I check my balance?*** \ Please contact the Coda finance team at ** for all balance inquiries. ***Will Coda continue making monthly settlements before the Partner reaches their cap?*** \ No, settlements are processed only when the Partner reaches their cap. However, special requests from the Partner can be accommodated. ***Can the settlement report be sent to a new email address / Request email changes?***\ Yes, please reach out to our customer success team at ****** ***Random GST-related concerns:***\ Example: If a Partner registers for GST on March 1, 2024, should the March invoice be reissued? * If the invoice has already been settled, it cannot be reissued. * If the invoice has not been settled, it can be reissued. ***How do settlement caps change?*** \ The default settlement cap is USD 100 after the remittance fee. Specific caps can be set upon the Partner's request. ***Concerns about the payment structure / Change payment structure request***\ Changes are possible. please reach out to our customer success team at ****** ***FX rate used for settlement: Is there any website for reference?***\ Please contact the Coda finance team at ****** for FX source references.\

# Cut-off Dates The table below illustrates the timeline for transactions that occurred in January depending on Payment Channel's settlement period: | Payment channel's settlement period | Cut-off date for submitting invoice | Payment sent by Coda to Partner | | ----------------------------------- | ----------------------------------- | ------------------------------- | | 30 days | 24th February | End of February | | 60 days | 24th March | End of March | | 90 days | 24th April | End of April | Invoices received after the 25th of each month will be included in the subsequent month's payment schedule. # Preparing a Partner Invoice to Coda Here are some tips to ensure the invoice that you send to Coda is correct (in cases where the Partner is obligated to send an invoice to Coda): * The invoice should be prepared only after the Partner has reviewed the Sales Report sent by Coda and has verified that the data is correct. * The amount specified on the invoice shall be for the value of transactions processed during the Transaction Period, net of Coda’s fees. Taking Indonesia carrier billing as an example, if Rp. 1.000.000 was processed in a transaction month (exclusive of VAT) and Coda’s fee is 30%, so the amount that should be specified on the invoice is Rp. 700.000. * The Partner can use any format for the invoice desired, so long as it includes the following information: (1) the payment channel(s) for which the invoice applies, (2) the Transaction Period, and (3) the net amount. * A sample invoice can be found in [Appendix A](broken://pages/pWEQ0pDRKLBt9YIDEs3O). # Interpreting an Invoice from Coda to the Partner Here's a tip to ensure that you correctly interpret the invoice from Coda to the Partner (in cases where Coda is obligated to send an invoice to the Partner): * The amount specified on the invoice shall be for the value of Coda’s fees. Taking Indonesia bank transfers as an example, if Rp. 1.000.000 was processed in a transaction month and Coda’s fee is 10%, then the amount specified on the invoice will be Rp. 100.000. # Other Important Notes **Settlement currency:** Transactions are always processed in the country’s local currency (i.e. Indonesian Rupiah, Singapore Dollars, Malaysian Ringgit, Thai Baht, Philippine Peso, or New Taiwan Dollars). Payouts to partners are always made in USD at the exchange rate used by the bank (or non-bank payment service provider where applicable) when the exchange from local currency to USD is made, less the international transfer fee specified in the Partner’s agreement with Coda. **Deferment of payment:** To minimize the remittance fees that partners bear, if a payment is less than US$100, Coda will, *unless the partner instructs Coda otherwise in writing*, defer making it until the current month’s payment and deferred payments from prior months total US$100 or more. **Settlement bank account:** The payee bank account must be a corporate account in the name of the partner. Personal bank accounts will not be accepted. **Accessing transaction data:** Finance contacts at Partners can access transaction records in two ways: * **Automatically via Email/SFTP/Webhook:** Coda will send the sales report (daily/weekly/monthly) basis and deliver this to one of the options available now. For more detailed information, please refer to this [Transaction Report Delivery Option](broken://spaces/SEdQy23klcHCaJcfBCmP) document.
* **Manually (i.e. “self-serve”):** Transaction data can be manually generated by any user that has Finance access in the [Publisher Portal](https://portal.codapayments.com/) anytime by visiting the **Transactions** tab. * The user can select the filters such as payment channels and date range as desired * Then press “Show results” * Finally, the user can click “Export CSV” or “Email CSV” to extract the transaction data in CSV format. For the Email CSV function, if you don’t receive the CSV within a few minutes, please check your spam/junk folder. * This process is illustrated below:

# Appendix A: Sample Invoice from Partner to Coda

# Payment Channel Our supported payment channels include Carrier Billing, Bank Transfers, Debit/Credit Cards, Convenience Store Payments, Cash Cards/Vouchers, and E-Wallets. We support these payment methods based on regional & product availability. ## Payment Types ### Carrier Billing Carrier Billing allows customers to charge purchases to their mobile phone account. The payment is authenticated through an SMS sent to the customer's phone and is processed immediately. ### Bank Transfer Customers can pay by executing a bank transfer at an ATM, bank counter, or via online banking. Merchants receive a unique payment code, which the customer enters as part of the bank transfer details. ### Card Payments This method allows customers to complete payments using their credit or debit card. Customers are redirected to the partner's payment page to input their card details and complete the payment. ### Convenience Store Payments This method allows customers to complete payments at a convenience store. Customers receive a unique payment code from Codapay, which they present at the store. ### Voucher (Cash Card) Customers purchase a voucher from an issuer and enter it in Codapay's payment window to purchase digital content. ### E-Wallet E-wallets allow customers to have a digital payment account and top-up balance. Codapay supports many types of e-wallets for purchases. ## Payment Channel List {% @gitbook-payment-search/gitbook-payment-search %} ## Payment List by Product

		Cover image
CODAPAY	Payment Channel Detail	image.png
CODASHOP	Payment Channel Detail	image.png
WEBSTORE	Payment Channel Detail	Untitled design (34).png

# Overview Get ready to discover why Codapay is the absolute game-changer. ## Easily accept payments worldwide on their own websites through a simple and easy-to-use API Built with over a decade of proven innovation and implementation, our user-friendly integration allows partners to process payments with best-in-class security and robust compliance practices. With seamless user experience, comprehensive data analytics, and global coverage, Codapay empowers businesses to expand their reach and optimize their payment processes. [**Get started now ->**](/codapay/getting-started) *** ### Codapay's Integration types


Hosted Payment Page `~10 mins`・Quickest Directs the customer to a secure, hosted payment page provided by Coda. Learn more ->	Screenshot 2024-05-30 at 12.18.53.png
Backend API `~60 mins`・Custom Integrate directly with Coda’s backend services, offering more control and customization over the payment process. Learn more ->	backend-api @1x.png

Hosted Payment Page
~10 mins・Quickest

Directs the customer to a secure, hosted payment page provided by Coda.

Learn more ->

Screenshot 2024-05-30 at 12.18.53.png

Backend API
~60 mins・Custom

Integrate directly with Coda’s backend services, offering more control and customization over the payment process.

Learn more ->

backend-api @1x.png

{% hint style="info" %} [**See all Codapay's Integration types here**](/codapay/integration-guides/choosing-the-right-type-of-integration#comparison-between-available-integrations) {% endhint %} *** ### Why Codapay?


🌍 Global Reach	We offer 300+ payment methods, available in 65 countries, supporting 60 currencies, and speaking 80 languages.
🏪 Convenience	Experience unmatched customization and advanced features like tokenized charging and single-click payments.
✅ Stay Compliant	Our team is experienced, and our systems robust, ensuring compliance with all laws and regulations in every market we serve.
📦 Complete Package	Save on transaction costs and FX with Coda’s comprehensive end-to-end Payout solution.
🪨 Rock-solid Reliability	We've got your back with 99.95%+ uptime with 24/7 monitoring and rapid response.
📈 Smart Insights	Gain exclusive access to our always-on analysis through the Publisher Portal.

*** # Getting started Quickly begin testing a Codapay integration. ## What you'll find This section will cover all the steps required to quickly begin testing with one of our popular integration types, which includes: * [Set up payments](/codapay/getting-started/set-up-payments) * [Test the Hosted Payment Page API](/codapay/getting-started/test-hosted-payment-page-api) Alternatively, you can test the Hosted Payment Page flow directly on our Coda Portal by following the steps in the ["Sandbox Testing"](https://portal.codapayments.com/integration/codapay/sandbox-testing) section. *** ## Set up payments overview Go to **Coda Portal** to complete these 3 steps:


Step 1 Create Title	Create a title that you will test an integration with.
Step 2 Set up your landing URL and the default callback URL	Configure the URLs for your selected title.
Step 3 Retrieve your API Key	Get your API Key to start testing.

Step 1

Create Title

Create a title that you will test an integration with.

Step 2

Set up your landing URL and the default callback URL

Configure the URLs for your selected title.

Step 3

Retrieve your API Key

Get your API Key to start testing.

*** ## Test Hosted Payment Page API overview


Step 1 Initiate the payment request	Start a payment request to get a response.
Step 2 Redirect your user to the payment page to complete payment	Complete the payment request.
Step 3 Receive the successful payment notification	Receive then respond with a success message.
Step 4 Check the status of a successful payment using the InquiryPaymentResult API call

# Set up payments Activate a title, countries, and payment methods on Coda's Publisher Portal to start accepting payments. {% hint style="info" %} This quickstart assumes that a Publisher Portal account was created and set up with business details, e-agreement signing, and KYC verification completed. If you need assistance completing these steps, please contact your account manager or email {% endhint %} ## What you'll learn * How to activate title, countries, and payment methods * Start accepting payments for a specific title, in specific countries, using specific payment methods ## Step 1: Create Title 1. Log in to your Publisher Portal account and navigate to “Titles”

2. Click on “Create Title” 3. Enter the title information or import them from the Google Play/App Store, select the content type.

4. The title will be auto-created with Codapay enabled. If not, select Service Type as Codapay *** ## Step 2: Set up your landing URL and the default callback URL 1. On your publisher portal account, navigate to **Products** -> **Codapay** -> **Select the Title -> Sandbox Configuration**

2. Select the country you want to set up, or use Bulk Edit configuration to edit multiple countries.

3. Click “Edit” -> Merchant & URLs configuration: * **Complete Notification URL:** This is where Codapay will notify you of a successful payment. * **Complete Landing Page URL:** This is the default URL to which your user will be redirected after the completion of the transaction. If you pass the `returnURL` as part of your initial API call, it will override this value.

4. After inputting the URLs, click "Save" *** ## Step 3: Retrieve your API Key from the Publisher Portal 1. On your Publisher Portal account, navigate to **Products -> Codapay -> API Keys** New merchants: You will see your Global API key (v2 API), as well as 1 Project ID for each title. Existing merchants: You will see multiple API keys that are unique for each title and country (v1 API) For more details, please see [API versions](https://coda-payments.gitbook.io/coda-public-technical-documentation/codapay/integration-guides/codapay-api-versions) 2. Optional: You can set up IP Address whitelisting for each title and country.

*** ## Next steps: * [Test Hosted Payment Page API](https://coda-payments.gitbook.io/coda-public-technical-documentation/codapay/getting-started/test-hosted-payment-page-api) # Test Hosted Payment Page API After you set up accepting payments in Coda Portal, you can quickly test a payment flow for a payment method. {% hint style="info" %} This tutorial only shows how to test for a specific payment method. If you are interested in our Payment Selection Page, [you can follow this guide](/codapay/hosted-payment-page-integration/payment-channel-integration-options). {% endhint %}

## What you'll learn * Initiating a payment request. * What your customer will experience upon payment request. * What your customer will experience upon a successful payment notification. This tutorial assumes you have a developer set up and tools to make API calls (Postman, ...). If that is not the case, you can also test the flow through our Coda Portal ["Sandbox Testing"](https://portal.codapayments.com/integration/codapay/sandbox-testing) section. *** ## Step 1: Initiate the payment request 1. Initiate the payment request by calling the `/init` endpoint to collect your **payment transaction ID**. Use the curl below and populate it with:

Parameter	Placeholder text	Description
country	`[SELECTED_COUNTRY]`	The country that you want to test. See the full list here.
currency	`[SELECTED_CURRENCY]`	The currency code that you want to use. See the full list here.
payType	`[SELECTED_PAYMENT_CHANNEL_ID]`	The payment method that you want to use. See the full list here.
apiKey	`[API_KEY]`	Get your APIKey from Coda Portal.
projectId	`[PROJECT_ID]`	*This field is only needed for v2.0 API Get the projectId for each title from Coda Portal.

{% hint style="warning" %} Make sure that the price is within transaction limits for the payment channel you’ve selected by [checking transaction limits here](/codapay/integration-guides/price-limits). {% endhint %} {% hint style="info" %} Other parameters have been populated with dummy data for testing purposes below. They can be changed and populated properly as part of your integration. More details on the parameters of the `/init` endpoint [can be found here](/codapay/hosted-payment-page-integration).\ \ Codapay offers two API versions - v1.0 and v2.0, with v2.0 being an upgraded version. **If you are a new merchant, please use v2.0.** More details [can be found here](/codapay/integration-guides/codapay-api-versions). {% endhint %} {% tabs %} {% tab title="v2.0 Request" %}

curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment/init.json' \
--header 'Content-Type: application/json' \
--data '{
    "initRequest": {
        "country": [SELECTED_COUNTRY],
        "payType": [SELECTED_PAYMENT_CHANNEL_ID],
        "apiKey": [API_KEY],
        "projectId": [PROJECT_ID] //This field is only needed for v2.0 API
        "orderId": "12321312321314",
        "currency": [SELECTED_CURRENCY],
        "items": [
            {
                "code": "1",
                "price": 50.00,
                "name": "Test Item"
            }
        ],
        "profile": {
            "entry": [
                {
                    "key": "user_id",
                    "value": "105"
                }
            ]
        }
    }
}

{% endtab %} {% tab title="v1.0 Request" %} ```json curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v1.0/Payment/init.json' \ --header 'Content-Type: application/json' \ --data '{ "initRequest": { "country": [SELECTED_COUNTRY], "payType": [SELECTED_PAYMENT_CHANNEL_ID], "apiKey": [COUNTRY_API_KEY], "orderId": "12321312321314", "currency": [SELECTED_CURRENCY], "items": [ { "code": "1", "price": 50.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } } ``` {% endtab %} {% endtabs %} Below is an example using a dummy sandbox API Key for **Singapore**, with **Singapore Dollar (SGD)** as a currency and **Card Payments** as a payment method. {% tabs %} {% tab title="v2.0 Request" %}

curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment/init.json' \
--header 'Content-Type: application/json' \
--data '{
    "initRequest": {
        "country": 702,
        "payType": 427,
        "apiKey": "test_32774abe1cd7d8bae650ea48265e",
        "projectId": 21 //This field is only needed for v2.0 API
        "orderId": "12321312321314",
        "currency": 702,
        "items": [
            {
                "code": "1",
                "price": 50.00,
                "name": "Test Item"
            }
        ],
        "profile": {
            "entry": [
                {
                    "key": "user_id",
                    "value": "105"
                }
            ]
        }
    }
}'

{% endtab %} {% tab title="v1.0 Request" %} ```json curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v1.0/Payment/init.json' \ --header 'Content-Type: application/json' \ --data '{ "initRequest": { "country": 702, "payType": 427, "apiKey": "32774abe1cd7d8bae650ea48265e", "orderId": "12321312321314", "currency": 702, "items": [ { "code": "1", "price": 50.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } }' ``` {% endtab %} {% tab title="Response" %} ```json { "initResult": { "resultCode": 0, "txnId": 7122167282516076304 } } ``` {% endtab %} {% endtabs %} *** ## Step 2: Redirect your user to the payment page to complete payment 1. Use the received `txnId` from **Step 1** to redirect your user to the following URL: {% hint style="info" %} [Click here to see all the available parameters to pass in the URL.](/codapay/hosted-payment-page-integration/display-the-hosted-payment-page) {% endhint %} {% tabs %} {% tab title="🖥️ Desktop" %}

https://sandbox.codapayments.com/airtime/begin?type=3&txn_id=[txnId]

{% endtab %} {% tab title="📱 Mobile" %}

https://sandbox.codapayments.com/airtime/begin?type=3&txn_id=[txnId]&browser_type=mobile-web

{% endtab %} {% endtabs %} Below is an example of what it would look like for the transaction initiated above for **Card Payments** in **Singapore**: {% tabs %} {% tab title="🖥️ Desktop" %}

https://sandbox.codapayments.com/airtime/begin?type=3&txn_id=7122167282516076304

{% endtab %} {% tab title="📱 Mobile" %}

https://sandbox.codapayments.com/airtime/begin?type=3&txn_id=7122167282516076304&browser_type=mobile-web

{% endtab %} {% endtabs %} 2. In the sandbox environment, you can follow the testing instructions [provided here to complete the payment](broken://spaces/YHHTIo7U3NRvUwPKNG0G/pages/jaFqkOEJv6NkI7vKsHzd). {% hint style="info" %} Complete a test transaction with **Card Payments** in **Singapore** and use the following test card below. {% endhint %}

Card number	Expiry date	CVC
`4242 4242 4242 4242`	`01/35`	`123`

{% hint style="warning" %} **Note:** On the sandbox environment, the payment might take a few minutes to complete. {% endhint %} *** ## Step 3: Receive the successful payment notification 1. You will receive a notification on the Complete Notification URL, including the following fields as query parameters:

Parameters	Description
TxnId	Coda transaction ID
OrderId	OrderId passed by you in the init request
ResultCode	Payment status (e.g. success = 0)
TotalPrice	Total price paid by the user for the transaction
PaymentType	Payment Channel ID chosen by the user
Checksum	A checksum to verify that messages have not been altered

2. Respond to this notification with a success message `ResultCode=0` or a failure message (including an appropriate error code). {% hint style="info" %} If you want to try receiving an error response, simply replace the error code digit with any of the available error codes, [which you can access here.](/codapay/error-codes) {% endhint %} *** ## Step 4: Check the status of a successful payment using the InquiryPaymentResult API call Use the InquiryPaymentResult API call below to inquire about the payment status of your transaction. {% hint style="info" %} [Click here to see all the available parameters.](/codapay/hosted-payment-page-integration/check-a-transaction-status) {% endhint %} {% tabs %} {% tab title="v2.0 Request" %} ```json curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment/inquiryPaymentResult.json' \ --header 'Content-Type: application/json' \ --data '{ "inquiryPaymentRequest": { "apiKey" : "test_32774abe1cd7d8bae650ea48265e", "country": 702 //This field is only needed for v2.0 API "projectId" : 21 //This field is only needed for v2.0 API "txnId" : "7144594637002072212", "needStatusFinal": "true" } }' ``` {% endtab %} {% tab title="v1.0 Request" %} ```json curl --location 'https://sandbox.codapayments.com/airtime/api/restful/v1.0/Payment/inquiryPaymentResult.json' \ --header 'Content-Type: application/json' \ --data '{ "inquiryPaymentRequest": { "apiKey" : "32774abe1cd7d8bae650ea48265e", "txnId" : "7144594637002072212", "needStatusFinal": "true" } }' ``` {% endtab %} {% tab title="Response" %} ```json { "paymentResult": { "orderId": 12321312321314, "profile": { "entry": [ { "key": "PaymentType", "value": 427 }, { "key": "isStatusFinal", "value": true }, { "key": "status", "value": "success" } ] }, "resultCode": 0, "resultDesc": "", "totalPrice": 50, "txnId": 7144594637002072212 } } ``` {% endtab %} {% endtabs %} ## Next steps * Dive deeper into Payment Page API to understand more about the [Hosted Payment Page](/codapay/hosted-payment-page-integration) and [Payment Channel Selection Page](/codapay/hosted-payment-page-integration/payment-channel-integration-options) offering. * Dive deeper into our [Backend API](/codapay/direct-api-integration) offering. [^1]: Replace the txnId response and copy then paste the complete URL. # Integration Guides In this section you will find guides on: * Choosing the right type of integration * An integration checklist to ensure you cover everything needed during integration * Configuring and testing payment channels * Brand Guidelines # Choosing the right type of integration When integrating a payment gateway into your system, selecting the appropriate integration method is crucial for ensuring a smooth and efficient transaction process. This guide will help you understand the available integration types, their use cases, and the criteria for making the best decision for your business needs. The three primary integration types are: 1. Hosted Payment Page 2. Direct API 3. Hosted Component (Coming Soon)

Hosted Payment Page

The Hosted Payment Page method involves directing the customer to a secure, hosted payment page provided by Coda. This page is responsible for collecting payment information and processing transactions. **Advantages** * Simplifies PCI compliance and handling of PII data since sensitive payment data is handled by Coda. * Quick and easy to implement, reducing development time. * Supports various devices, including desktop browsers, mobile browsers, and in-app web **Criteria for Use** * You prefer a simple and quick integration with minimal technical overhead. * You need to support multiple payment channels without extensive development. * You want to offload PCI compliance responsibilities to Coda.

Direct API

The Direct API method allows you to integrate directly with Coda’s backend services, offering more control and customization over the payment process **Advantages** * Full control over the user interface and payment flow, enabling a customized payment experience. * Direct communication with Coda’s services allows for advanced features and integration. * Suitable for businesses needing a tailored payment experience. **Criteria for Use** * You require a highly customized payment process tailored to your business needs. * Your business can handle the complexities of PCI compliance. * You have the technical resources to implement and maintain the integration.

Hosted Component

The Hosted Component integration provides a prebuilt UI component that you can embed directly into your existing checkout flow. This method offers a balance between ease of implementation and a seamless user experience, as Coda is not visible to the end user during the purchase process. **Advantages** * Reduced Development Effort: Utilize a pre-built UI component to minimize the technical resources required for implementation. * Seamless Brand Experience: Maintain full control over the user interface visibility, keeping the Coda branding hidden from the customer. **Criteria for Use** * You want an embedded experience: You prefer to keep the customer on your own site or app during the entire payment process. * You have technical resources: You possess the necessary front-end development resources to embed and maintain the UI component.

### Making the Decision To decide which integration type suits your needs, consider the following criteria: * **Technical Resource Availability:** If your team has limited development resources or expertise, the Hosted Payment Page is the better option due to its simplicity and ease of implementation. * **Customization Needs:** If you need a highly customized user experience and have the technical capability to manage PII data, the Direct API provides the flexibility you require. * **Compliance Requirements:** For businesses looking to minimize their PCI compliance burden, the Hosted Payment Page offers a significant advantage by offloading sensitive data handling to Coda. * **Speed to Market:** If you need to launch quickly, the Hosted Payment Page allows for faster implementation and leverages Coda’s optimized and user-friendly interface. * **Performance:** The Hosted Payment Page benefits from Coda's years of optimization, ensuring a high-performance, reliable payment process that can enhance user satisfaction. By understanding the features and requirements of each integration type, you can make an informed decision that aligns with your business goals, technical capabilities, and timeline. *** ### Comparison between available integrations

...	Hosted Payment Page	Direct API	Hosted Component

Customer interface	A page designed and hosted by Coda on which a customer can initiate a purchase for onechannel. Coda can also customise this with publisher branding. Optional: Payment* Channel Selection Page A page designed and hosted by Coda on which a customer can select from a variety of channels.	A set of APIs to integrate Coda’s payment channels into your own UI.	Prebuilt UI component to embed in your checkout flow.
Who presents payment Information to end user?	Coda	Publisher	Publisher
Is Coda visible in purchase flow?	✅	❌	❌
Typical conversion rate	High	Variable	Variable
Integration complexity	Low	High	High
What payment methods are available?	All	Selected	Selected
How to get started?	Hosted Payment Page guide -> Payment Channel Selection Page guide ->	Follow this guide ->	Follow this guide ->

# Codapay API Versions Codapay offers two versions of its API: v1.0 and v2.0. While both versions are fully supported, **v2.0 is the recommended version for all new integrations**. It provides several improvements designed to simplify integration, improve maintainability, and enable access to newer features such as card saving. #### Why v2.0? **v2.0** introduces the concept of a **Global API Key**, replacing the need for multiple API keys across countries and titles. This reduces complexity and streamlines integration and credential management. Additionally, a **Project ID** field has been added to help distinguish different products or titles, enabling better transaction segmentation and reporting. Some advanced features, including **saved card functionality**, are only available when using v2.0 API keys. #### Key Differences: v1.0 vs v2.0 | Feature | v1.0 | v2.0 | | ------------------------ | ------------------------------------- | ------------------------------- | | API Key | One key per title-country combination | One global API key per merchant | | Project ID | Not required | **Mandatory** for all requests | | Saved Card Support | Not supported | Supported | | Endpoint URL | `/v1.0/Payment` | `/v2.0/Payment` | | Request Payload Contract | No `projectId` | `projectId` is required | ### Migrating from v1.0 to v2.0 If you are already integrated with **Codapay API v1.0**, we recommend upgrading to **v2.0** to benefit from a simplified integration and new features. The upgrade process is lightweight and compatible with your existing transaction logic. #### Migration Steps 1. **Request a v2.0 API Key:** Contact your Codapay integration support to obtain your global API key and project ID(s). 2. **Update API Endpoint:** Switch your base URLs from `/v1.0/` to `/v2.0/` for both sandbox and production environments: * **Sandbox:** `https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment` * **Production:** `https://airtime.codapayments.com/airtime/api/restful/v2.0/Payment` 3. **Add the** `projectId` **Field:** Update your `initRequest` payload to include the `projectId`, which is **mandatory** in v2.0. ```json "initRequest": { "projectId": "YOUR_PROJECT_ID", ... } ``` 4. **Retain Existing Fields:** All other request fields and flow remain unchanged. You can continue using the same logic for `country`, `payType`, `currency`, `items`, and `profile`. 5. **Test and Go Live:** Validate your integration against the v2.0 sandbox environment. Once verified, switch to the production endpoint and begin using the updated flow. #### Sample Comparison **v1.0 Sample** ```json { "initRequest": { "country": 158, "payType": 82, "apiKey": "e944d44f065eade8157737385a094a", "orderId": "12321312321314", "currency": 901, "items": [ { "code": "1", "price": 1000.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } } ``` **v2.0 Sample** ```json { "initRequest": { "country": 158, "payType": 82, "apiKey": "e944d44f065eade8157737385a094a", "projectId": 21, //This field is only needed for v2.0 API "orderId": "12321312321314", "currency": 901, "items": [ { "code": "1", "price": 1000.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } } ``` # Upgrade to Codapay API v2 and Unlock Saved Card Support Codapay API v2 makes your integration simpler and more powerful — and it’s the only version that supports **saved card functionality** for returning users. Here’s how to **upgrade to v2 + enable saved cards** in just a few easy steps. ### Why Upgrade? * **One Global API Key** per merchant — no more country-title key management * **Project ID** support for easier transaction tracking across games or services * **Card Saving Support** for faster checkout and higher conversion * Fully compatible with your existing v1 setup 📘 [See API v2 Overview](/codapay/integration-guides/codapay-api-versions) | 💳 [See Saved Card Integration Guide](/codapay/hosted-payment-page-integration/saving-card-details) ### Migration + Enablement Steps #### 1. **Request v2 Access** Contact your Codapay integration support or account manager to: * Get your **v2.0 API key** and **project ID** * Ask to **enable saved card functionality** (optional, but recommended) #### 2. **Update Your Integration** * Change the base endpoint from `/v1.0/Payment` to `/v2.0/Payment` * Add `projectId` in the `initRequest` payload\ Example: ```json "projectId": "YOUR_PROJECT_ID" ``` * Keep everything else the same: `country`, `payType`, `items`, `profile`, etc. #### 3. **Enable Saved Cards** If you opted to enable saved card functionality: * Pass these extra fields in your request: ```json "enableSavePaymentMethod": true, "displaySavedPaymentMethodList": true, "userInitiated": true ``` * Include a unique `partnerShopperId` in the `shopper` object to link cards to users. 📘 [Full Field List + Shopper Mapping](/codapay/hosted-payment-page-integration/saving-card-details#integration-overview) #### 4. **Test in Sandbox** Use your v2 key and projectId in the sandbox URL: ```url https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment ``` Try: * A first-time card payment with saving enabled * A returning user selecting a saved card [📘 View Request + Response Examples](/codapay/hosted-payment-page-integration/saving-card-details#scenarios-and-examples) #### 5. **Go Live** Once confirmed, update your production integration using the v2.0 key and projectId: ```url https://airtime.codapayments.com/airtime/api/restful/v2.0/Payment ``` You're now live on v2 — with saved cards enabled 🎉 # Integration Checklist Use this checklist to ensure a smooth and complete integration of Codapay into your system. Following these steps will help you avoid common pitfalls and ensure that all necessary configurations are in place for a successful launch.

### 1. Review Documentation and Plan Integration #### Review Integration Types * Understand the differences between Hosted Payment Page and Backend API integrations. * Decide which integration type suits your business needs (refer to "[Choosing the Right Type of Integration](/codapay/integration-guides/choosing-the-right-type-of-integration)" for guidance). * Decide which Codapay API version to use (refer to "[Codapay API Versions](/codapay/integration-guides/codapay-api-versions)" for guidance). #### Technical Resource Availability * Ensure you have the necessary technical resources available to implement and maintain the chosen integration type. ### 2. Setup and Configuration Follow the [Getting Started](/codapay/getting-started) guide for detailed steps on setting up API credentials, configuring redirect URLs, activating payment channels, and environment configuration. ### 3. Integration Refer to the [Getting Started](/codapay/getting-started) guide and the rest of the API documentation for detailed instructions on implementing the [Hosted Payment Page](/codapay/hosted-payment-page-integration) and [Backend API](/codapay/direct-api-integration). ### 4. Testing #### Merchant Account Status * Verify that your merchant account is in "Testing" status during sandbox testing. * Upon successful completion of sandbox tests, request Codapay Support Team to change your account status to "Active". #### Sandbox Testing * Conduct thorough testing in Coda’s Sandbox Environment. * Test all possible scenarios, including successful transactions, failures, and edge cases. ### 5. Pre-Launch Preparation #### E-Annex Approval * Inform Coda’s Partner Business Team once testing is complete in the sandbox environment. * Complete the payment channel E-Annex approval process. #### Production Configuration * Configure the redirect and callback URLs for the production environment * Please inform the Codapay Support Team once you have completed the configuration. Additionally, kindly provide the following information: - [x] The request currency (USD or local currency) - [x] The request payType (0 or payment channel ID) - [x] Are you using [InquiryPaymentResult](/codapay/hosted-payment-page-integration/check-a-transaction-status) endpoint? - [x] Integration methods (Webview / External Browser / PC Client) #### Production Environment Testing * After activating E-Annex, conduct tests in the production environment. * Ensure the payments function correctly with real transactions * If you require assistance from Coda for testing, please share the following details: * APK **or** Top-up Website URL * Game account ID **or** app login ID and password * Denomination (Lowest available denomination) {% hint style="info" %} Codapay Support Team operates from **9AM to 6PM SGT, Monday - Friday**. Please provide ***1 business day prior notice*** to allocate resources and manpower accordingly. {% endhint %} #### Final Checks * Ensure all front-end implementations adhere to Coda’s Brand Guidelines. ### 6. Launch Contact Codapay Support Team to confirm all integrated channels are ready for launch, including those requiring pre-approval and inform them of your launch date so that they can help monitor. ### Who to contact for help

Team	Email	Responsibilities
Technical Support Team (24/7)	partnersupport@coda.co	Transaction check Refund request Payment channel outage Failed to login Publisher Portal
Partner Business Team	publisher_team@coda.co	Transaction conversation rate New channels available Financial inquiries Create new Publisher Portal account Issues related with VAT
Codapay Support Team	codapay_integration@coda.co	Production Testing request Resetting Publisher Portal account FTP/S or SFTP report Renotify Codapay transaction Error codes not listed in this document

# Testing Guide Testing your integration and payment channels in the Sandbox environment is a critical step to ensure everything functions correctly before going live. This guide provides an overview of the testing resources available to assist you. ### Configure the Sandbox Environment Refer to the [Getting Started](/codapay/getting-started) guide to learn to obtain the Sandbox credentials to set up and configure your testing environment. ### Channel Specific Testing Each payment channel has specific testing requirements. Refer to the [Payment Channel Testing Instructions](/codapay/integration-guides/testing-guide/payment-channel-testing-instructions) for detailed steps. Some of the payment channel require using a simulator to complete transactions. Refer to the [Payment Simulator Guide](/codapay/integration-guides/testing-guide/sandbox-testing-guide) for further help. ### Resources and Support **Documentation and Guides** * [Payment Channel Testing Instructions](/codapay/integration-guides/testing-guide/payment-channel-testing-instructions): Detailed steps for testing each payment channel. * [Simulator Guide](/codapay/integration-guides/testing-guide/sandbox-testing-guide): Instructions for setting up and using the payment simulator. * [Getting Started](/codapay/getting-started) guide: Comprehensive setup instructions for API credentials, redirect URLs, payment channel activation, and environment configuration and flow testing. **Support Contacts:** * **Technical Support Team:** * **Partner Business Team:** * **Codapay Support Team:** # Payment Channel Testing Instructions Here you will find test cards, mobile numbers and wallet accounts to test your transactions in Sandbox {% hint style="success" %} For testing some of the payment channels, you will need to use the payment simulator available on our publisher portal, for more information visit [**here**](https://coda-payments.gitbook.io/coda-private-technical-documentation/codapay/integration-guides/sandbox-environment/new-payment-simulator-guide). {% endhint %}

Country	Payment channel name	Testing instructions
Argentina	Card Payments Argentina	Success Use case: 4000 0003 2000 0021 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Australia	Google Pay Apple Pay Australia	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Australia	PayPal Australia	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Austria	Google Pay Apple Pay Austria	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Austria	EPS	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Austria	Card Payments Austria	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Bahrain	Benefit	Use the following phone number to initiate the transaction: Phone: 31000000 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Bangladesh	Robi Airtel	Not Available
Bangladesh	Nagad	Not Available
Belgium	Google Pay Apple Pay Belgium	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Belgium	Bancontact Mobile	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Belgium	Card Payments Belgium	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Belgium	PayPal Belgium	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Bolivia	Card Payments Bolivia	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Brazil	Boleto	Use the following CPF to initiate the transaction: Birth Date : Any valid date CPF: 70383053102 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Brazil	Bank transfer Brazil	Use the following CPF and phone number to initiate the transaction: CPF: 70383053102 Phone: 11961234567 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Brazil	Pix	Use the following CPF to initiate the transaction: CPF: 70383053102 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Brazil	PicPay	Use the following CPF and phone number to initiate the transaction: CPF: 70383053102 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Brazil	Card Payments Brazil	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Brazil	PayPal Brazil	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Cambodia	Wing	This payment channel can be tested using the test credentials below: Account: 1122334455667 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Cambodia	PiPay	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Cambodia	Paygo	This payment channel can be tested using the test credentials below: Phone: 85511111111 OTP: 00000
Cambodia	Bakong (KHQR)	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Cambodia	Card Payments Cambodia	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Canada	Card Payments Canada	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Canada	Google Pay Apple Pay Canada	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Canada	PayPal Canada	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Chile	Card Payments Chile	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Chile	PayPal Chile	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Colombia	Bank Transfers Colombia	Use the following DNI to initiate the transaction: DNI: 1122334455667 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Colombia	Card Payments Colombia	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Colombia	DaviPlata	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Colombia	Nequi	Use the following phone number to initiate the transaction: Phone: 3198881271 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Colombia	Google Pay / Apple Pay Colombia	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Czech Republic	Google Pay Apple Pay Czech Republic	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Czech Republic	Card Payments Czech Republic	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Czech Republic	Paypal Czech Republic	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Denmark	Google Pay Apple Pay Denmark	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Denmark	Mobilepay	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Denmark	Card Payments Denmark	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Denmark	PayPal Denmark	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Ecuador	Card Payments Ecuador	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Ecuador	PayPal Ecuador	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Egypt	Vodafone Cash	Use the following phone number to initiate the transaction: Phone: 1010101010 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Egypt	Orange Money	Use the following phone number to initiate the transaction: Phone: 1200663741 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Egypt	Masary Aman Momken	Use the following phone number to initiate the transaction: Phone: 201010101010 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Egypt	Card Payments Egypt	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Egypt	Fawry	Use the following phone number to initiate the transaction: Phone: 1000000200 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Egypt	PayPal Egypt	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
France	Google Pay Apple Pay France	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
France	Card Payments France	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
France	PayPal France	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Finland	PayPal Finland	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Finland	Card Payments Finland	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Germany	Google Pay Apple Pay Germany	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Germany	Card Payments Germany	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Germany	Paypal Germany	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Germany	PaysafeCard Germany	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Greece	PayPal Greece	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Greece	Card Payments Greece	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Hong Kong	Alipay Hong Kong	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Hong Kong	WeChat Pay Hong Kong	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Hong Kong	FPS	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Hong Kong	Card Payments Hong Kong	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Hong Kong	Google Pay Apple Pay Hong Kong	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Hong Kong	PayPal Hong Kong	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Hungary	Google Pay Apple Pay Hungary	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Hungary	Card Payments Hungary	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Hungary	PayPal Hungary	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
India	UPI	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Indonesia	Tri Indonesia	This payment channel can be tested using the test credentials below: Phone: 89507209582 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	XL	This payment channel can be tested using the test credentials below: Phone: 85960557109 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	Indosat	Use the following phone number to initiate the transaction: Phone: 85779160178 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	Telkomsel	Use the following phone number and OTP to initiate the transaction: Phone: 81212857477 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	Bank Transfers Indonesia	After initiating the transaction, 1. fill in email address with a valid format, and choose the bank 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Indonesia	Alfamart	After initiating the transaction, 1. fill in email address with a valid format (first name + last name) 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Indonesia	Indomaret	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Indonesia	QRIS	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	GOPAY	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	OVO	This payment channel can be tested using the test credentials below: Phone: 81212857477 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	DANA	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Indonesia	LinkAja	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Indonesia	ShopeePay Indonesia	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Indonesia	DOKU Wallet	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Indonesia	Card payments Indonesia	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Indonesia	PayPal Indonesia	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Ireland	PayPal Ireland	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Ireland	Card Payments Ireland	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Italy	Google Pay Apple Pay Italy	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Italy	Card Payments Italy	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Italy	PayPal Italy	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Japan	Card Payments Japan	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Japan	Google Pay Apple Pay Japan	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Japan	PayPay	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Japan	PayPal Japan	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Kazakhstan	Card Payments Kazakhstan	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Kenya	M-PESA	Use the following phone number to initiate the transaction: Phone: 254700000000 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Kuwait	KNET & Card Payments Kuwait	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Laos	Lao Telecom	This payment channel can be tested using the test credentials below: Phone: 2058408260 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Laos	Card Payments Laos	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Malaysia	Digi	Use the following phone number to initiate the transaction: Phone: 1126325994 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Malaysia	Celcom	Use the following phone number to initiate the transaction: Phone: 1126325994 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Malaysia	U Mobile	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Malaysia	Maxis	Use the following phone number to initiate the transaction: Phone: 1126325994 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Malaysia	MAE	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Malaysia	Boost	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Malaysia	Touch-NGo	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Malaysia	ShopeePay Malaysia	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Malaysia	GrabPay Malaysia	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Malaysia	Card Payments Malaysia	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Malaysia	Google Pay Apple Pay Malaysia	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Mexico	Oxxo Pay	After initiating the transaction and pressing on the "Continue" button, a new simulator page will open on a new tab Choose the desired transaction status to simulate
Mexico	OXXO	Use the following RFC number to initiate the transaction: RFC: 1122334455667 fill in email address and name (first name + last name) with a valid format After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Mexico	PaysafeCard Mexico	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Mexico	Bank Transfer Mexico	Use the following RFC number to initiate the transaction: RFC: 1122334455667 fill in email address and name (first name + last name) with a valid format After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Mexico	Todito Cash	Not Available
Mexico	Mercado Pago MX	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Mexico	Card Payments Mexico	After initiating, enter the following information and press continue: - Name: Any name - Email: Any email address - Phone number: 5512345678 You will be redirect to a page where you can enter your card details: - Name: Any name - Card Number: 4242424242424242 for successful transaction and 4000000000000002 for declined - Expiry date: any valid date - CVC: any 3 digits
Mexico	Google Pay Apple Pay Mexico	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Mexico	PayPal Mexico	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Mongolia	MonPay	This payment channel can be tested using the test credentials below: Phone: 85246312 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Mongolia	Unitel Mongolia	This payment channel can be tested using the test credentials below: Phone: 85246312 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Mongolia	Toki	Usee the following phone number to initiate the transaction: Phone: 99918965 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Morocco	Card Payments Morocco	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Myanmar	ATOM	This payment channel can be tested using the test credentials below: Phone: 9762198200 OTP: 777777
Myanmar	U9	This payment channel can be tested using the test credentials below: Phone: 9943224706 OTP: 777777
Myanmar	WavePay	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Myanmar	Card Payments Myanmar	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Nepal	E-Pay	Not Available
Netherlands	Google Pay Apple Pay Netherlands	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Netherlands	iDeal	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Netherlands	Card Payments Netherlands	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Netherlands	Paypal Netherlands	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
New Zealand	Google Pay Apple Pay New Zealand	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
New Zealand	Card Payments New Zealand	Success Use case: 4000 0055 4000 0008 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
New Zealand	PayPal New Zealand	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Nigeria	Bank Transfer Nigeria	Use the following phone number to initiate the transaction: 08021234567 fill in email address and name (first name + last name) with a valid format After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Nigeria	Paga	Use the following phone number to initiate the transaction: 08021234567 fill in email address and name (first name + last name) with a valid format After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Nigeria	Opay Wallet	After initiating the transaction, 1. fill in email address and name (first name + last name) with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Nigeria	Verve Card	After initiating the transaction, 1. fill in email address and name (first name + last name) with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Nigeria	Card Payments Nigeria	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Norway	Google Pay Apple Pay Norway	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Norway	Vipps	After initiating the transaction and pressing on the "Continue" button, head to the payment simulator on the Publisher Portal and: 1. Select "Adyen EU" 2. Enter the transaction ID 3. Select the payment status you want to simulate 4. Enter the transaction amount
Norway	Card Payments Norway	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Norway	PayPal Norway	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Pakistan	Easypaisa	Use the following phone number to initiate the transaction: Phone: 3423372065 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Pakistan	JazzCash	Use the following phone number to initiate the transaction: Phone: 3060003421 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Pakistan	HBL Konnect	Use the following phone number and OTP to initiate the transaction: Phone: 3336775364 OTP: 77777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Pakistan	Card Payments Pakistan	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Pakistan	Bank Transfer Pakistan	Use the following credentials to initiate the transaction: Phone: 3336775364 Bank Account : 4210112345679 CNIC Number : 4210112345679 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Paraguay	Card Payments Paraguay	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Peru	Card Payments Peru	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Peru	PayPal Peru	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Philippines	Smart	This payment channel can be tested using the test credentials below: Phone: 9298611977 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Philippines	Dito	This payment channel can be tested using the test credentials below: Phone: 9298611977 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Philippines	Bank Transfers Philippines	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Philippines	7-Eleven Philippines	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Philippines	Cash at Retail ex 7-Eleven PH	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Philippines	GCash	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Philippines	GrabPay Philippines	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Philippines	Maya	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Philippines	Coins.ph	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Philippines	Card Payments Philippines	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Philippines	PayPal Philippines	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Philippines	Google Pay Apple Pay Philippines	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Poland	Google Pay Apple Pay Poland	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Poland	Blik	Use the following code to initiate the transaction: Blik Code: 777777 After pressing on the "Continue" button, a simulator page will open on a new tab, choose the desired transaction status to simulate
Poland	Card Payments Poland	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Poland	Paypal Poland	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Portugal	Google Pay Apple Pay Portugal	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Portugal	Multibanco	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Portugal	Card Payments Portugal	Use test cards to simulate several use cases (see testSuccess Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digitcards in the "Card test data").
Portugal	PayPal Portugal	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Qatar	Card Payments Qatar	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Qatar	PayPal Qatar	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Romania	Google Pay Apple Pay Romania	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Romania	Card Payments Romania	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Romania	PayPal Romania	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Saudi Arabia	Mobily	Not Available
Saudi Arabia	Card Payments Saudi Arabia	Success Use case: 4464 0400 0000 0007 Any valid date and CVV 123 Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Saudi Arabia	Mada	This payment channel can be tested using the test credentials below: Test Cards: 5123450000000008 OR 5123456789012346 Expiry: 01/39 CVV: 100
Saudi Arabia	Apple Pay Saudi Arabia	Not Available
Saudi Arabia	STC Pay	This payment channel can be tested using the test credentials below: Phone: 0557877988 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Saudi Arabia	PayPal Saudi Arabia	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Singapore	SingTel	This payment channel can be tested using the test credentials below: Phone: 84228130 OTP: 777777
Singapore	GrabPay Singapore	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Singapore	PayNow	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Singapore	Card Payments Singapore	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Singapore	PayPal Singapore	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Slovakia	PayPal Slovakia	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Slovakia	Card Payments Slovakia	4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
South Korea	Carrier Billing South Korea	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	KakaoPay	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	Naver Pay	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	Payco	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	T money	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	Culture Voucher	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
South Korea	Happymoney	Not Available
South Korea	Card Payments South Korea	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Spain	Google Pay Apple Pay Spain	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Spain	Card Payments Spain	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Spain	PayPal Spain	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Sri Lanka	Card Payments Sri Lanka	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Sri Lanka	Dialog	Not Available
Sweden	Google Pay Apple Pay Sweden	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Sweden	Trustly	Not Available
Sweden	Card Payments Sweden	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Sweden	PayPal Sweden	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Switzerland	Google Pay Apple Pay Switzerland	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
Switzerland	TWINT	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Switzerland	Card Payments Switzerland	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Switzerland	PayPal Switzerland	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Taiwan	Chunghwa Telecom	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Taiwan	FarEasTone	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Taiwan	GASH Gift Card	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Taiwan	Line Pay	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction. Note: this channel requires `items.code` to be not null. Ensure in production environment this field is set.
Taiwan	JKO Pay	After initiating the transaction, tap on the "Continue" button on the QR page, tap on the "Simulate payment outcome" button a new simulator page will open on a new tab, choose the desired transaction status to simulate
Taiwan	Card Payments Taiwan	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Taiwan	PayPal Taiwan	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Taiwan	GASH e-wallet	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Thailand	dtac	This payment channel can be tested using the test credentials below: Phone: 66947341559 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	AIS	This payment channel can be tested using the test credentials below: Phone: 909788150 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	Truemove H	This payment channel can be tested using the test credentials below: Phone: 909788150 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	Bank Transfers and Cash at Retail TH	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Thailand	K PLUS	This payment channel can be tested using the test credentials below: Phone number: 909788150 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	Promptpay	After initiating the transaction, 1. tap on the "Simulate payment outcome" button 2.a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	7-Eleven Thailand	This payment channel can be tested using the test credentials below: Phone number: 909788150 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	True Money Cash Card	This payment channel can be tested using the test codes below. Note that codes only work for the specified amount. 50 THB: 00000000000050 90 THB: 00000000000090 150 THB: 00000000000150 300 THB: 00000000000300 500 THB: 00000000000500 1000 THB: 00000000001000
Thailand	One 2 Call Cash Card	This payment channel can be tested using the test codes below. Note that codes only work for the specified amount. 50 THB: 4633189273447881 100 THB: 6468092687777569 500 THB: 0934714708596311 1000 THB: 8393686298717652
Thailand	TrueMoney Wallet	Use the following Phone number and OTP to complete a transaction: Phone: 909788150 OTP: 777777 After pressing on the "Continue" button, a new simulator page will open on a new tab, choose the desired transaction status to simulate
Thailand	ShopeePay Thailand	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Thailand	Rabbit LINE Pay	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Thailand	Card Payments Thailand	Use the following card details to initiate the transaction: Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Thailand	PayPal Thailand	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Timor Leste	Telemor	Not Available
Turkey	Papara	Not Available
Turkey	Card Payments Turkey	Not Available
Turkey	Bank Transfer Turkey	Not Available
UAE	Etisalat	Not Available
UAE	Card Payments United Arab Emirates	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
UAE	PayPal United Arab Emirates	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
United Kingdom	Google Pay Apple Pay UK	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
United Kingdom	Card Payments UK	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
United Kingdom	PayPal UK	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`
Uruguay	Card Payments Uruguay	Use test cards to simulate several use cases (sSuccess Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digitee test cards in the "Card test data").
USA	Google Pay Apple Pay US	Google Pay: 1. Test using a device/browser with Google Pay configured 2. Complete the transaction with the card registered with Google Pay, the card will not be charged
USA	Card Payments United States of America	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
USA	Cash App	1. Scan the QR code with any mobile device 2. Complete the transaction by clicking the "Approve" button
USA	PayPal US	PayPal US can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs` Venmo: Please reach out to the Codapay Support Team for the Sandbox APK file
Vietnam	VTC Pay	After initiating the transaction, 1. fill in email address with a valid format 2. press on the "Continue" button, a new simulator page will open on a new tab 3. Choose the desired transaction status to simulate
Vietnam	Card Payments Vietnam	Success Use case: 4242 4242 4242 4242 Any valid date and any 3-digit Decline Use case: 4000 0000 0000 0002 Any valid date and any 3-digit
Vietnam	MoMo E-Wallet	After initiating and pressing "Continue" you will be redirected to a page where you can choose the payment status to be used to complete the transaction.
Vietnam	PayPal Vietnam	This payment channel can be tested using the test credentials below: E-mail: sb-fibvd4157965@personal.example.com Password: `Mz<-G0bs`

# Sandbox Testing Guide {% hint style="info" %} 👍 **Simulator feature available for Admin and Tech roles** {% endhint %} ### **Step 1: Login to** [**Publisher Portal**](https://portal.coda.co/) ### **Step 2: Access from the side menu Products > Codapay > Sandbox Testing** ### Payment Initiation Choose the **Title** and enter the required **Request Parameters**. Then, click the **"Send Request"** button to generate the **Transaction ID**.

### Payment Page After selecting **"Generate Payment Page"** on the payment initiation page, you'll be redirected to the **Payment Page** tab. There, you can access test page URLs for both mobile and desktop versions. To open the payment page in a new tab, either click the **"Generate Payment Page"** button or directly select the provided URLs.

### Display Payment Page Make sure to open the payment page, fill up the required testing information (refer to [payment channel testing instruction](/codapay/integration-guides/testing-guide/payment-channel-testing-instructions)), and proceed to the next step

### Payment Simulator Choose the transaction status you would like to simulate

### Transaction status update Payment Page will be updated to the responding simulated status

### Payment Status Check Enter the **request parameters** to check the response for a **Successful Payment Status**. You can implement the **Payment Status Check** flow on your end to verify the payment results for each transaction.

Click on Send Request to check the response structure

# Sandbox Configuration and Production Configuration To configure please proceed to [Publisher Portal](https://portal.coda.co/) -> Products -> Codapay -> Sandbox/Production Configuration ## Merchant & URL Configuration 1. Proceed to Publisher Portal > Products > Codapay > Sandbox/Production Configuration 2. Select "Edit" > "Merchant & URLs configuration. Or select the countries > "Bulk edit configuration"

***

**Backend API**: This is required if you're integrating with [Backend API](/codapay/integration-guides/payment-channel-info/backend-api) **USD Price Notification**: By activating, you will receive the init USD Price appended to the end of the callback parameter (Only applicable for "currency": 840) {% tabs %} {% tab title="Sample response" %} \ PaymentType=23\&ResultCode=0\&Checksum=bbb4828b8d2a1bafb123a12b55d666f5&USDPrice=100.00 {% endtab %} {% endtabs %} **Failed Notification:** The notification URL would receive failed transaction notification as well, including expired transaction. **Complete notification URL**: When a transaction has been completed with Success status, Codapay notifies the partner's application using the "Complete notification URL", also known as "Callback URL" **Complete landing page URL**: **(Supports HTTP/HTTPS/Deeplink)** This URL defines which page the customers are being redirected to after completing the transaction in Coda's payment interface. Please reuse the same redirect address if there's no categorized redirect page: * ATM pending landing page URL * Pending OTC landing page URL \*No configuration required - Subscription notification URL *** ## Payment Page Configuration 1. Proceed to Publisher Portal > Products > Codapay > Sandbox/Production Configuration 2. Select "Edit" > "Coda payment page configuration"

**Payment page configuration （Only applicable for "payType": 0)** Calling `"payType": 0` allows the user to choose the preferred payment without the merchant designing the payment channel selection page (PCSP) and continuing payment. #### Note: * PCSP does not display fixed price point channel and Voucher (cash card) channel * Only the amount supported by the payment channel will be shown * Payment channel displayed as "Not Init" status means it's not activated; please contact Codapay support team for further assistance. *** ## **Bulk edit configuration** **To use the "Bulk edit configuration", you'd need to select the titles.** Filtering options: * Title name * Country name # Country and Currency Codes

Country	Country Code (ISO 3166)	Currency	Currency Code (ISO 4217)
Algeria	12	Algerian Dinar	12
Argentina	32	Argentine Peso	32
Australia	36	Australian dollar	36
Austria	40	Euro	978
Bahrain	48	Bahraini Dinar	48
Bangladesh	50	Bangladeshi Taka	50
Brazil	76	Brazilian Real	986
Bolivia	68	Bolivian Boliviano	68
Belgium	56	Euro	978
Cambodia	116	United States Dollar	840
Chile	152	Chilean Peso	152
Colombia	170	Colombian Peso	170
Canada	124	Canadian Dollar	124
Czech Republic	203	Czech Koruna	203
Denmark	208	Danish Krone	208
Dominican Republic	214	Dominican Peso	214
Egypt	818	Egyptian Pound	818
Ecuador	218	United States Dollar	840
France	250	Euro	978
Finland	246	Euro	978
Germany	276	Euro	978
Greece	300	Euro	978
Guatemala	320	Quetzal	320
Hong Kong	344	Hong Kong Dollar	344
Hungary	348	Forint	348
India	356	Indian Rupee	356
Indonesia	360	Indonesian Rupiah	360
Iraq	368	Iraqi Dinar	368
Ireland	372	Euro	978
Israel	376	New Israeli Sheqel	376
Italy	380	Euro	978
Japan	392	Yen	392
Kazakhstan	398	Kazakhstani Tenge	398
Kuwait	414	Kuwaiti Dinar	414
Kenya	404	Kenyan Shilling	404
Laos	418	Lao Kip	418
Malaysia	458	Malaysian Ringgit	458
Mexico	484	Mexican Peso	484
Mongolia	496	Mongolian Tugrug	496
Morocco	504	Moroccan Dirham	504
Myanmar	104	Myanmar Kyat	104
Nepal	524	Nepalese rupee	524
Nigeria	566	Nigerian Naira	566
Netherlands	528	Euro	978
New Zealand	554	New Zealand Dollar	554
Norway	578	Norwegian Krone	578
Pakistan	586	Pakistani Rupee	586
Paraguay	600	Paraguayan Guaraní	600
Peru	604	Nuevo Sol	604
Philippines	608	Philippine Peso	608
Poland	616	Zloty	985
Portugal	620	Euro	978
Puerto Rico	630	US Dollar	840
Qatar	634	Qatari Riyal	634
Russia	643	Russian Ruble	643
Romania	642	Romanian Leu	946
Saudi Arabia	682	Saudi Riyal	682
Singapore	702	Singapore Dollar	702
Slovakia	703	Euro	978
South Africa	710	South African Rand	710
South Korea	410	Korean Won	410
Sri Lanka	144	Sri Lankan Rupee	144
Switzerland	756	Swiss Franc	756
Spain	724	Euro	978
Sweden	752	Swedish Krona	752
Taiwan	158	New Taiwan Dollar	901
Thailand	764	Thai Baht	764
Timor-Leste	626	United States Dollar	840
Turkey	792	Turkish Lira	949
United Arab Emirates	784	United Arab Emirates Dirham	784
Great Britain (UK, Scotland, Wales)	826	Pound Sterling	826
Uruguay	858	Uruguayan Peso	858
United States of America	840	United States Dollar	840
Uzbekistan	860	Uzbekistan Sum	860
Vietnam	704	Vietnamese Dong	704

**Documentation Note:** Geographical labels and API parameters (such as `country_code`) are based on ISO 3166-1 standards to ensure compatibility with global banking and payment networks. Across our documentation and systems, these identifiers are used strictly for technical routing and to designate operational markets. # Languages


Country	Language	Language Code
Indonesia	Indonesian	id_ID
Indonesia	English	en_ID
Singapore	English	en_SG
Singapore	Chinese (Mandarin)	zh_SG
Malaysia	English	en_MY
Malaysia	Chinese	zh_MY
Malaysia	Malay	ms_MY
Philippines	English	en_PH
Philippines	Tagalog	tl_PH
Thailand	English	en_TH
Thailand	Thai	th_TH
Vietnam	English	en_VN
Vietnam	Vietnamese	vi_VN
Cambodia	English	en_KH
Cambodia	Khmer	km_KH
Myanmar	English	en_MM
Myanmar	Burmese	my_MM
Laos	English	en_LA
Laos	Lao	lo_LA
Taiwan	English	en_TW
Taiwan	Traditional Chinese	zh_TW
Hong Kong	English	en_HK
Hong Kong	Chinese	zh_HK
Japan	English	en_JP
Japan	Japanese	ja_JP
South Korea	English	en_KR
South Korea	Korean	ko_KR
Timor-Leste	English	en_TL
Timor-Leste	Portuguese	pt_TL
India	English	en_IN
Sri Lanka	English	en_LK
Bangladesh	English	en_BD
Bangladesh	Bengali	bn_BD
Pakistan	English	en_PK
Nepal	English	en_NP
Nepal	Nepali	np_NP
Saudi Arabia	English	en_SA
Saudi Arabia	Arabic	ar_SA
United Arab Emirates	English	en_AE
United Arab Emirates	Arabic	ar_AE
Egypt	English	en_EG
Egypt	Arabic	ar_EG
Iraq	English	en_IQ
Iraq	Arabic	ar_IQ
Qatar	English	en_QA
Qatar	Arabic	ar_QA
Kuwait	English	en_KW
Kuwait	Arabic	ar_KW
Bahrain	English	en_BH
Bahrain	Arabic	ar_BH
Morocco	English	en_MA
Morocco	Arabic	ar_MA
Algeria	English	en_DZ
Israel	English	en_IL
Brazil	English	en_BR
Brazil	Portuguese	pt_BR
Mexico	English	en_MX
Mexico	Spanish	es_MX
Argentina	English	en_AR
Argentina	Spanish	es_AR
Colombia	English	en_CO
Colombia	Spanish	es_CO
Chile	English	en_CL
Chile	Spanish	es_CL
Peru	English	en_PE
Peru	Spanish	es_PE
Paraguay	English	en_PY
Paraguay	Spanish	es_PY
Uruguay	English	en_UY
Uruguay	Spanish	es_UY
Bolivia	English	en_BO
Bolivia	Spanish	es_BO
Ecuador	English	en_EC
Ecuador	Spanish	es_EC
Guatemala	English	en_GT
Guatemala	Spanish	es_GT
Dominican Republic	English	en_DO
Puerto Rico	English	en_PR
United Kingdom	English	en_GB
Ireland	English	en_IE
Germany	English	en_DE
Germany	German	de_DE
France	English	en_FR
France	French	fr_FR
Spain	English	en_ES
Spain	Spanish	es_ES
Italy	English	en_IT
Italy	Italian	it_IT
Netherlands	English	en_NL
Netherlands	Dutch	nl_NL
Belgium	English	en_BE
Belgium	German	de_BE
Belgium	French	fr_BE
Switzerland	English	en_CH
Switzerland	German	de_CH
Switzerland	French	fr_CH
Austria	English	en_AT
Austria	German	de_AT
Poland	English	en_PL
Poland	Polish	pl_PL
Portugal	English	en_PT
Portugal	Portuguese	pt_PT
Sweden	English	en_SE
Sweden	Swedish	sv_SE
Norway	English	en_NO
Norway	Norwegian	no_NO
Denmark	English	en_DK
Denmark	Danish	da_DK
Finland	English	en_FI
Finland	Finnish	fi_FI
Greece	English	en_GR
Greece	Greek	el_GR
Czech Republic	English	en_CZ
Czech Republic	Czech	cs_CZ
Slovakia	English	en_SK
Slovakia	Slovak	sk_SK
Hungary	English	en_HU
Hungary	Hungarian	hu_HU
Romania	English	en_RO
Romania	Romanian	ro_RO
Russia	Russian	ru_RU
Turkey	English	en_TR
Turkey	Turkish	tr_TR
Kazakhstan	English	en_KZ
Kazakhstan	Russian	ru_KZ
Uzbekistan	English	en_UZ
Mongolia	English	en_MN
Mongolia	Mongolian	mn_MN
United States	English	en_US
Canada	English	en_CA
Australia	English	en_AU
New Zealand	English	en_NZ
South Africa	English	en_ZA
Nigeria	English	en_NG
Kenya	English	en_KE

# Payment Channel Info Comprehensive Overview of Payment Methods Supported by Codapay Our supported payment channels include Carrier Billing, Bank Transfers, Debit/Credit Cards, Convenience Store Payments, Cash Cards/Vouchers, and E-Wallets. Codapay supports these payment methods based on regional availability. You can integrate each payment channel using the [Hosted Payment Page Integration](/codapay/hosted-payment-page-integration) or [Backend API Integration](/codapay/direct-api-integration), depending on their availability. {% hint style="success" %} Hosted Payment Page Integration supports all payment channels. For the channels supported by Backend API Integration, please refer to the related column. {% endhint %} Below is a summary of the channels we support in each country/region, along with explanations of each payment type ## Payment Types ### Carrier Billing Carrier Billing allows customers to charge purchases to their mobile phone account. The payment is authenticated through an SMS sent to the customer's phone and is processed immediately. {% hint style="info" %} **Note:** Some mobile network and cashcard operators only allow transactions at predefined price points and may enforce limits for transaction values. See [price points and transaction limits](/codapay/integration-guides/price-limits) for details. {% endhint %} ### Bank Transfer Customers can pay by executing a bank transfer at an ATM, bank counter, or via online banking. Merchants receive a unique payment code, which the customer enters as part of the bank transfer details. ### Card Payments This method allows customers to complete payments using their credit or debit card. Customers are redirected to the partner's payment page to input their card details and complete the payment. ### Convenience Store Payments This method allows customers to complete payments at a convenience store. Customers receive a unique payment code from Codapay, which they present at the store. ### Voucher (Cash Card) Customers purchase a voucher from an issuer and enter it in Codapay's payment window to purchase digital content. ### E-Wallet E-wallets allow customers to have a digital payment account and top-up balance. Codapay supports many types of e-wallets for purchases. ## Available Payment Channels by Region {% hint style="success" %} **Payment Channels Logo**: The logo can be downloaded from [Brand Guidelines](/codapay/integration-guides/brand-guidelines#logos) zip file. {% endhint %} ## Asia ### Australia🇦🇺

Payment Channel	Type	Supported API Integration
Card Payments Australia	Cards	Hosted Payment Page
Google Pay Apple Pay Australia	E-Wallet	Hosted Payment Page
PayPal Australia	E-Wallet	Hosted Payment Page

### Bangladesh🇧🇩 > 🚧 bKash, Nagad > > * bKash paused since 11th August 2026 until further notice. > * Nagad paused since 22nd July 2026 until further notice.

Payment Channel	Type	Supported API Integration
bKash	E-Wallet	Hosted Payment Page, Backend API
Robi Airtel	Carrier Billing	Hosted Payment Page, Backend API
Nagad	E-wallet	Hosted Payment Page

### Cambodia🇰🇭 > 🚧 Metfone, Cellcard, Smart Axiata > > * Metfone paused since 7th March 2024 until further notice. > * Cellcard paused since 16th March 2024 until further notice. > * Smart paused since 21st March 2024 until further notice.

Payment Channel	Type	Supported API Integration
Bakong (KHQR)	E-Wallet	Hosted Payment Page
Card Payments Cambodia	Cards	Hosted Payment Page
Cellcard	Carrier Billing	Hosted Payment Page
Metfone	Carrier Billing	Hosted Payment Page
Smart Axiata	Carrier Billing	Hosted Payment Page, Backend API
Paygo	E-Wallet	Hosted Payment Page
PiPay	E-Wallet	Hosted Payment Page
Wing	E-Wallet	Hosted Payment Page

### Hong Kong🇭🇰

Payment Channel	Type	Supported API Integration
Alipay Hong Kong	E-Wallet	Hosted Payment Page, Backend API
Card Payments Hong Kong	Cards	Hosted Payment Page
WeChat Pay Hong Kong	E-Wallet	Hosted Payment Page, Backend API
Google Pay Apple Pay Hong Kong	E-Wallet	Hosted Payment Page
FPS	Bank Transfer	Hosted Payment Page
PayPal Hong Kong	E-Wallet	Hosted Payment Page

### India 🇮🇳

Payment Channel	Type	Supported API Integration
UPI	Bank Transfer	Hosted Payment Page

### Indonesia🇮🇩 > 🚧 Smartfren > > Smartfren paused since 2nd Sep 2025 until further notice.

Payment Channel	Type	Supported API Integration
Alfamart	Convenience Store Payments (OTC)	Hosted Payment Page, Backend API
Bank Transfers Indonesia	Bank Transfer	Hosted Payment Page, Backend API
Card Payments Indonesia	Cards	Hosted Payment Page
DANA	E-Wallet	Hosted Payment Page, Backend API
DOKU Wallet	E-Wallet	Hosted Payment Page, Backend API
GO-PAY	E-Wallet	Hosted Payment Page, Backend API
Indomaret	Convenience Store Payments (OTC)	Hosted Payment Page, Backend API
Indosat	Carrier Billing	Hosted Payment Page, Backend API
LinkAja	E-Wallet	Hosted Payment Page, Backend API
OVO	E-Wallet	Hosted Payment Page, Backend API
QRIS	Bank Transfer	Hosted Payment Page
ShopeePay Indonesia	E-Wallet	Hosted Payment Page, Backend API
Smartfren	Carrier Billing	Hosted Payment Page
Telkomsel	Carrier Billing	Hosted Payment Page, Backend API
Tri Indonesia	Carrier Billing	Hosted Payment Page, Backend API
XL	Carrier Billing	Hosted Payment Page, Backend API
PayPal Indonesia	E-Wallet	Hosted Payment Page

### Iraq🇮🇶 > 🚧 Zain Iraq > > DCB Channel paused since 28th Feb 2023 until further notice.

Payment Channel	Type	Supported API Integration
Zain Iraq	Carrier Billing	Hosted Payment Page

### Japan🇯🇵

Payment Channel	Type	Supported API Integration
Card Payments Japan	Cards	Hosted Payment Page
Google Pay Apple Pay Japan	E-Wallet	Hosted Payment Page
PayPay	E-Wallet	Hosted Payment Page
PayPal Japan	E-Wallet	Hosted Payment Page

### Kazakhstan🇰🇿

Payment Channel	Type	Supported API Integration
Card Payments Kazakhstan	Cards	Hosted Payment Page

### Laos🇱🇦 > 🚧 Unitel Laos > > Channel paused since 16th Jan 2026 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Laos	Cards	Hosted Payment Page
Lao Telecom	Carrier Billing	Hosted Payment Page
Unitel Laos	Carrier Billing	Hosted Payment Page, Backend API

### Malaysia🇲🇾 > 🚧 Maxis > > Channel paused since 12 Aug 2026 until further notice. | Payment Channel | Type | Supported API Integration | | ----------------------------- | --------------- | -------------------------------- | | Maxis | Carrier Billing | Hosted Payment Page | | Boost | E-Wallet | Hosted Payment Page, Backend API | | Card Payments Malaysia | Cards | Hosted Payment Page | | Celcom | Carrier Billing | Hosted Payment Page, Backend API | | Digi | Carrier Billing | Hosted Payment Page | | GrabPay Malaysia | E-Wallet | Hosted Payment Page, Backend API | | MAE / DuitNow | Bank Transfer | Hosted Payment Page, Backend API | | ShopeePay Malaysia | E-Wallet | Hosted Payment Page, Backend API | | Touch-NGo | E-Wallet | Hosted Payment Page, Backend API | | U Mobile | Carrier Billing | Hosted Payment Page | | Google Pay Apple Pay Malaysia | E-Wallet | Hosted Payment Page | ### Mongolia🇲🇳

Payment Channel	Type	Supported API Integration
MonPay	E-Wallet	Hosted Payment Page
Unitel Mongolia	Carrier Billing	Hosted Payment Page
Toki	Wallet	Hosted Payment Page

### Myanmar🇲🇲 > 🚧 easyPoints, MPT, KBZPay > > * easyPoints Channel paused since 19th Aug 2022 until further notice. > * MPT Channel paused since 27th Mar 2024 until further notice. > * KBZPay Channel paused since 20th July 2024 until further notice. | Payment Channel | Type | Supported API Integration | | --------------------- | ------------------- | -------------------------------- | | ATOM | Carrier Billing | Hosted Payment Page, Backend API | | Card Payments Myanmar | Cards | Hosted Payment Page | | MPT | Carrier Billing | Hosted Payment Page | | U9 | Carrier Billing | Hosted Payment Page, Backend API | | WavePay | E-Wallet | Hosted Payment Page | | KBZPay | E-Wallet | Hosted Payment Page, Backend API | | easyPoints | Voucher (Cash Card) | Hosted Payment Page, Backend API | ### Nepal🇳🇵 > 🚧 E-Pay > > * E-Pay Channel paused since 17th Apr 2025 until further notice.

Payment Channel	Type	Supported API Integration
E-Pay	E-Wallet	Hosted Payment Page, Backend API

### **New Zealand🇳🇿**

Payment Channel	Type	Supported API Integration
Google Pay Apple Pay New Zealand	E-Wallet	Hosted Payment Page
Card Payments New Zealand	Cards	Hosted Payment Page
PayPal New Zealand	E-Wallet	Hosted Payment Page

### Pakistan🇵🇰 > 🚧 Nayapay, Ufone, Telenor Pakistan > > * Nayapay Channel paused since 26th Sept 2022 until further notice. > * Ufone Channel paused since 26th June 2023 until further notice. > * Telenor Pakistan paused since 11th Dec 2023 until further notice. > * Easypaisa paused for **Live Streaming titles** since 23rd Jan 2023 until further notice.

Payment Channel	Type	Supported API Integration
Easypaisa	E-Wallet	Hosted Payment Page
Jazzcash	E-Wallet	Hosted Payment Page
Nayapay	E-Wallet	Hosted Payment Page
Telenor Pakistan	Carrier Billing	Hosted Payment Page, Backend API
Ufone	Carrier Billing	Hosted Payment Page
Card Payments Pakistan	Cards	Hosted Payment Page
HBL Konnect	E-Wallet	Hosted Payment Page
Bank Transfer Pakistan	Bank Transfer	Hosted Payment Page

### Philippines🇵🇭 > 🚧 PayPal Philippines > > * PayPal Philippines Channel paused since 17th Apr 2025 until further notice. | Payment Channel | Type | Supported API Integration | | -------------------------------- | -------------------------------- | -------------------------------- | | 7-Eleven Philippines | Convenience Store Payments (OTC) | Hosted Payment Page, Backend API | | Bank Transfers Philippines | Bank Transfer | Hosted Payment Page, Backend API | | Card Payments Philippines | Cards | Hosted Payment Page | | Cash at Retail ex 7-Eleven PH | Convenience Store Payments (OTC) | Hosted Payment Page | | Coins.ph | E-Wallet | Hosted Payment Page, Backend API | | GCash | E-Wallet | Hosted Payment Page, Backend API | | GrabPay Philippines | E-Wallet | Hosted Payment Page | | Maya | E-Wallet | Hosted Payment Page, Backend API | | Smart | Carrier Billing | Hosted Payment Page, Backend API | | Dito | Carrier Billing | Hosted Payment Page | | Google Pay Apple Pay Philippines | E-Wallet | Hosted Payment Page | | PayPal Philippines | E-Wallet | Hosted Payment Page | ### Singapore🇸🇬 > 🚧 SingTel > > * SingTel paused since 9th Dec 2025 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Singapore	Cards	Hosted Payment Page
GrabPay Singapore	E-Wallet	Hosted Payment Page, Backend API
PayNow	E-Wallet	Hosted Payment Page
SingTel	Carrier Billing	Hosted Payment Page
PayPal Singapore	E-Wallet	Hosted Payment Page

### South Korea🇰🇷 > 🚧 Happymoney > > * Happymoney paused since 25th Jul 2024 until further notice. | Payment Channel | Type | Supported API Integration | | --------------------------- | ------------------- | ------------------------- | | Card Payments South Korea | Cards | Hosted Payment Page | | Carrier Billing South Korea | Carrier Billing | Hosted Payment Page | | KakaoPay | E-Wallet | Hosted Payment Page | | Naver Pay | E-Wallet | Hosted Payment Page | | Culture Voucher | Voucher (Cash Card) | Hosted Payment Page | | Payco | E-Wallet | Hosted Payment Page | | T-Money | E-Wallet | Hosted Payment Page | | Happymoney | Voucher (Cash Card) | Hosted Payment Page | ### Sri Lanka🇱🇰

Payment Channel	Type	Supported API Integration
Card Payments Sri Lanka	Cards	Hosted Payment Page
Dialog	Carrier Billing	Hosted Payment Page

### Taiwan > 🚧 PayPal Taiwan > > Channel pause since 10th December 2025 until further notice > > 🚧 Taiwan Mobile > > Channel pause since 31st March 2023 until further notice | Payment Channel | Type | Supported API Integration | | --------------------------- | ------------------- | -------------------------------- | | Chunghwa Telecom | Carrier Billing | Hosted Payment Page, Backend API | | FarEasTone | Carrier Billing | Hosted Payment Page, Backend API | | GASH Gift Card | Voucher (Cash Card) | Hosted Payment Page, Backend API | | JKO Pay | E-Wallet | Hosted Payment Page, Backend API | | Line Pay | E-Wallet | Hosted Payment Page, Backend API | | Taiwan Mobile | Carrier Billing | Hosted Payment Page | | Card Payments Taiwan | Cards | Hosted Payment Page | | PayPal Taiwan | E-Wallet | Hosted Payment Page | | GASH e-wallet | E-Wallet | Hosted Payment Page | | Google Pay Apple Pay Taiwan | E-Wallet | Hosted Payment Page | ### Thailand🇹🇭 > 🚧 One-2-Call Cash Card > > Channel temporary not available until further notice. | Payment Channel | Type | Supported API Integration | | ------------------------------------ | -------------------------------------------------- | -------------------------------- | | 7-Eleven Thailand | Convenience Store Payments (OTC) | Hosted Payment Page, Backend API | | AIS | Carrier Billing | Hosted Payment Page | | Bank Transfers and Cash at Retail TH | Bank Transfer and Convenience Store Payments (OTC) | Hosted Payment Page, Backend API | | Card Payments Thailand | Cards | Hosted Payment Page | | dtac | Carrier Billing | Hosted Payment Page | | K PLUS | Bank Transfer | Hosted Payment Page, Backend API | | One-2-Call Cash Card | Voucher (Cash Card) | Hosted Payment Page, Backend API | | PromptPay | Bank Transfer | Hosted Payment Page, Backend API | | Rabbit LINE Pay | E-Wallet | Hosted Payment Page, Backend API | | ShopeePay Thailand | E-Wallet | Hosted Payment Page, Backend API | | TrueMoney Cash Card | Voucher (Cash Card) | Hosted Payment Page | | True Money Wallet | E-Wallet | Hosted Payment Page | | Truemove H | Carrier Billing | Hosted Payment Page | | PayPal Thailand | E-Wallet | Hosted Payment Page | ### Timor Leste🇹🇱 > 🚧 Telemor > > Channel paused since 3rd Oct 2025 until further notice.

Payment Channel	Type	Supported API Integration
Telemor	Carrier Billing	Hosted Payment Page

### Vietnam🇻🇳

Payment Channel	Type	Supported API Integration
Card Payments Vietnam	Cards	Hosted Payment Page
VTCPay	E-Wallet	Hosted Payment Page
MoMo E-Wallet	E-Wallet	Hosted Payment Page
PayPal Vietnam	E-Wallet	Hosted Payment Page

*** ## Middle East ### Bahrain🇧🇭 > 🚧 Zain Bahrain, Benefit > > Zain Channel paused since 11th Oct 2022 until further notice. > > Benefit channel paused since 24th Feb 2025

Payment Channel	Type	Supported API Integration
Zain Bahrain	Carrier Billing	Hosted Payment Page
Benefit	Cards	Hosted Payment Page, Backend API

### Egypt🇪🇬 > 🚧 Meeza Card Payments > > Meeza Card Payments channel paused since 24th Jul 2025 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Egypt	Cards	Hosted Payment Page
Fawry	Convenience Store Payments (OTC)	Hosted Payment Page, Backend API
Masary, Aman, Momken	Convenience Store Payments (OTC)	Hosted Payment Page, Backend API
Meeza Card Payments	Cards	Hosted Payment Page
Orange Money	E-Wallet	Hosted Payment Page
Vodafone Cash	E-Wallet	Hosted Payment Page, Backend API
PayPal Egypt	E-Wallet	Hosted Payment Page

### Kuwait🇰🇼 > 🚧 Zain Kuwait > > * Zain Channel paused since 11th Oct 2022 until further notice.

Payment Channel	Type	Supported API Integration
Zain Kuwait	Carrier Billing	Hosted Payment Page
KNET & Card Payments Kuwait	Cards	Hosted Payment Page

### Qatar🇶🇦

Payment Channel	Type	Supported API Integration
Card Payments Qatar	Cards	Hosted Payment Page
PayPal Qatar	E-Wallet	Hosted Payment Page

### Saudi Arabia🇸🇦 > 🚧 Mobily > > * Mobily Channel paused since 15th Apr 2025 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Saudi Arabia	Cards	Hosted Payment Page
Mada	Cards	Hosted Payment Page, Backend API
STC Pay	E-Wallet	Hosted Payment Page
Mobily	Carrier Billing	Hosted Payment Page
Apple Pay Saudi Arabia	E-Wallet	Hosted Payment Page
PayPal Saudi Arabia	E-Wallet	Hosted Payment Page

### Turkey🇹🇷 > 🚧 Papara, Bank Transfer Turkey > > * Bank Transfer Turkey Channel paused since 24th Dec 2025 until further notice. > * Papara Channel paused since 31st Oct 2025 until further notice.

Payment Channel	Type	Supported API Integration
Papara	E-Wallet	Hosted Payment Page
Bank Transfer Turkey	Bank Transfer	Hosted Payment Page, Backend API
Card Payments Turkey	Cards	Hosted Payment Page

### United Arab Emirates (UAE)🇦🇪 > 🚧 **Payby, Etisalat** > > * Payby Channel paused since 12th Dec 2022 until further notice. > * Etisalat Channel paused since 11th Aug 2025 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments United Arab Emirates	Cards	Hosted Payment Page
PayBy	E-Wallet	Hosted Payment Page, Backend API
Etisalat	Carrier Billing	Hosted Payment Page
PayPal United Arab Emirates	E-Wallet	Hosted Payment Page

*** ## Africa ### Morocco🇲🇦

Payment Channel	Type	Supported API Integration
Card Payments Morocco	Cards	Hosted Payment Page

### Nigeria🇳🇬

Payment Channel	Type	Supported API Integration
Paga	E-Wallet	Hosted Payment Page, Backend API
Verve Card	Cards	Hosted Payment Page, Backend API
Bank Transfers Nigeria	Bank Transfer	Hosted Payment Page
Opay Wallet	E-Wallet	Hosted Payment Page
Card Payments Nigeria	Cards	Hosted Payment Page

### South Africa🇿🇦 > 🚧 Bank Transfer Africa, 1Voucher > > * Bank Transfer Africa paused since 7th March 2023 until further notice. > * 1Voucher paused since 22nd April 2024 until further notice.

Payment Channel	Type	Supported API Integration
Bank Transfers South Africa	Bank Transfer	Hosted Payment Page, Backend API
Card Payments South Africa	Cards	Hosted Payment Page
1Voucher	Voucher	Hosted Payment Page

### Kenya🇰🇪 > 🚧 M-PESA > > * M-PESA paused since 28th July 2026 until further notice.

Payment Channel	Type	Supported API Integration
M-PESA	E-Wallet	Hosted Payment Page

*** ## North America ### Canada🇨🇦

Payment Channel	Type	Supported API Integration
Card Payments Canada	Cards	Hosted Payment Page
Google Pay Apple Pay Canada	E-Wallet	Hosted Payment Page
PayPal Canada	E-Wallet	Hosted Payment Page

### United States of America🇺🇸 | Payment Channel | Type | Supported API Integration | | ---------------------------------------------------------------- | -------- | ------------------------- | |

Card Payments US
(Visa, Mastercard, American Express)

| Cards | Hosted Payment Page | | Google Pay Apple Pay US | E-Wallet | Hosted Payment Page | | Cash App | E-Wallet | Hosted Payment Page | | PayPal US | E-Wallet | Hosted Payment Page | ## Latin America ### Argentina🇦🇷 > 🚧 Rapipago, MercadoPago, Pago Facil > > Channel paused since 1st June 2023 until further notice. | Payment Channel | Type | Supported API Integration | | ----------------------- | -------------------------------- | -------------------------------- | | Card Payments Argentina | Cards | Hosted Payment Page | | Mercado Pago Argentina | Wallet | Hosted Payment Page, Backend API | | Pago Facil | Convenience Store Payments (OTC) | Hosted Payment Page, Backend API | | Rapipago | Convenience Store Payments (OTC) | Hosted Payment Page, Backend API | ### Bolivia🇧🇴 > 🚧 Cash Payments Bolivia > > Channel paused since 9th July 2023 until further notice.

Payment Channel	Type	Supported API Integration
Cash Payments Bolivia	Convenience Store Payments (OTC)	Hosted Payment Page
Card Payments Bolivia	Cards	Hosted Payment Page

### Brazil🇧🇷 > 🚧 Mercado Pago, Bank Transfers Brazil > > Bank Transfers Brazil paused since 20th Aug 2026 until further notice. > > Mercado Pago paused since 2nd Nov 2025 until further notice.

Payment Channel	Type	Supported API Integration
Bank Transfers Brazil	Bank Transfer	Hosted Payment Page
Boleto	Convenience Store Payments (OTC)	Hosted Payment Page
Card Payments Brazil	Cards	Hosted Payment Page
Mercado Pago	E-Wallet	Hosted Payment Page, Backend API
PicPay	E-Wallet	Hosted Payment Page, Backend API
Pix	Bank Transfer	Hosted Payment Page, Backend API
PayPal Brazil	E-Wallet	Hosted Payment Page

### Chile🇨🇱 > 🚧 Bank Transfer Chile > > Channel paused since 9th July 2023 until further notice.

Payment Channel	Type	Supported API Integration
Bank Transfers Chile	Bank Transfer	Hosted Payment Page
Card Payments Chile	Cards	Hosted Payment Page
PayPal Chile	E-Wallet	Hosted Payment Page

### Colombia🇨🇴

Payment Channel	Type	Supported API Integration
Card Payments Colombia	Cards	Hosted Payment Page
DaviPlata	E-Wallet	Hosted Payment Page, Backend API
Nequi	E-Wallet	Hosted Payment Page
Bank Transfers Colombia	Bank Transfer	Hosted Payment Page, Backend API
PayPal Colombia	E-Wallet	Hosted Payment Page
Google Pay / Apple Pay Colombia	E-Wallet	Hosted Payment Page

### Ecuador🇪🇨 > 🚧 Cash Payment Ecuador > > Channel paused since 9th July 2023 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Ecuador	Cards	Hosted Payment Page
Cash Payments Ecuador	Convenience Store Payments (OTC)	Hosted Payment Page
PayPal Ecuador	E-Wallet	Hosted Payment Page

### Mexico🇲🇽 > 🚧 toditoCash > > Channel paused since 19th December 2025 until further notice. | Payment Channel | Type | Supported API Integration | | --------------------------- | -------------------------------- | -------------------------------- | | Bank Transfer Mexico | Bank Transfer | Hosted Payment Page, Backend API | | Card Payments Mexico | Cards | Hosted Payment Page | | Mercado Pago Mexico | E-Wallet | Hosted Payment Page, Backend API | | Oxxo Pay | Voucher (Cash Card) | Hosted Payment Page, Backend API | | PaysafeCard Mexico | Voucher (Cash Card) | Hosted Payment Page | | toditoCash | E-Wallet | Hosted Payment Page, Backend API | | Google Pay Apple Pay Mexico | E-Wallet | Hosted Payment Page | | PayPal Mexico | E-Wallet | Hosted Payment Page | | OXXO | Convenience Store Payments (OTC) | Hosted Payment Page | ### Paraguay🇵🇾

Payment Channel	Type	Supported API Integration
Card Payments Paraguay	Cards	Hosted Payment Page

### Peru🇵🇪 > 🚧 Bank Transfer Peru and Cash Payment Peru > > Channel paused since 9th June 2023 until further notice.

Payment Channel	Type	Supported API Integration
Bank Transfers Peru	Bank Transfer	Hosted Payment Page, Backend API
Card Payments Peru	Cards	Hosted Payment Page
Cash Payments Peru	Convenience Store Payments (OTC)	Hosted Payment Page, Backend API
PayPal Peru	E-Wallet	Hosted Payment Page

### Uruguay🇺🇾 > 🚧 Cash Payment Uruguay > > Channel paused since 9th June 2023 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Uruguay	Cards	Hosted Payment Page
Cash Payment Uruguay	Convenience Store Payments (OTC)	Hosted Payment Page

*** ## Europe ### Austria🇦🇹

Payment Channel	Type	Supported API Integration
EPS	Bank Transfer	Hosted Payment Page
Google Pay Apple Pay Austria	E-Wallet	Hosted Payment Page
Card Payments Austria	Cards	Hosted Payment Page
PayPal Austria	E-Wallet	Hosted Payment Page

### Belgium🇧🇪

Payment Channel	Type	Supported API Integration
Bancontact	E-Wallet	Hosted Payment Page
Google Pay Apple Pay Belgium	E-Wallet	Hosted Payment Page
Card Payments Belgium	Cards	Hosted Payment Page
PayPal Belgium	E-Wallet	Hosted Payment Page

### Czech Republic🇨🇿

Payment Channel	Type	Supported API Integration
Card Payments Czech Republic	Cards	Hosted Payment Page
Google Pay Apple Pay Czech Republic	E-Wallet	Hosted Payment Page
PayPal Czech Republic	E-Wallet	Hosted Payment Page

### Denmark🇩🇰

Payment Channel	Type	Supported API Integration
MobilePay	E-Wallet	Hosted Payment Page
Google Pay Apple Pay Denmark	E-Wallet	Hosted Payment Page
Card Payments Denmark	Cards	Hosted Payment Page
PayPal Denmark	E-Wallet	Hosted Payment Page

### France🇫🇷

Payment Channel	Type	Supported API Integration
Card Payments France	Cards	Hosted Payment Page
Google Pay Apple Pay France	E-Wallet	Hosted Payment Page
PayPal France	E-Wallet	Hosted Payment Page

### Finland🇫🇮

Payment Channel	Type	Supported API Integration
PayPal Finland	E-Wallet	Hosted Payment Page
Card Payments Finland	Cards	Hosted Payment Page

### Germany🇩🇪 > 🚧GiroPay > > Channel paused since 26th April 2024 until further notice.

Payment Channel	Type	Supported API Integration
Card Payments Germany	Cards	Hosted Payment Page
GiroPay	Bank Transfer	Hosted Payment Page
Google Pay Apple Pay Germany	E-Wallet	Hosted Payment Page
Paypal Germany	E-Wallet	Hosted Payment Page, Backend API
PaysafeCard Germany	Voucher	Hosted Payment Page

### Greece🇬🇷

Payment Channel	Type	Supported API Integration
PayPal Greece	E-Wallet	Hosted Payment Page
Card Payments Greece	Cards	Hosted Payment Page

### Hungary🇭🇺

Payment Channel	Type	Supported API Integration
Card Payments Hungary	Cards	Hosted Payment Page
Google Pay Apple Pay Hungary	E-Wallet	Hosted Payment Page
PayPal Hungary	E-Wallet	Hosted Payment Page

### Ireland🇮🇪

Payment Channel	Type	Supported API Integration
PayPal Ireland	E-Wallet	Hosted Payment Page
Card Payments Ireland	Cards	Hosted Payment Page

### Italy🇮🇹

Payment Channel	Type	Supported API Integration
Card Payments Italy	Cards	Hosted Payment Page
Google Pay Apple Pay Italy	E-Wallet	Hosted Payment Page
PayPal Italy	E-Wallet	Hosted Payment Page

### Netherlands🇳🇱

Payment Channel	Type	Supported API Integration
Card Payments Netherlands	Cards	Hosted Payment Page
iDeal	Bank Transfer	Hosted Payment Page
Google Pay Apple Pay Netherlands	E-Wallet	Hosted Payment Page
Paypal Netherlands	E-Wallet	Hosted Payment Page

### Norway🇳🇴

Payment Channel	Type	Supported API Integration
Vipps	E-Wallet	Hosted Payment Page
Google Pay Apple Pay Norway	E-Wallet	Hosted Payment Page
Card Payments Norway	Cards	Hosted Payment Page
PayPal Norway	E-Wallet	Hosted Payment Page

### Poland🇵🇱

Payment Channel	Type	Supported API Integration
BLIK	Bank Transfer	Hosted Payment Page
Card Payments Poland	Cards	Hosted Payment Page
Google Pay Apple Pay Poland	E-Wallet	Hosted Payment Page
Paypal Poland	Wallet	Hosted Payment Page

### Portugal🇵🇹 | Payment Channel | Type | Supported API Integration | | ----------------------------- | -------------------------------- | ------------------------- | | Multibanco | Convenience Store Payments (OTC) | Hosted Payment Page | | Google Pay Apple Pay Portugal | E-Wallet | Hosted Payment Page | | Card Payments Portugal | Cards | Hosted Payment Page | | PayPal Portugal | E-Wallet | Hosted Payment Page | ### Romania🇷🇴

Payment Channel	Type	Supported API Integration
Card Payments Romania	Cards	Hosted Payment Page
Google Pay Apple Pay Romania	E-Wallet	Hosted Payment Page
PayPal Romania	E-Wallet	Hosted Payment Page

### Slovakia🇸🇰

Payment Channel	Type	Supported API Integration
PayPal Slovakia	E-Wallet	Hosted Payment Page
Card Payments Slovakia	Cards	Hosted Payment Page

### Spain🇪🇸

Payment Channel	Type	Supported API Integration
Card Payments Spain	Cards	Hosted Payment Page
Google Pay Apple Pay Spain	E-Wallet	Hosted Payment Page
PayPal Spain	E-Wallet	Hosted Payment Page

### Switzerland🇨🇭

Payment Channel	Type	Supported API Integration
TWINT	E-Wallet	Hosted Payment Page
Google Pay Apple Pay Switzerland	E-Wallet	Hosted Payment Page
Card Payments Switzerland	Cards	Hosted Payment Page
PayPal Switzerland	E-Wallet	Hosted Payment Page

### Sweden🇸🇪

Payment Channel	Type	Supported API Integration
Trustly	Bank Transfer	Hosted Payment Page
Google Pay Apple Pay Sweden	E-Wallet	Hosted Payment Page
Card Payments Sweden	Cards	Hosted Payment Page
PayPal Sweden	E-Wallet	Hosted Payment Page

### United Kingdom🇬🇧

Payment Channel	Type	Supported API Integration
Card Payments UK	Cards	Hosted Payment Page
Google Pay Apple Pay UK	E-Wallet	Hosted Payment Page
PayPal UK	E-Wallet	Hosted Payment Page

**Documentation Note**: Geographical labels and API parameters (such as `country_code`) are based on ISO 3166-1 standards to ensure compatibility with global banking and payment networks. Across our documentation and systems, these identifiers are used strictly for technical routing and to designate operational markets. # Hosted Payment Page ## Asia ### Australia🇦🇺

Payment Channel	payType
Card Payments Australia	442
Google Pay Apple Pay Australia	897
PayPal Australia	771

### Bangladesh🇧🇩

Payment Channel	payType
bKash	470
Robi Airtel	63
Nagad	680

### Cambodia🇰🇭 | Payment Channel | payType | | ---------------------- | ------- | | Bakong (KHQR) | 454 | | Card Payments Cambodia | 419 | | Cellcard | 122 | | Metfone | 123 | | Smart Axiata | 121 | | Paygo | 452 | | PiPay | 451 | | Wing | 450 | ### Hong Kong🇭🇰 | Payment Channel | payType | | ------------------------------ | ------- | | Alipay Hong Kong | 311 | | Card Payments Hong Kong | 431 | | WeChat Pay Hong Kong | 312 | | Google Pay Apple Pay Hong Kong | 861 | | FPS | 313 | | PayPal Hong Kong | 777 | ### India 🇮🇳

Payment Channel	payType
UPI	391

### Indonesia🇮🇩 | Payment Channel | payType | | ------------------------ | ------- | | Alfamart | 221 | | Bank Transfers Indonesia | 220 | | Card Payments Indonesia | 400 | | DANA | 240 | | DOKU Wallet | 223 | | GO-PAY | 227 | | Indomaret | 226 | | Indosat | 22 | | LinkAja | 234 | | OVO | 230 | | QRIS | 906 | | ShopeePay Indonesia | 233 | | Smartfren | 27 | | Telkomsel | 24 | | Tri Indonesia | 26 | | XL | 23 | | PayPal Indonesia | 769 | ### Iraq🇮🇶 | Payment Channel | payType | | --------------- | ------- | | Zain Iraq | 169 | ### Japan🇯🇵 | Payment Channel | payType | | -------------------------- | ------- | | Card Payments Japan | 407 | | Google Pay Apple Pay Japan | 911 | | PayPay | 371 | | PayPal Japan | 767 | ### Kazakhstan🇰🇿 | Payment Channel | payType | | ------------------------ | ------- | | Card Payments Kazakhstan | 441 | ### Laos🇱🇦 | Payment Channel | payType | | ------------------ | ------- | | Card Payments Laos | 420 | | Lao Telecom | 132 | | Unitel Laos | 131 | ### Malaysia🇲🇾 | Payment Channel | payType | | ----------------------------- | ------- | | Maxis | 50 | | Boost | 238 | | Card Payments Malaysia | 421 | | Celcom | 52 | | Digi | 51 | | GrabPay Malaysia | 236 | | MAE / DuitNow | 242 | | ShopeePay Malaysia | 241 | | Touch-NGo | 237 | | U Mobile | 53 | | Google Pay Apple Pay Malaysia | 862 | ### Mongolia🇲🇳 | Payment Channel | payType | | --------------- | ------- | | MonPay | 650 | | Unitel Mongolia | 190 | | Toki | 649 | ### Myanmar🇲🇲 | Payment Channel | payType | | --------------------- | ------- | | ATOM | 101 | | Card Payments Myanmar | 411 | | MPT | 103 | | U9 | 102 | | WavePay | 380 | | KBZPay | 383 | | easyPoints | 382 | ### Nepal🇳🇵 | Payment Channel | payType | | --------------- | ------- | | E-Pay | 398 | ### **New Zealand🇳🇿** | Payment Channel | payType | | -------------------------------- | ------- | | Google Pay Apple Pay New Zealand | 883 | | Card Payments New Zealand | 443 | | PayPal New Zealand | 795 | ### Pakistan🇵🇰 | Payment Channel | payType | | ---------------------- | ------- | | Easypaisa | 394 | | Jazzcash | 395 | | Nayapay | 399 | | Telenor Pakistan | 61 | | Ufone | 62 | | Card Payments Pakistan | 1009 | | HBL Konnect | 389 | | Bank Transfer Pakistan | 388 | ### Philippines🇵🇭 | Payment Channel | payType | | -------------------------------- | ------- | | 7-Eleven Philippines | 253 | | Bank Transfers Philippines | 250 | | Card Payments Philippines | 410 | | Cash at Retail ex 7-Eleven PH | 251 | | Coins.ph | 258 | | GCash | 252 | | GrabPay Philippines | 255 | | Maya | 257 | | Smart | 91 | | Dito | 92 | | Google Pay Apple Pay Philippines | 864 | | PayPal Philippines | 775 | ### Singapore🇸🇬 | Payment Channel | payType | | ----------------------- | ------- | | Card Payments Singapore | 427 | | GrabPay Singapore | 260 | | PayNow | 263 | | SingTel | 40 | | PayPal Singapore | 264 | ### South Korea🇰🇷 | Payment Channel | payType | | --------------------------- | ------- | | Card Payments South Korea | 408 | | Carrier Billing South Korea | 175 | | KakaoPay | 690 | | Naver Pay | 693 | | Culture Voucher | 695 | | Payco | 694 | | T-Money | 696 | | Happymoney | 697 | ### Sri Lanka🇱🇰 | Payment Channel | payType | | ----------------------- | ------- | | Card Payments Sri Lanka | 414 | | Dialog | 60 | ### Taiwan | Payment Channel | payType | | --------------------------- | ------- | | Chunghwa Telecom | 82 | | FarEasTone | 81 | | GASH Gift Card | 300 | | JKO Pay | 302 | | Line Pay | 301 | | Taiwan Mobile | 80 | | Card Payments Taiwan | 428 | | PayPal Taiwan | 772 | | GASH e-wallet | 303 | | Google Pay Apple Pay Taiwan | 1204 | ### Thailand🇹🇭 | Payment Channel | payType | | ------------------------------------ | ------- | | 7-Eleven Thailand | 344 | | AIS | 71 | | Bank Transfers and Cash at Retail TH | 331 | | Card Payments Thailand | 413 | | dtac | 70 | | K PLUS | 348 | | One-2-Call Cash Card | 347 | | PromptPay | 349 | | Rabbit LINE Pay | 332 | | ShopeePay Thailand | 346 | | TrueMoney Cash Card | 340 | | True Money Wallet | 342 | | Truemove H | 73 | | PayPal Thailand | 773 | ### Timor Leste🇹🇱 | Payment Channel | payType | | --------------- | ------- | | Telemor | 170 | ### Vietnam🇻🇳 | Payment Channel | payType | | --------------------- | ------- | | Card Payments Vietnam | 416 | | VTCPay | 352 | | MoMo E-Wallet | 351 | | PayPal Vietnam | 776 | *** ## Middle East ### Bahrain🇧🇭 | Payment Channel | payType | | --------------- | ------- | | Zain Bahrain | 150 | | Benefit | 720 | ### Egypt🇪🇬 | Payment Channel | payType | | -------------------- | ------- | | Card Payments Egypt | 417 | | Fawry | 337 | | Masary, Aman, Momken | 751 | | Meeza Card Payments | 750 | | Orange Money | 339 | | Vodafone Cash | 338 | | PayPal Egypt | 766 | ### Kuwait🇰🇼 | Payment Channel | payType | | --------------------------- | ------- | | Zain Kuwait | 160 | | KNET & Card Payments Kuwait | 475 | ### Qatar🇶🇦 | Payment Channel | payType | | ------------------- | ------- | | Card Payments Qatar | 439 | | PayPal Qatar | 855 | ### Saudi Arabia🇸🇦 | Payment Channel | payType | | -------------------------- | ------- | | Card Payments Saudi Arabia | 412 | | Mada | 730 | | STC Pay | 702 | | Mobily | 163 | | Apple Pay Saudi Arabia | 731 | | PayPal Saudi Arabia | 765 | ### Turkey🇹🇷 | Payment Channel | payType | | -------------------- | ------- | | Papara | 653 | | Card Payments Turkey | 425 | | Bank Transfer Turkey | 651 | ### United Arab Emirates (UAE)🇦🇪 | Payment Channel | payType | | ---------------------------------- | ------- | | Card Payments United Arab Emirates | 418 | | PayBy | 701 | | Etisalat | 140 | | PayPal United Arab Emirates | 783 | *** ## Africa ### Morocco🇲🇦 | Payment Channel | payType | | --------------------- | ------- | | Card Payments Morocco | 426 | ### Nigeria🇳🇬 | Payment Channel | payType | | ---------------------- | ------- | | Paga | 920 | | Verve Card | 603 | | Bank Transfers Nigeria | 600 | | Opay Wallet | 922 | | Card Payments Nigeria | 433 | ### South Africa🇿🇦 | Payment Channel | payType | | --------------------------- | ------- | | Bank Transfers South Africa | 601 | | Card Payments South Africa | 432 | | 1Voucher | 602 | ### Kenya🇰🇪 | Payment Channel | payType | | --------------- | ------- | | M-PESA | 1300 | *** ## North America ### Canada🇨🇦 | Payment Channel | payType | | --------------------------- | ------- | | Card Payments Canada | 430 | | Google Pay Apple Pay Canada | 866 | | PayPal Canada | 768 | ### United States of America🇺🇸 | Payment Channel | payType | | ----------------------------------------------------------------- | ------- | |

Card Payments US
(Visa, Mastercard & American Express)

| 1006 | | Google Pay Apple Pay US | 898 | | Cash App | 899 | | PayPal US | 780 | ## Latin America ### Argentina🇦🇷 | Payment Channel | payType | | ----------------------- | ------- | | Card Payments Argentina | 424 | | Mercado Pago Argentina | 526 | | Pago Facil | 504 | | Rapipago | 505 | ### Bolivia🇧🇴 | Payment Channel | payType | | --------------------- | ------- | | Cash Payments Bolivia | 515 | | Card Payments Bolivia | 472 | ### Brazil🇧🇷 | Payment Channel | payType | | --------------------- | ------- | | Bank Transfers Brazil | 501 | | Boleto | 500 | | Card Payments Brazil | 422 | | Mercado Pago | 517 | | PicPay | 508 | | Pix | 516 | | PayPal Brazil | 510 | ### Chile🇨🇱 | Payment Channel | payType | | -------------------- | ------- | | Bank Transfers Chile | 513 | | Card Payments Chile | 435 | | PayPal Chile | 785 | ### Colombia🇨🇴 | Payment Channel | payType | | ----------------------- | ------- | | Card Payments Colombia | 436 | | DaviPlata | 527 | | Nequi | 528 | | Bank Transfers Colombia | 511 | | PayPal Colombia | 786 | | Google Pay / Apple Pay | 884 | ### Ecuador🇪🇨 | Payment Channel | payType | | --------------------- | ------- | | Card Payments Ecuador | 438 | | Cash Payments Ecuador | 519 | | PayPal Ecuador | 854 | ### Mexico🇲🇽 | Payment Channel | payType | | --------------------------- | ------- | | Bank Transfer Mexico | 503 | | Card Payments Mexico | 423 | | Mercado Pago Mexico | 524 | | Oxxo Pay | 523 | | PaysafeCard Mexico | 509 | | toditoCash | 525 | | Google Pay Apple Pay Mexico | 870 | | PayPal Mexico | 764 | | OXXO | 502 | ### Paraguay🇵🇾 | Payment Channel | payType | | ---------------------- | ------- | | Card Payments Paraguay | 440 | ### Peru🇵🇪 | Payment Channel | payType | | ------------------- | ------- | | Bank Transfers Peru | 770 | | Card Payments Peru | 437 | | Cash Payments Peru | 753 | | PayPal Peru | 789 | ### Uruguay🇺🇾 | Payment Channel | payType | | --------------------- | ------- | | Card Payments Uruguay | 434 | | Cash Payment Uruguay | 521 | *** ## Europe ### Austria🇦🇹 | Payment Channel | payType | | ---------------------------- | ------- | | EPS | 904 | | Google Pay Apple Pay Austria | 868 | | Card Payments Austria | 473 | | PayPal Austria | 788 | ### Belgium🇧🇪 | Payment Channel | payType | | ---------------------------- | ------- | | Bancontact | 905 | | Google Pay Apple Pay Belgium | 871 | | Card Payments Belgium | 455 | | PayPal Belgium | 784 | ### Czech Republic🇨🇿 | Payment Channel | payType | | ----------------------------------- | ------- | | Card Payments Czech Republic | 446 | | Google Pay Apple Pay Czech Republic | 872 | | PayPal Czech Republic | 798 | ### Denmark🇩🇰 | Payment Channel | payType | | ---------------------------- | ------- | | MobilePay | 908 | | Google Pay Apple Pay Denmark | 873 | | Card Payments Denmark | 459 | | PayPal Denmark | 794 | ### France🇫🇷 | Payment Channel | payType | | --------------------------- | ------- | | Card Payments France | 1002 | | Google Pay Apple Pay France | 859 | | PayPal France | 754 | ### Finland🇫🇮 | Payment Channel | payType | | --------------------- | ------- | | PayPal Finland | 796 | | Card Payments Finland | 463 | ### Germany🇩🇪 | Payment Channel | payType | | ---------------------------- | ------- | | Card Payments Germany | 1007 | | GiroPay | 900 | | Google Pay Apple Pay Germany | 874 | | Paypal Germany | 762 | | PaysafeCard Germany | 518 | ### Greece🇬🇷 | Payment Channel | payType | | -------------------- | ------- | | PayPal Greece | 790 | | Card Payments Greece | 456 | ### Hungary🇭🇺 | Payment Channel | payType | | ---------------------------- | ------- | | Card Payments Hungary | 444 | | Google Pay Apple Pay Hungary | 875 | | PayPal Hungary | 851 | ### Ireland🇮🇪 | Payment Channel | payType | | --------------------- | ------- | | PayPal Ireland | 799 | | Card Payments Ireland | 464 | ### Italy🇮🇹 | Payment Channel | payType | | -------------------------- | ------- | | Card Payments Italy | 1001 | | Google Pay Apple Pay Italy | 876 | | PayPal Italy | 755 | ### Netherlands🇳🇱 | Payment Channel | payType | | -------------------------------- | ------- | | Card Payments Netherlands | 1003 | | iDeal | 901 | | Google Pay Apple Pay Netherlands | 877 | | Paypal Netherlands | 756 | ### Norway🇳🇴

Payment Channel	payType	Backend API Integration
Vipps	909	Not Available
Google Pay Apple Pay Norway	878	Not Available
Card Payments Norway	458	Not Available
PayPal Norway	793	Not Available

### Poland🇵🇱 | Payment Channel | payType | | --------------------------- | ------- | | BLIK | 903 | | Card Payments Poland | 1005 | | Google Pay Apple Pay Poland | 879 | | Paypal Poland | 758 | ### Portugal🇵🇹 | Payment Channel | payType | | ----------------------------- | ------- | | Multibanco | 910 | | Google Pay Apple Pay Portugal | 880 | | Card Payments Portugal | 457 | | PayPal Portugal | 792 | ### Romania🇷🇴 | Payment Channel | payType | | ---------------------------- | ------- | | Card Payments Romania | 445 | | Google Pay Apple Pay Romania | 881 | | PayPal Romania | 787 | ### Slovakia🇸🇰 | Payment Channel | payType | | ---------------------- | ------- | | PayPal Slovakia | 857 | | Card Payments Slovakia | 471 | ### Spain🇪🇸 | Payment Channel | payType | | -------------------------- | ------- | | Card Payments Spain | 1000 | | Google Pay Apple Pay Spain | 882 | | PayPal Spain | 759 | ### Switzerland🇨🇭 | Payment Channel | payType | | -------------------------------- | ------- | | TWINT | 902 | | Google Pay Apple Pay Switzerland | 867 | | Card Payments Switzerland | 448 | | PayPal Switzerland | 781 | ### Sweden🇸🇪 | Payment Channel | payType | | --------------------------- | ------- | | Trustly | 907 | | Google Pay Apple Pay Sweden | 869 | | Card Payments Sweden | 449 | | PayPal Sweden | 782 | ### United Kingdom🇬🇧 | Payment Channel | payType | | ----------------------- | ------- | | Card Payments UK | 1004 | | Google Pay Apple Pay UK | 865 | | PayPal UK | 760 | # Special Payment Channels This page lists the channels that require special remarks/configuration, please take note. ## Channel List

Countries/Regions	Channels	Type	Description
Indonesia	Telkomsel	DCB	This channel has strict price and SKU parameters restrictions. Before applying to go live on this channel, you need to fill out the price application form (Telkomsel submissionv2.xlsx). Provide appropriate information as required, and Coda tech team submits the channel for approval before it can enter production testing and go live.
Cambodia	Metfone	DCB	Please contact Coda tech or business team to submit for review and approval by the channel in order perform production test and launch.
Thailand	Shopeepay Thailand	E-wallet	Please contact Coda tech or business team to submit for review and approval by the channel in order perform production test and launch.
Thailand	One-2-Call Cash Card True Money Cash Card	Cash card	Merchants must set up price verification。 For more info, please refer to "Special Notes for Accessing Point Card Channels".
Pakistan	Telenor Pakistan	DCB	Please contact Coda tech or business team to submit for review and approval by the channel in order perform production test and launch.
Bangladesh	Robi Airtel	DCB	Please contact Coda tech or business team to submit for review and approval by the channel in order perform production test and launch.
Vietnam	VTC	E-wallet	VTCPay channels are required to apply for activation approval title by title. Kindly reach out Coda Business for more information.
Vietnam	Momo	E-wallet	Momo channels are required to apply for activation approval title by title. Kindly reach out Coda Business for more information.
Myanmar	U9	DCB	U9 channels are required to apply for activation approval title by title. Kindly reach out Coda Business for more information.
Saudi Arabia	Apple Pay Saudi Arabia	E-wallet	This channel is limited open payment page in mobile version, using web browser will return `error 242`
Saudi Arabia	Mobily	Carrier Billing	Mobily identifies each transaction order using productId. Prior to launch, please review this information and reach out to Coda Support Team for assistance with configuration.

## Important Note for Voucher (Cash Card) Channel Please take note that **True Money Cash Card** and **One-2-Call Cash Card**, are the point in the transaction where Coda notifies you of the value of the voucher that was redeemed. Your system should interpret the value indicated in the net\_amount parameter of the notification URL and distribute an appropriate amount of game credits that corresponds with the value of the voucher the customer redeemed. Because Coda cannot block customers from redeeming particular voucher denominations, merchants are required to support the redemption of each denomination/price point in which the voucher is distributed 100 THB Please do the above if it is not done as we don’t have a case where the user purchases a 50 THB card and is able to receive a 100 THB in-game item. # Backend API ### Channel Details (Pay Type, Pay At, Pay Channel, and Mandatory fields) Below is a summary of each channel we support for Backend API integration. Along with the payment type details (Pay Type, Pay At, Pay Channel, and mandatory fields) for each country/region, the list is provided below. ## Asia ### Bangladesh

Payment Channel Name	Pay Type	Pay At	mno_code	Mandatory fields
Robi Airtel	1	N/A	47002	N/A

### Cambodia

Payment Channel Name	Pay Type	Pay At	mno_code	Mandatory fields
Smart Axiata	1	N/A	45605	MSISDN

### Hong Kong

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
AliPay Hong Kong	5	N/A	-143	N/A
WeChat Pay Hong Kong	5	N/A	-144	N/A

### Indonesia

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Alfamart	3	14	55	Full Name
Bank Transfer Indonesia (BCA)	2	5	1	Full Name
Bank Transfer Indonesia (BRI)	2	5	2	Full Name
Bank Transfer Indonesia (BII)	2	5	3	Full Name
Bank Transfer Indonesia (BNI)	2	5	4	Full Name
Bank Transfer Indonesia (CIMB)	2	5	5	Full Name
Bank Transfer Indonesia (Mandiri)	2	5	6	Full Name
Bank Transfer Indonesia (Permata)	2	5	7	Full Name
Bank Transfer Indonesia (Danamon)	2	5	248	Full Name
Bank Transfer Indonesia (VA Doku)	2	5	243	Full Name
Bank Transfer Indonesia (Other)	2	5	8	Full Name
Bank Transfer Indonesia (Mobile Banking BCA)	2	5	9	Full Name
Bank Transfer Indonesia (Mobile Banking BRI)	2	5	12	Full Name
Bank Transfer Indonesia (Mobile Banking BII)	2	5	13	Full Name
Bank Transfer Indonesia (Mobile Banking BNI)	2	5	14	Full Name
Bank Transfer Indonesia (Mobile Banking CIMB)	2	5	15	Full Name
Bank Transfer Indonesia (Mobile Banking Mandiri)	2	5	16	Full Name
Bank Transfer Indonesia (Mobile Banking Permata)	2	5	17	Full Name
Bank Transfer Indonesia (Mobile Banking Other Banks)	2	5	18	Full Name
QRIS	2	5	236	Full Name
DANA	5	N/A	19	N/A
DOKU Wallet	5	N/A	-63	N/A
GO-PAY	5	N/A	-69	user_id
Indomaret	3	14	77	N/A
Indosat	1	N/A	mno_code: 51001	MSISDN
LinkAja	5	N/A	39	N/A
OVO	5	N/A	20	MSISDN
ShopeePay Indonesia	5	N/A	40	N/A
Telkomsel	1	N/A	51010	MSISDN
Tri Indonesia	1	N/A	51089	MSISDN
XL	1	N/A	51008	MSISDN

### Laos

Payment Channel Name	Pay Type	Pay At	mno_code	Mandatory fields
Unitel Laos	1	N/A	45703	N/A

### Malaysia

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Boost	5	N/A	-88	Email
GrabPay	5	N/A	-74	N/A
MAE / DuitNow	2	N/A	-130	N/A
ShopeePay Malaysia	5	N/A	200	N/A
Touch-NGo	5	N/A	-77	N/A

### Myanmar

Payment Channel Name	Pay Type	Pay At	pay_channel	mno_code	Mandatory fields
ATOM	1	N/A		41406	MSISDN
U9	1	N/A		41405	MSISDN
KBZPay	1	5	95	N/A

### Nepal

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
E-Pay	5	N/A	126	N/A

### Pakistan

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Telenor Pakistan	1	N/A	mno_code: 52586	MSISDN

### Philippines

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
7-Eleven Philippines	3	14	67	Payment Agent, Email
Bank Transfers Philippines(Metrobank)	2	5	41	Bank, Email
Bank Transfers Philippines(BPI)	2	5	42	Bank, Email
Bank Transfers Philippines(PNB)	2	5	43	Bank, Email
Bank Transfers Philippines(BDO)	2	5	44	Bank, Email
Bank Transfers Philippines(RCBC)	2	5	45	Bank, Email
Bank Transfers Philippines(Chinabank)	2	5	46	Bank, Email
Bank Transfers Philippines(UCPB)	2	5	47	Bank, Email
Bank Transfers Philippines(Security Bank)	2	5	48	Bank, Email
Bank Transfers Philippines(Union Bank)	2	5	49	Bank, Email
Bank Transfers Philippines(EastWest)	2	5	50	Bank, Email
Bank Transfers Philippines(Maybank)	2	5	51	Bank, Email
Bank Transfers Philippines(Sterling Bank)	2	5	52	Bank, Email
Bank Transfers Philippines(Landbank)	2	5	75	Bank, Email
Coins.ph	5	5	-61	N/A
GCash	5	5	68	N/A
Maya	5	5	96	N/A

### Singapore

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
GrabPay Singapore	5	N/A	-76	N/A

### Taiwan

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Chunghwa Telecom	1	N/A	mno_code: 46692, 46611	N/A
FarEasTone	1	N/A	mno_code46602, 46607, 46601, 46606, 46603	N/A
GASH Gift Card	4	N/A	300	N/A
JKO Pay	5	N/A	-142	Email
Line Pay	5	N/A	-100	Email

### Thailand

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
7-Eleven TH	3	14	344	Full Name, Email, MSISDN
Cash at Retails(Big C Supercenter)	3	14	21	Email
Cash at Retails(Family Mart)	3	14	22	Email
Cash at Retails(MPAY)	3	14	23	Email
Cash at Retails(Thailand Post)	3	14	24	Email
Cash at Retails(TESCO Lotus)	3	14	25	Email
Cash at Retails(TOT Just Pay)	3	14	26	Email
Cash at Retails(TrueMoney Express)	3	14	27	Email
Cash at Retails(CenPay)	3	14	37	Email
Bank Transfer Thailand(Bank of Ayudhya)	2	2	28	Email
Bank Transfer Thailand (Bangkok Bank)	2	2	29	Email
Bank Transfer Thailand(CIMB)	2	2	30	Email
Bank Transfer Thailand(Kasikornbank)	2	2	31	Email
Bank Transfer Thailand(Krungthai Bank)	2	2	32	Email
Bank Transfer Thailand(Siam Commercial Bank)	2	2	33	Email
K PLUS	5	5	-200	MSISDN
One-2-Call Cash Card	4	N/A	-128	N/A
PromptPay	5	5	-129	N/A
Rabbit LINE Pay	5	5	-65	N/A
ShopeePay Thailand	5	5	-89	N/A

## Middle East ### Turkey

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Papara	5	N/A	239	N/A

### Bahrain

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Benefit	6	N/A	160	Email, Full Name

### Egypt

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Masary, Aman, Momken	3	N/A	-126	MSISDN, Email
Vodafone Cash	5	N/A	-102	MSISDN, Email

### Saudi Arabia

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Mada	6	N/A	241	N/A

### United Arab Emirates (UAE)

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
PayBy	5	N/A	-99	N/A

## Africa ### Nigeria

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Paga	5	N/A	237	Full Name, Email, MSISDN
Verve Card	6	N/A	-14	Email

### South Africa

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Bank Transfer South Africa	2	N/A	-61	N/A

## Latin America ### Argentina

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Mercado Pago Argentina	5	N/A	-67	N/A
Pago Facil	3	14	111	Email, Full name
Rapipago	3	14	112	N/A

### Brazil

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Mercado Pago	5	4	154	Full Name, CPF Number, Email, MSISDN
PicPay	5	4	98	Full Name, CPF Number, Email, MSISDN
Pix	2	5	153	Full Name, CPF Number, Email, MSISDN

### Colombia

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
DaviPlata	5	N/A	255	email, document_type (CC, CE, TI), document_number
Bank Transfer Colombia	2	2	279	email, name, id_type, id_doc_type, id_no, pay_channel id_type list: N("Persona Natural"), J("Persona Jurídica"); id_doc_type list: CC("Cédula de ciudadanía."), CE("Cédula de extranjería."), NIT("Número de identificación tributario."), TI("Tarjeta de identidad."), PP("Pasaporte."), IDC("Identificador único de cliente, para el caso de ID's únicos de clientes/usuarios de servicios públicos."), CEL("En caso de identificarse a través de la línea del móvil."), RC("Registro civil de nacimiento."), DE("Documento de identificación extranjero."), SE_NIT("Sociedad Extranjera sin Nit."), FIDE("Fideicomiso."), NIT_M("Nit Menores."), RIF_V("RIF Venezuela."), NIT_E("Nit Extranjería."), NIT_N("Nit Persona Natural."), C_DIP("Carnet Diplomático."), RUT("RUT."), CPF("Registro de personas físicas (Cadastro de Pessoas Físicas)."), CEDULAECU("Cedula Ecuador."), CEDULACOL("Cedula Colombia."); pay_channel list: 260 BAN100 261 BANCAMIA S.A. 262 BANCO AGRARIO 263 BANCO AV VILLAS 264 BANCO BBVA COLOMBIA S.A. 265 BANCO CAJA SOCIAL 266 BANCO COOPERATIVO COOPCENTRAL 267 BANCO DAVIVIENDA 268 BANCO DE BOGOTA 269 BANCO DE OCCIDENTE 270 BANCO FALABELLA 271 BANCO FINANDINA S.A. BIC 272 BANCO GNB SUDAMERIS 273 BANCO ITAU 274 BANCO PICHINCHA S.A. 275 BANCO POPULAR 276 BANCO SANTANDER COLOMBIA 277 BANCO SERFINANZA 278 BANCO UNION antes GIROS 279 BANCOLOMBIA 280 BANCOOMEVA S.A. 281 CFA COOPERATIVA FINANCIERA 282 CITIBANK 283 COLTEFINANCIERA 284 CONFIAR COOPERATIVA FINANCIERA 285 COOFINEP COOPERATIVA FINANCIERA 286 COTRAFA 287 DALE 288 DAVIPLATA 289 IRIS 290 LULO BANK 291 MOVII S.A. 292 NEQUI 293 RAPPIPAY 294 RAPPIPAY DAVIPLATA 295 SCOTIABANK COLPATRIA

### Mexico

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Card Payment Mexico	6	N/A	256	Name, Email, Msisdn
Bank Transfer Mexico(Bonarte)	2	5	110	Full name, NFC number, Email
Bank Transfer Mexico(BBVA Bancomer)	2	5	108	Full name, NFC number, Email
Bank Transfer Mexico(Santander)	2	5	109	Full name, NFC number, Email
Bank Transfer Mexico(SPEI)	2	5	107	Full name, NFC number, Email
Mercado Pago Mexico	5	N/A	-67	N/A
OXXO	3	14	106	N/A

### Peru

Payment Channel Name	Pay Type	Pay At	Pay Channel	Mandatory fields
Bank Transfer Peru(Banco BBVA Peru)	2	2	161	Full Name, Email
Bank Transfer Peru(Banco de Crédito del Perú)	2	2	162	Full Name, Email
Bank Transfer Peru(Interbank Perú)	2	2	163	Full Name, Email
Bank Transfer Peru(Banco Interamericano de Finanzas)	2	2	164	Full Name, Email
Bank Transfer Peru(Scotiabank Perú)	2	2	165	Full Name, Email
Bank Transfer Peru(Caja Arequipa)	2	2	166	Full Name, Email
Cash Payment Peru(KasNet)	3	14	138	Full Name, Email
Cash Payment Peru(BBVA Continental)	3	14	139	Full Name, Email
Cash Payment Peru(Red Digital)	3	14	140	Full Name, Email
Cash Payment Peru(Caja Arequipa)	3	14	141	Full Name, Email
Cash Payment Peru(MoneyGram)	3	14	142	Full Name, Email
Cash Payment Peru(Western Union)	3	14	143	Full Name, Email
Cash Payment Peru(Interbank)	3	14	144	Full Name, Email
Cash Payment Peru(Banco de Crédito)	3	14	145	Full Name, Email
Cash Payment Peru(Caja Arequipa)	3	14	146	Full Name, Email
Cash Payment Peru(Fullcarga)	3	14	147	Full Name, Email
Cash Payment Peru(Disashop)	3	14	148	Full Name, Email
Cash Payment Peru(BanBif)	3	14	149	Full Name, Email
Cash Payment Peru(Instores)	3	14	150	Full Name, Email
Cash Payment Peru(Scotiabank)	3	14	151	Full Name, Email

# Tokenization API 2.0 The following is a list of supported payment methods, each accompanied by its respective information:

Payment Method	Country	Currency	Status	Payment Method Type	One-click payment	Off-session payments (subscription/auto top-up)
GoPay	Indonesia	IDR	Live	gopay	Supported ✅	Coming soon!
Mada	Saudi Arabia	SAU	Live	Card	Supported ✅	Coming soon!
Dana	Indonesia	IDR	Live	dana	Supported ✅	Coming soon!

# Payment Channel Update This section will include all updates and announcements related to payment channel changes. # Channel Status This page will include all updates on channel status changes (Discontinued/Paused/Resumed).

Date	Country/Region	Payment Channel	Status
20th Aug 2026	Brazil	Bank Transfer Brazil	Paused
12nd Aug 2026	Malaysia	Maxis	Paused
11th Aug 2026	Bangladesh	bKash	Paused
28th Jul 2026	Kenya	M-PESA	Paused
31st Mar 2026	Myanmar	Card Payments Myanmar	Resumed
31st Mar 2026	Turkey	Card Payments Turkey	Resumed
2nd Mar 2026	Hong Kong	WeChat Pay Hong Kong	Resumed
2nd Mar 2026	Taiwan	Chunghwa Telecom	Resumed
21th Jan 2026	Taiwan	Chunghwa Telecom	Paused
16th Jan 2026	Laos	Unitel Laos	Paused
8th Jan 2026	Turkey	Card Payments Turkey	Paused
24th Dec 2025	Turkey	Bank Transfer Turkey	Paused
19th Dec 2025	Mexico	Todito Cash	Paused
10th Dec 2025	Taiwan	Paypal Taiwan	Paused
9th Dec 2025	Singapore	Singtel	Paused
2nd Aug 2025	Indonesia	Smartfren	Paused
11th Aug 2025	Hong Kong	WeChat Pay Hong Kong	Paused - Applies to non-gaming titles only
11th Aug 2025	UAE	Etisalat	Paused
1st Aug 2025	Singapore	M1	Discontinued
24th Jul 2025	Egypt	Fawry	Discontinued
18th Jun 2025	Turkey	Papara	Resumed
2nd Jun 2025	Philippines	PayPal Philippines	Paused
27th May 2025	Turkey	Papara	Paused
13th May 2025	Indonesia	Smartfren	Resumed
9th May 2025	Indonesia	Smartfren	Paused
5th May 2025	Egypt	Fawry	Paused
17th Apr 2025	Nepal	E-Pay	Paused
15th Apr 2025	Saudi Arabia	Mobily	Paused
24th Feb 2025	Bahrain	Benefit	Paused
6th Feb 2025	Kuwait	KNET	Paused
23rd Sept 2024	Brazil	Ame Digital	Discontinued
16th Jul 2024	Philippines	Globe	Discontinued
26th Apr 2024	Taiwan	Asia Pacific Telecom	Discontinued
22nd Apr 2024	Nigeria	1Voucher	Discontinued
27th Nov 2023	Hong Kong	PayMe	Discontinued
1st Sept 2023	Singapore	StaHub	Discontinued
14th Jun 2023	Thailand	Dolfin	Discontinued
27th Jul 2021	Malaysia	Digi Prepaid Reload Card	Discontinued

# Price Limit and Expiry Time This page will include all updates on channel price limits and expiry time changes. | Date | Country | Payment Channel | Change Details | | ------------- | -------------------- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | 13th Jun 2025 | Poland | Card Payments Poland |

New Minimum Price Point: PLN 2.44

Previous Minimum Price Point: PLN 2

New Minimum Price Point: GBP 0.5

Previous Minimum Price Point: GBP 1

New Minimum Price Point: KWD 0.2

Previous Minimum Price Point: KWD 0.1

New Minimum Price Point: BOB 4

Previous Minimum Price Point: BOB 4.50

New Minimum Price Point: EUR 0.6

Previous Minimum Price Point: EUR 0.5

New Minimum Price Point: EUR 0.6

Previous Minimum Price Point: EUR 0.5

New Minimum Price Point: DKK 4

Previous Minimum Price Point: DKK 0.5

New Minimum Price Point: NOK 6.60

Previous Minimum Price Point: NOK 5

New Minimum Price Point: AUD 1

Previous Minimum Price Point: AUD 0.6

New Minimum Price Point: TWD 19.50

Previous Minimum Price Point: TWD 12

New Minimum Price Point: SGD 0.84

Previous Minimum Price Point: SGD 0.5

New Minimum Price Point: MAD 5.99

Previous Minimum Price Point: MAD 4

New Maximum Price Point: ARS 999,999

Previous Maximum Price Point: ARS 500,000

New Maximum Price Point: PLN 26,000

Previous Maximum Price Point: PLN 999,999

New Maximum Price Point: PKR 999,999

Previous Maximum Price Point: PKR 130,000

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999

New Maximum Price Point: USD 9,999

Previous Maximum Price Point: USD 999,999

New Maximum Price Point: GBP 5,000

Previous Maximum Price Point: GBP 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999

New Maximum Price Point: KWD 2,000

Previous Maximum Price Point: KWD 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999.99

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: BOB 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: EUR 999,999.99

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: EUR 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: EUR 999,999

New Maximum Price Point: DKK 46,000

Previous Maximum Price Point: DKK 999,999

New Maximum Price Point: NOK 71,000

Previous Maximum Price Point: NOK 999,999

New Minimum Price Point: ARS 700

Previous Minimum Price Point: ARS 95,000

New Maximum Price Point: BRL 40,000

Previous Maximum Price Point: BRL 100,000

New Maximum Price Point: MYR 49,999.99

Previous Maximum Price Point: MYR 999,999.99

New Maximum Price Point: EGP 25,000

Previous Maximum Price Point: AED 999,999

New Maximum Price Point: EGP 350,000

Previous Maximum Price Point: EGP 999,999

New Minimum Price Point: LKR 200

Previous Minimum Price Point: LKR 162

New Maximum Price Point: THB 230,000

Previous Maximum Price Point: THB 999,999

New Maximum Price Point: SAR 27,000

Previous Maximum Price Point: SAR 999,999

New Minimum Price Point: MMK 1,500

Previous Minimum Price Point: MMK 810

New Maximum Price Point: PHP 400,000

Previous Maximum Price Point: PHP 999,999

New Maximum Price Point: IDR 110,000,000

Previous Maximum Price Point: IDR 78,000,000

New Maximum Price Point: EUR 26,000

Previous Maximum Price Point: EUR 999,999

New Maximum Price Point: EUR 6,000

Previous Maximum Price Point: EUR 999,999

New Maximum Price Point: SEK 67,000

Previous Maximum Price Point: SEK 999,999

New Maximum Price Point: CHF 7,000

Previous Maximum Price Point: CHF 999,999

New Maximum Price Point: CZK 150,000

Previous Maximum Price Point: CZK 999,999

New Maximum Price Point: HUF 2,486,000

Previous Maximum Price Point: HUF 999,999

New Maximum Price Point: NZD 11,000

Previous Maximum Price Point: NZD 999,999.99

New Maximum Price Point: AUD 10,000

Previous Maximum Price Point: AUD 999,999

New Maximum Price Point: QAR 25,000

Previous Maximum Price Point: QAR 999,999

New Maximum Price Point: USD 7,000

Previous Maximum Price Point: USD 999,999

New Maximum Price Point: SAR 27,000

Previous Maximum Price Point: SAR 999,999,999

New Minimum Price Point: CAD 0.5

Previous Minimum Price Point: CAD 0.1

New Minimum Price Point: PEN 2.5

Previous Minimum Price Point: PEN 1.5

New Maximum Price Point: COP 29,215,000.00

Previous Maximum Price Point: COP 999,999.99

New Minimum Price Point: CLP 600

Previous Minimum Price Point: CLP 300

New Minimum Price Point: UYU 25

Previous Minimum Price Point: UYU 16.5

New Maximum Price Point: ZAR 125,000

Previous Maximum Price Point: ZAR 999,999.99

New Maximum Price Point: HKD 54,000

Previous Maximum Price Point: HKD 999,999

New Maximum Price Point: CAD 9,000

Previous Maximum Price Point: CAD 999,999

New Maximum Price Point: TWD 209,000

Previous Maximum Price Point: TWD 999,999

New Maximum Price Point: MAD 64,000

Previous Maximum Price Point: MAD 999,999

New Maximum Price Point: SGD 9,999

Previous Maximum Price Point: SGD 999,999

New Maximum Price Point: IDR 1,200,000

Previous Maximum Price Point: IDR 1,000,000

New Minimum Price Point: PHP 6

Previous Minimum Price Point: PHP 0.01

New Maximum Price Point: EGP 25,000

Previous Maximum Price Point: EGP 9,500

New Minimum Price Point: ARS 95,000

Previous Minimum Price Point: ARS 400

New Maximum Price Point: IDR 510,000

Previous Maximum Price Point: IDR 500,000

New Minimum Price Point: THB 8,000

Previous Minimum Price Point: THB 5,000

New Minimum Price Point: IDR 10,000

Previous Minimum Price Point: IDR 6,000

New Minimum Price Point: EGP 18

Previous Minimum Price Point: EGP 30

New Minimum Price Point: NGN 800

Previous Minimum Price Point: NGN 700

New Maximum Price Point: KRW 999,999

Previous Maximum Price Point: KRW 1,000,000

New Minimum Price Point: VND 13,000

Previous Minimum Price Point: VND 8,558

New Minimum Price Point: SAR 750,000

Previous Minimum Price Point: SAR 1,000,000

New Maximum Price Point: PKR 750,000

Previous Maximum Price Point: PKR 1,000,000

New Maximum Price Point: PKR 750,000

Previous Maximum Price Point: PKR 1,000,000

| # New Channel Announcement This page will include all newly launched payment channels. # Pakistan - HBL Konnect {% hint style="success" %} What is Pakistan CNIC?\ Pakistan CNIC (Computerized National Identity Card) is a unique 13-digit ID issued to Pakistani citizens by NADRA. HBL Konnect requires CNIC to verify the identity of users when opening a digital wallet or branchless banking account. The CNIC ensures that the account is linked to a valid Pakistani citizen, enabling secure and compliant financial transactions such as money transfers, bill payments, mobile recharges, and government disbursements. Using CNIC helps HBL Konnect meet regulatory requirements and prevent fraud by authenticating users through their official national ID {% endhint %} ❗We are excited to introduce "HBL Konnect" our payment channel designed exclusively for Codapay users. With the inclusion of "HBL Konnect," we are proud to offer a seamless and convenient payment option with this local e-wallet payment. Here are some key details about this new payment option: 📱 e-wallet Channel: HBL Konnect is a platform allowing users to purchase their desired items with their familiar e-wallet. 💲 Price Point Limit: Refer [here](https://coda-payments.gitbook.io/coda-private-technical-documentation/references/price-point). CONTACT Business Development Team for further details. 🔒 Authentication: When proceeding with payment in HBL Konnect, it redirects users to the Pay checkout page, CNIC Number & MSISDN linked to wallet account are required to proceed with the payment. ⏰ Transaction Expiry: Please note that transactions made through HBL Konnect have a validity period of 15 minutes. Users may complete payment within this timeframe to ensure a successful transaction. 💻 Integration Details: For merchants and developers, please be aware that HBL Konnect integration supports the payment page API. Unfortunately, the Backend API integration is currently not available. We appreciate your understanding and cooperation in this matter. We encourage all our users to take advantage of this payment channel, leveraging an efficient payment experience. By incorporating "HBL Konnect" into our platform, we aim to provide a tailored and reliable payment solution that meets the specific needs of our users. **Flow Description**


	User selects HBL Konnect as a payment channel User is asked to enter their CNIC Number and MSISDN
	User enters OTP on OTP input screen
	Coda displays the pending page
	Payment completed

# United States - American Express ❗We are excited to introduce "American Express" our payment channel designed exclusively for Codapay users. With the inclusion of "American Express," we are proud to offer a seamless and convenient payment option with this local card payment. Here are some key details about this new payment option: 📱 card payment Channel: American Express is a platform allowing users to purchase their desired items with their familiar credit card. 💲 Price Point Limit: Refer [here](https://coda-payments.gitbook.io/coda-private-technical-documentation/references/price-point). CONTACT Business Development Team for further details. 🔒 Authentication: When proceeding with payment in American Express, it redirects users to the Pay checkout page, Zip Code & Credit Card information (Card number, Expiry date and CVC) are required to proceed with the payment. ⏰ Transaction Expiry: Please note that transactions made through American Express have a validity period of 15 minutes. Users may complete payment within this timeframe to ensure a successful transaction. 💻 Integration Details: For merchants and developers, please be aware that American Express integration supports the payment page API. Unfortunately, the Backend API integration is currently not available. We appreciate your understanding and cooperation in this matter. We encourage all our users to take advantage of this payment channel, leveraging an efficient payment experience. By incorporating "American Express" into our platform, we aim to provide a tailored and reliable payment solution that meets the specific needs of our users. **Flow Description** | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdTgLX3vcsed7toabQnasJTP_69p6zF637le8iKZsi8onKwae-QA_x8_LL3xWRp7f95WWYJcD4_HQ41YB7VYLMfAGGHlkDxEdB5u9RnXP8AK64V_WGJPvymvkwH9gwegNK2e1pM?key=BrlxDnmtC3GostSRxYVhIQ) |

User selects Card Payment as a payment option
Users inputs his zipcode information

| | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXd_dWm1QHkq7I3OnW7VpNPuRFfjhPww3yeCsRZa3kdT9FyGe2piIAliWKPsC2eECj4zOMmz6AZYFiq-N2S0Fs2iSWTYQCAAlT4y6ASsA237jgQKbyfaBHrK98k4ukMGA1adBjwz5Q?key=BrlxDnmtC3GostSRxYVhIQ) |

User sees payment summary including tax User enter’s card details and clicks on Pay Now button User does 3DS authentication and completes payment

| | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXca96jA8--mJILwmUfqfAH8wq8XzWXaAndAiL4G84eKHT407-N6mFljKCdRK47YujgoKut_Umx4e8iYhT-tFm2hsjvjn4Q0lyRC4SUuGPUo4_1tV4d5ztXDmQDv235wKi8O1u2gkg?key=BrlxDnmtC3GostSRxYVhIQ) |

Coda displays the pending page

| | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXeDCP9cfwx7Tv6j77Sd11h0QmqHt7PFoYjPlXJdB-ITPJwsVeLLvZBrqNdGVs0K4nsNJXDZ5ty_P4GKB6kOrvplbGMgUuVo8I1OVsFukRh6EvO5J0HfKkGv_aDtJHC-gGyo0UI?key=BrlxDnmtC3GostSRxYVhIQ) |

Payment completed

| # Colombia - Google / Apple Pay ❗We are excited to introduce "Google / Apple Pay" our payment channel designed exclusively for Codapay users. With the inclusion of "Google / Apple Pay," we are proud to offer a seamless and convenient payment option with this e-wallet payment. Here are some key details about this new payment option: 📱 e-wallet Channel: Google / Apple Pay is a platform allowing users to purchase their desired items with their familiar e-wallet. 💲 Price Point Limit: Refer [here](https://coda-payments.gitbook.io/coda-private-technical-documentation/references/price-point). CONTACT Business Development Team for further details. 🔒 Authentication: When proceeding with payment in Google / Apple Pay, it redirects users to the Pay checkout page, Credit Card linked to wallet account are required to proceed with the payment. ⏰ Transaction Expiry: Please note that transactions made through Google / Apple Pay have a validity period of 15 minutes. Users may complete payment within this timeframe to ensure a successful transaction. 💻 Integration Details: For merchants and developers, please be aware that Google / Apple Pay integration supports the payment page API. Unfortunately, the Backend API integration is currently not available. We appreciate your understanding and cooperation in this matter. We encourage all our users to take advantage of this payment channel, leveraging an efficient payment experience. By incorporating "Google / Apple Pay" into our platform, we aim to provide a tailored and reliable payment solution that meets the specific needs of our users. **Flow Description** | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXe_1xzshinVYr_qDJI6IULc91Y0pw14rY3yMNmoHXs17mRhwlwhc_9bSoFaje1aiTL-vkAWjTdm5zApY_rFN1yUd1ijPw0-nPNlAVSKAWfjYYSLta9sQ1ftU7ocyLHw_q1upQOmoQ?key=l7oUWm-DjsYe6X2NpEhKQg) |

User selects Google / Apple Pay as a payment channel
Coda displays the payment button (Google / Apple / Link depending on customer browser and other parameters)

| | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXeeO1XZS5u-BR6YCW7o6hS6FCUwuH4Hs2dIV3XOlqXN9V7qXCS2WKUtB35rS4rTT2Uz9MAaKEmveEjZc2TfgAPCgg95SowgOLIbGHo6SbkwJ8ah3grk0CqQo3BOSfIDFMyF5wX5uw?key=l7oUWm-DjsYe6X2NpEhKQg) |

User clicks on the payment button and proceeds with the payment

| | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXdhTbVPn9pmQ57WnU7CHkTKeYaGb4Sg8jRW9TIxGfMHC3mavr1Ao8k9UVPdzuh3MvZOOWYG5dEETWRSautpnR13sMPR-ZAURwamDXU_cFZMJK37o7IjX-FWitfBH8f9tDE1En6NbQ?key=l7oUWm-DjsYe6X2NpEhKQg) |

Coda displays the pending page

| | ![](https://lh7-rt.googleusercontent.com/docsz/AD_4nXfQSK1m8ZHf4PgA9RpK-tMbYEQhjrvkdB5W6ehIxC82uEkN511TUFp2rl3tcaUIp_syJSwS8OoIm_XDuK6WTrIm-aAPKhROGMpEwLDCfvwDI_LJrKak-hoRj3JfLDRm3zmiJ_msDg?key=l7oUWm-DjsYe6X2NpEhKQg) |

Payment completed

| CommentShare feedback on the editor # Price Limits {% hint style="info" %} **Note** * Please account for any per-transaction fees when setting low-value end-user prices. * Other Limits are for your information only, are enforced by Coda and/or the payment channel, also may change at any time. * For more information on payment channels that have been paused, please contact your Coda Business Team PIC. {% endhint %} ### Argentina | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------- | ------------------- | ------------------- | ----------------------------------------- | ------------------------------------- | ---------------------- | | Pago Facil | ARS 5 | ARS 112,797 | N/A | N/A | 3 day | | Rapipago | ARS 5 | ARS 112,797 | N/A | N/A | 5 day | | Card Payments Argentina | ARS 700 | ARS 999,999 | N/A | N/A | 20 min | | Mercado Pago | ARS 5 | ARS 112,797 | Max ARS 112,797 monthly limit per account | N/A | 2 hours | ### Austria | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | EPS | EUR 0.01 | EUR 1,000 | N/A | N/A | 30 min | | Google Pay Apple Pay Austria | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Austria | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | PayPal Austria | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | ### Australia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------------ | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Australia | AUD 1 | AUD 999,999 | N/A | N/A | 15 min | | Google Pay Apple Pay Australia | AUD 0.5 | AUD 500 | N/A | N/A | 15 min | | PayPal Australia | AUD 0.01 | AUD 999,999 | N/A | N/A | 15 min | ### Bahrain | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ------------------- | ------------------------------------- | ---------------------- | | Zain Bahrain | BHD 1 | BHD 30 | BHD 30/Month/MSISDN | N/A | 20 min | | Benefit | BHD 0.1 | BHD 700 | N/A | N/A | 10 min | ### Bangladesh | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | bKash | Tk 10 | Tk 50,000 | N/A | N/A | 10 min | | Robi Airtel | Tk 1 | Tk 2,000 | N/A | N/A | 15 min | | Nagad | Tk 10 | Tk 25,000 | N/A | N/A | 60 min | ### Brazil | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | --------------------------------------------- | ------------------------------------- | ---------------------- | | Boleto | BRL 1 | BRL 1100 | BRL 3,000/User/Month | N/A | 10 day | | Bank Transfer Brazil | BRL 1 | BRL 1100 | BRL 3,000/User/Month | N/A | 10 day | | Mercado Pago Brazil | BRL 0.01 | BRL 1000 | N/A | N/A | 24 hour | | PicPay | BRL 1 | BRL 25,000 | N/A | N/A | 24 hour | | Pix | BRL 0.15 | BRL 30,000 |

BRL
30,000/Month

| N/A | 24 hour | | Card Payments Brazil | BRL 0.1 | BRL 40,000 | N/A | N/A | 10 min | | PayPal Brazil | BRL 1 | BRL 999,999 | N/A | N/A | 10 min | ### Bolivia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Cash Payments Bolivia | Bs. 10 | Bs. 3,450 | N/A | N/A | 14 days | | Card Payments Bolivia | Bs. 0.10 | Bs. 48,000 | N/A | N/A | 15 min | ### Belgium | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Bancontact | EUR 0.02 | EUR 1,500 | N/A | N/A | 30 min | | Google Pay Apple Pay Belgium | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Belgium | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | PayPal Belgium | EUR 0.01 | EUR. 999,999 | N/A | N/A | 15 min | ### Cambodia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------- | ------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Smart Axiata | USD 0.5 | USD 1,000 | USD2,000/Month/MSISDN | N/A | 10 min | | Cellcard | N/A | N/A | N/A | N/A | 10 min | | Metfone | USD 0.01 | USD 200 |

Max amount:
USD 2000/Day,

Number of transaction:
10 transaction/Day/MSISDN

| N/A | 10 min | | Wing | USD 0.1 | USD 1,000 | N/A | N/A | 15 min | | PiPay | USD 0.01 | USD 300 | N/A | N/A | 20 min | | Paygo | USD 0.10 | USD 500 | N/A | N/A | 10 min | | Card Payments Cambodia | USD 0.50 | USD 999,999 | N/A | N/A | 15 min | | Bakong (KHQR) | USD 0.50 | USD 1,000 | USD 3,500 per day per customer | N/A | 13 min | ### Canada | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Canada | CAD 0.5 | CAD 9,000 | N/A | N/A | 10 min | | Google Pay Apple Pay Canada | CAD 0.5 | CAD 999,999 | N/A | N/A | 15 min | | PayPal Canada | CAD 0.01 | N/A | N/A | N/A | 15 min | ### Chile ✍️ Chilean payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Bank Transfers Chile | CLP 4 | CLP 6,700,000 | N/A | N/A | 48 h | | Card Payments Chile | CLP 600 | CLP 999,999 | N/A | N/A | 15 min | | PayPal Chile | CLP 10 | N/A | N/A | N/A | 15 min | ### Colombia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------------- | ------------------- | ------------------- | ------------------------- | ------------------------------------- | ---------------------- | | Card Payments Colombia | COP 2,100 | COP 29,215,000.00 | N/A | N/A | 15 min | | DaviPlata | COP 1,000 | COP 3,000,000 | Does not support decimals | N/A | 5 min | | Nequi | COP 5,000 | COP 5,000,000 | Does not support decimals | N/A | 30 min | | Bank Transfers Colombia | COP 3,700 | COP 17,000,000 | N/A | N/A | 25 min | | PayPal Colombia | COP 40 | COP 999,999 | N/A | N/A | 15 min | | Google Pay / Apple Pay Colombia | COP 2100 | COP 999,999 | Does not support decimals | N/A | 15 min | ### Czech Republic | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Czech Republic | CZK 15 | CZK 150,000 | N/A | N/A | 15 min | | Google Pay Apple Pay Czech Republic | CZK 13 | CZK 999,999 | N/A | N/A | 15 min | | PayPal Czech Republic | CZK 0.5 | CZK 999,999 | N/A | N/A | 15 min | ### Denmark | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | MobilePay | DKK 0.01 | DKK 1,000 | N/A | N/A | 28 Day | | Google Pay Apple Pay Denmark | DKK 4 | DKK 999,999 | N/A | N/A | 15 min | | Card Payments Denmark | DKK 0.5 | DKK 46,000 | N/A | N/A | 15 min | | PayPal Denmark | DKK 0.1 | DKK 999,999 | N/A | N/A | 15 min | ### Egypt | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Fawry | EGP 1 | EGP 300,000 | N/A | N/A | 24 hour | | Vodafone Cash | EGP 5 | EGP 105,000 | N/A | N/A | 65 min | | Masary, Aman, Momken | EGP 1 | EGP 1,000 | N/A | N/A | 25 hour | | Meeza Card Payments | EGP 1 | EGP 100,000 | N/A | N/A | 20 min | | Card Payments Egypt | EGP 30 | EGP 350,000 | N/A | N/A | 20 min | | Orange Money | EGP 5 | EGP 60,000 | N/A | N/A | 65 min | | PayPal Egypt | EGP 0.5 | EGP 25,000 | N/A | N/A | 10 min | ### Ecuador | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | --------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Cash Payments Ecuador | USD 0.5 | USD 700 |

Facilito USD 700
Others 300 USD

| N/A | 14 days | | Card Payments Ecuador | USD 0.5 | USD 7,000 | N/A | N/A | 15 min | | PayPal Ecuador | USD 0.01 | USD 999,999 | N/A | N/A | 15 min | ### France | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments France | EUR 0.5 | EUR 6,000 | N/A | N/A | 30 min | | Google Pay Apple Pay France | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | PayPal France | EUR 0.01 | EUR 999,999 | N/A | N/A | 11 min | ### Finland | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | PayPal Finland | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Finland | EUR 0.5 | EUR 6,000 | N/A | N/A | 15 min | ### Germany | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Germany | EUR 0.5 | EUR 6,000 | N/A | N/A | 30 min | | GiroPay | EUR 0.01 | EUR 1,000 | N/A | N/A | 30 min | | Google Pay Apple Pay Germany | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | Paypal Germany | EUR 0.01 | EUR 999,999 | N/A | N/A | 10 min | | PaysafeCard Germany | EUR 0.01 | EUR 1,000 | N/A | N/A | 30 min | ### Greece | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | PayPal Greece | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Greece | EUR 0.5 | EUR 6,000 | N/A | N/A | 15 min | ### Hong Kong | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------------ | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Hong Kong | HKD 4 | HKD 54,000 | N/A | N/A | 15 min | | Alipay Hong Kong | HKD 0.01 | HKD 1,000 | N/A | N/A | 17 min | | WeChat Pay Hong Kong | HKD 0.01 | HKD 1,000 | N/A | N/A | 17 min | | Google Pay Apple Pay Hong Kong | HKD 3 | HKD 999,999 | N/A | N/A | 15 min | | FPS | HKD 0.01 | HKD 40,000 | N/A | N/A | 5 min | | PayPal Hong Kong | HKD 0.1 | HKD 999,999 | N/A | N/A | 15 min | ### Hungary ✍️ Hungary payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Hungary | HUF 200 | HUF 2,486,000 | N/A | N/A | 15 min | | Google Pay Apple Pay Hungary | HUF 200 | HUF 999,999 | N/A | N/A | 15 min | | PayPal Hungary | HUF 1 | HUF 999,999 | N/A | N/A | 15 min | ### India

Payment Channel	Minimum Price Point	Maximum Price Point	Other Limits	Detailed price points (if applicable)	Transactions expire in
UPI	INR 1	INR 100,000	N/A	N/A	15 min

### Indonesia ✍️ Indonesian payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------ | ------------------- | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | Alfamart | IDR 1 | IDR 2,000,000 | IDR 10,000,000/Day | N/A | 25 hour | | Bank Transfers Indonesia | IDR 10,000 | IDR 50,000,000 / Bank account limit | N/A | N/A | 24 hour | | Indosat | IDR 1 | IDR 2,000,000 | IDR 2,000,000/Day | N/A | 10 min | | Telkomsel | IDR 500 | IDR 510,000 | N/A | [Fixed Price Point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 20 min | | XL | IDR 1,000 | IDR 1,200,000 |

IDR 100,000/Month (only applies to postpaid customers)

IDR 3,000,000/Day (for all customers)

| N/A | 20 min | | Tri Indonesia | IDR 500 | IDR 1,300,000 | N/A | N/A | 10 min | | Smartfren | IDR 1 | IDR 2,000,000 | N/A | N/A | 10 min | | DOKU Wallet | IDR 1,000 | IDR 5,000,000 | IDR 20,000,000/Month | N/A | 1 hour | | Indomaret | IDR 1 | IDR 5,000,000 | N/A | N/A | 2 Day | | GO-PAY | IDR 1 | IDR 10,000,000 | N/A | N/A | 6 h | | OVO | IDR 1 | IDR 10,000,000 | IDR 20,000,000/Month | N/A | Must confirm transaction within 55 seconds in the app (5 Minutes expiry time at Coda) | | DANA | IDR 1 | IDR 3,000,000 | N/A | N/A | 35 min | | LinkAja | IDR 1,000 | IDR 5,000,000 | N/A | N/A | 10 min | | ShopeePay Indonesia | IDR 100 | IDR 1,000,000,000 | N/A | N/A | 15 min | | QRIS | IDR 1 | IDR 10,000,000 | N/A | N/A | 15 min | | Card Payments Indonesia | IDR 10,000 | IDR 110,000,000 | N/A | N/A | 15 min | | PayPal Indonesia | IDR 500 | IDR 999,999 | N/A | N/A | 15 min | ### Iraq | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | -------------------- | ------------------------------------- | ---------------------- | | Zain Iraq | IQD 100 | IQD 250,000 | IQD 20,000,000/Month | N/A | 15mins | ### Italy | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Italy | EUR 0.5 | EUR 999,999 | N/A | N/A | 30 min | | Google Pay Apple Pay Italy | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | PayPal Italy | EUR 0.01 | EUR 999,999 | N/A | N/A | 10 min | ### Ireland | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | PayPal Ireland | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Ireland | EUR 0.5 | EUR 6,000 | N/A | N/A | 15 min | ### Japan ✍️ Japanese payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Japan | JPY 60 | JPY 999,999 | N/A | N/A | 10 min | | Google Pay Apple Pay Japan | JPY 58 | JPY 999,999 | N/A | N/A | 15 min | | PayPay | JPY 1 | JPY 500,000 | N/A | N/A | 5 min | | PayPal Japan | JPY 15 | JPY 999,999 | N/A | N/A | 10 min | ### Kuwait | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Zain Kuwait | KWD 1 | KWD 20 | KWD 30/Month | N/A | 20 min | | KNET | KWD 0.1 | KWD 1,000 | N/A | N/A | 15 min | | Card Payments Kuwait | KWD 0.2 | KWD 2,000 | N/A | N/A | 15 min | ### Kazakhstan | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------ | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Kazakhstan | KZT 250 | KZT 999,999 | N/A | N/A | 15min | ### Kenya | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ------------------------- | ------------------------------------- | ---------------------- | | M-PESA | KES 1 | KES 1,000,000 | Does not support decimals | N/A | 30min | ### Laos | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------ | ------------------- | ------------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------------- | | Unitel Laos | LAK 1,000 | LAK 2,249,800 |

Postpaid:
LAK 200,000/Day and LAK 2,000,000/Month

| [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 10 min | | Lao Telecom | LAK 1,000 | LAK 2,200,000 | N/A | N/A | 20 min | | Card Payments Laos | LAK 3,186 | LAK 999,999 | N/A | N/A | 20 min | ### Malaysia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------------- | ------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------- | | Maxis | MYR 1 | MYR 100 |

MYR 100/Day and MYR 400/Month

Transactions only allow for prepaid numbers.

| N/A (any number between 1 and 100, with no decimal points) | 10 min | | Digi | MYR 0.10 | MYR 1000 |

Postpaid: MYR 500/Month
Prepaid: MYR 1000/Month

Transactions allow for both postpaid and prepaid numbers.

| N/A (any number within the limits, with two decimal points) | 2 min | | Celcom | MYR 0.10 | MYR 1000 |

Postpaid: MYR 500/Month
Prepaid: MYR 1000/Month

Transactions allow for both postpaid and prepaid numbers.

| N/A | 5 min | | U Mobile | MYR 0.01 | MYR 500 | Transactions will be allowed only on prepaid numbers | N/A | 15 min | | GrabPay Malaysia | MYR 1 | MYR 500 | Maximum MYR 1,500/User/Day | N/A | 10 min | | Touch-NGo | MYR 0.10 | MYR 50,000 | N/A | N/A | 35 min | | Boost | MYR 1 | MYR 3,000 | N/A | N/A | 6 min | | ShopeePay Malaysia | MYR 0.01 | MYR 2,999 | N/A | N/A | 15 min | | MAE / Duitnow | MYR 0.01 | MYR 1,000 | Max MYR 1,000/Day | N/A | 1 min | | Card Payments Malaysia | MYR 2 | MYR 49,999.99 | N/A | N/A | 15 min | | Google Pay Apple Pay Malaysia | MYR 2 | MYR 999,999 | N/A | N/A | 15 min | ### Mexico | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | OxxoPay | MXN 1 | MXN 10,000 | N/A | N/A | 3 day | | Bank Transfer Mexico | MXN 1 | MXN 6,000 | N/A | N/A | 10 day | | PaysafeCard Mexico | MXN 0.01 | MXN 2,500 | N/A | N/A | 30 min | | Mercado Pago Mexico | MXN 0.5 | MXN 10,000 | N/A | N/A | 4 h | | toditoCash | MXN 1 | MXN 10,000 | N/A | N/A | 15 min | | Card Payments Mexico | MXN 20 | MXN 100,000 | N/A | N/A | 125 min | | Google Pay Apple Pay Mexico | MXN 8 | MXN 999,999 | N/A | N/A | 15 min | | PayPal Mexico | MXN 1 | MXN 999,999 | N/A | N/A | 10 min | | OXXO | MXN 1 | MXN 10,000 | N/A | N/A | 10 days | ### Mongolia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | MonPay | MNT 1 | MNT 1,000,000 |

Max Limit for Non-MonPay User:
MNT 20'000 MonPay (7.4 USD)

Max Limit for MonPay User:
MNT 1'000'000 (374.2 USD)

| N/A | 15 min | | Unitel Mongolia | MNT 1,000 | MNT 1,725,000 |

Charge limits vary based on user's mobile package.

Postpaid varies from 40k to 200k MNT

Prepaid has no limit

| N/A | 6 min | | Toki | MNT 1 | MNT 360,000 |

Charge limits vary based on mobile package.

Postpaid varies from 40k to 200k MNT

Prepaid no limit

| N/A | 6 min | ### Morocco | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Morocco | MAD 5.99 | MAD 64,000 | N/A | N/A | 10 min | ### Myanmar | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | | MPT | MMK 50 | MMK 50,000 | N/A | N/A | 10 min | | ATOM | MMK 50 | MMK 5,000,000 |

Daily Limit:
MMK 20,000,000

Monthly Limit (30 days):
MMK 40,000,000

| N/A | 10 min | | U9 | MMK 1 | MMK 3,300,000 | N/A | N/A | 10 min | | WavePay | MMK 1 | MMK 1,600,000 | N/A | N/A | 35 min | | easyPoints | MMK 500 | MMK 500,000 | N/A |

You can initiate a transaction with either:
A)
Any amount between 500-500,000 Kyat, we recommend using the most popular denominations of: 500; 1,000; 2,000; 3,000; 5,000; 10,000; 50,000; 100,000
OR
B)
Amount = 0. In this case we will charge the voucher and notify you the amount in the charge response. You may then decide which/how many items to deliver to the user.

| 10 min | | KBZPay | MMK 1 | MMK 5,000,000 | N/A | N/A | 15 min | | Card Payments Myanmar | MMK 1,500 | MMK 999,999 | N/A | N/A | 20 min | ### Nepal | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | E-Pay | NPR 1 | NPR 100,000 | N/A | N/A | 20 min | ### Nigeria | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------- | ------------------- | ------------------- | ---------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Paga | NGN 1 | NGN 5,000,000 | N/A | N/A | 24 h | | Verve Card | NGN 51 | NGN 3,000,000 | Accept payment with cards that is issued in Nigeria, foreign card is not accepted. | N/A | 17 min | | Bank Transfers Nigeria | NGN 5 | NGN 25,000,000 | N/A | Not support decimal points. | 1 h | | Opay Wallet | NGN 51 | NGN 600,000 | N/A | N/A | 30 min | | Card Payments Nigeria | NGN 800 | NGN 999,999 | N/A | N/A | 15 min | ### Netherlands | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Netherlands | EUR 0.5 | EUR 6,000 | N/A | N/A | 30 min | | iDeal | EUR 0.01 | EUR 1,000 | N/A | N/A | 30 min | | Google Pay Apple Pay Netherlands | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | Paypal Netherlands | EUR 0.01 | EUR 500 | N/A | N/A | 10 min | ### **New Zealand** | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Google Pay Apple Pay New Zealand | NZD 0.9 | NZD 999,999 | N/A | N/A | 15 min | | Card Payments New Zealand | NZD 1 | NZD 999,999 | N/A | N/A | 10 min | | PayPal New Zealand | NZD 0.01 | NZD 999,999 | N/A | N/A | 15 min | ### Norway | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Vipps | NOK 1 | NOK 1,000 | N/A | N/A | 28 Day | | Google Pay Apple Pay Norway | NOK 6 | NOK 999,999 | N/A | N/A | 15 min | | Card Payments Norway | NOK 6.60 | NOK 999,999 | N/A | N/A | 15 min | | PayPal Norway | NOK 0.1 | NOK 999,999 | N/A | N/A | 15 min | ### Pakistan | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------- | ------------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Telenor Pakistan | Rs 1 | Rs 5,000 |

Max Limit for Prepaid:
PKR 5,000/Transaction

Max Limit for Postpaid:
PKR 2,500/Transaction

| N/A | 10 min | | Ufone | Rs 1 | Rs 10,000 |

No Decimal Pricing

Prepaid Per Transaction:
PKR 10,000,

Prepaid Per Month:
PKR 25,000

Postpaid Per Transaction:
PKR 5,000

Postpaid Per Month:
PKR 10,000

| N/A | 10 min | | Easypaisa | Rs 1 | Rs 750,000 | N/A | N/A | 15 min | | JazzCash | Rs 1 | Rs 750,000 | N/A | N/A | 15 min | | Nayapay | Rs 0.01 | Rs 50,000 | Rs 50,000 per user per day | N/A | 12 min | | Card Payments Pakistan | Rs 170 | Rs 999,999 | N/A | N/A | 15 min | | HBL Konnect | Rs 1 | Rs 750,000 | N/A | N/A | 15 min | | Bank Transfer Pakistan | Rs 1 | Rs 1,000,000 | N/A | N/A | 60 min | ### Poland | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | BLIK | PLN 2 | PLN 1,500 | N/A | N/A | 30min | | Card Payments Poland | PLN 2.44 | PLN 26,000 | N/A | N/A | 30 min | | Google Pay Apple Pay Poland | PLN 3 | PLN 999,999 | N/A | N/A | 15 min | | Paypal Poland | PLN 0.01 | PLN 999,999 | N/A | N/A | 10 min | ### Paraguay | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Paraguay | PYG 5,000 | PYG 4,000,000 | N/A | N/A | 15 min | ### Portugal | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Multibanco | EUR 0.01 | EUR 2,500 | N/A | N/A | 28 day | | Google Pay Apple Pay Portugal | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Portugal | EUR 0.5 | EUR 6,000 | N/A | N/A | 15 min | | PayPal Portugal | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | ### Peru | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Cash Payments Peru | PEN 1 | PEN 500 | N/A | N/A | 14 day | | Bank Transfers Peru | PEN 1 | PEN 5000 | N/A | N/A | 14 day | | Card Payments Peru | PEN 2.5 | PEN 999,999 | N/A | N/A | 20 min | | PayPal Peru | PEN 0.01 | PEN 999,999 | N/A | N/A | 15 min | ### Philippines | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------------- | ------------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Smart | PHP 1 | PHP 2,400 | N/A | N/A | 10 min | | Bank Transfers Philippines | PHP 10 | PHP 10,000 |

Exceptions:

BDO ATM
minimum PHP 200

EastWest bank
maximum PHP 2,000

| N/A | 2 hour | | Cash at Retail ex 7-Eleven PH | PHP 50 | PHP 10,000 | N/A | N/A | 2 hour | | GCash | PHP 0.01 | PHP 100,000 | N/A | N/A | 20 min | | GrabPay Philippines | PHP 30 | PHP 10,000 | N/A | N/A | 2 hour | | 7-Eleven Philippines | PHP 450 | PHP 10,000 | N/A | N/A | 2 hour | | Maya | PHP 0.01 | PHP 50,000 | N/A | N/A | 35 min | | Coins.ph | PHP 6 | PHP 10,000 | N/A | N/A | 15 min | | Card Payments Philippines | PHP 25 | PHP 400,000 | N/A | N/A | 20 min | | Dito | PHP 0.01 | PHP 10,000 | N/A | N/A | 2 min | | Google Pay Apple Pay Philippines | PHP 25 | PHP 999,999 | N/A | N/A | 15 min | | PayPal Philippines | PHP 0.5 | PHP 999,999 | N/A | N/A | 15 min | ### Qatar | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Qatar | QAR 2 | QAR 999,999 | N/A | N/A | 15 min | | PayPal Qatar | QAR 0.05 | QAR 999,999 | N/A | N/A | 15 min | ### Romania | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Romania | RON 5 | RON 999,999 | N/A | N/A | 15 min | | Google Pay Apple Pay Romania | RON 2.5 | RON 999,999 | N/A | N/A | 15 min | | PayPal Romania | RON 0.05 | RON 999,999 | N/A | N/A | 15 min | ### Saudi Arabia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------- | ------------------- | ------------------- | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | | Card Payments Saudi Arabia | SAR 2 | SAR 27,000 | N/A | N/A | 20 min | | Mada | SAR 0.01 | SAR 27,000 | N/A | N/A | 10 min | | STC Pay | SAR 0.01 | SAR 300 | Daily limit: 300 per user | support decimal point | 10 min | | Mobily | SAR 1 | SAR 500 | N/A | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points), contact integration support team for more info | 1 min | | Apple Pay Saudi Arabia | SAR 0.01 | SAR 999,999 | N/A | N/A | 30 min | | PayPal Saudi Arabia | SAR 0.01 | SAR 999,999 | N/A | N/A | 10 min | ### Slovakia | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | PayPal Slovakia | EUR 0.01 | EUR 999,999 | N/A | N/A | 15 min | | Card Payments Slovakia | EUR 0.5 | EUR 6,000 | N/A | N/A | 15 min | ### Singapore | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------- | ------------------- | ------------------- | ----------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | SingTel | SGD 3 | SGD 100 |

SGD 200/Month
(only applies to postpaid customers)

| N/A | 10 min | | GrabPay Singapore | SGD 1 | SGD 300 | Maximum SGD 300/User/Day | N/A | 10 min | | PayNow | SGD 0.1 | SGD 1,000 | N/A | N/A | 5 min | | Card Payments Singapore | SGD 0.84 | SGD 9,999 | N/A | N/A | 30 min | | PayPal Singapore | SGD 0.1 | SGD 999,999 | N/A | N/A | 10 min | ### South Africa | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Bank Transfers South Africa | ZAR 1 | ZAR 15,000 | N/A | N/A | 30 min | | Card Payments South Africa | ZAR 10 | ZAR 125,000 | N/A | N/A | 15 min | | 1Voucher | ZAR 2 | ZAR 2,500 | N/A | N/A | 30 min | ### South Korea ✍️ South Korea payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- | | Carrier Billing South Korea | KRW 10 | KRW 1,000,000 | N/A | N/A | 35 min | | KakaoPay | KRW 100 | KRW 330,000 | N/A | N/A | 35 mins | | Naver Pay | KRW 100 | KRW 330,000 |

Special Instruction:
Users can pay using two methods (Credit Cards and Naver Point) but merchants from the gaming industry are not allowed to pay by Naver Point.

| N/A | 35 mins | | Card Payments South Korea | KRW 100 | KRW 1,000,000 | N/A | N/A | 35 mins | | Culture Voucher | KRW 1,100 | KRW 999,999 | N/A | N/A | 35 mins | | Payco | KRW 100 | KRW 330,000 | N/A | N/A | 35 mins | | T-Money | KRW 100 | KRW 330,000 | N/A | N/A | 35 mins | | Happymoney | KRW 1,100 | KRW 9,999,999 | N/A | N/A | 35 mins | ### Sri Lanka | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Sri Lanka | LKR 200 | LKR 999,999 | N/A | N/A | 20 min | | Dialog | LKR 1 | LKR 50,000 | N/A | N/A | | ### Switzerland | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | TWINT | CHF 0.01 | CHF 5,000 | N/A | N/A | 20 min | | Google Pay Apple Pay Switzerland | CHF 0.5 | CHF 999,999 | N/A | N/A | 15 min | | Card Payments Switzerland | CHF 0.5 | CHF 999,999 | N/A | N/A | 15 min | | PayPal Switzerland | CHF 0.01 | CHF 999,999 | N/A | N/A | 15 min | ### Spain | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Spain | EUR 0.5 | EUR 6,000 | N/A | N/A | 30 min | | Google Pay Apple Pay Spain | EUR 0.5 | EUR 999,999 | N/A | N/A | 15 min | | PayPal Spain | EUR 0.01 | EUR 999,999 | N/A | N/A | 10 min | ### Sweden | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Trustly | SEK 3 | SEK 10,000 | N/A | N/A | 28 Day | | Card Payments Sweden | SEK 5 | SEK 999,999 | N/A | N/A | 15 min | | Google Pay Apple Pay Sweden | SEK 0.5 | SEK 999,999 | N/A | N/A | 15 min | | PayPal Sweden | SEK 0.1 | N/A | N/A | N/A | 15 min | ### Taiwan ✍️ Taiwan payments **NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------------- | ------------------- | ------------------- | --------------------- | ----------------------------------------------------------------------------------------- | ---------------------- | | Taiwan Mobile | N/A | N/A | Only support postpaid | N/A | 15 min | | FarEasTone | TWD 30 | TWD 3,000 | Only support postpaid | N/A | 1 hour | | Chunghwa Telecom | TWD 30 | TWD 2,000 | Only support postpaid | N/A | 1 hour | | GASH Gift Card | TWD 30 | TWD 20,000 | N/A | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 1 hour | | Line Pay | TWD 1 | TWD 45,000 | N/A | N/A | 20 min | | JKO Pay | TWD 1 | TWD 50,000 | TWD 100,000/Day | N/A | 15 min | | Card Payments Taiwan | TWD 19.50 | TWD 209,000 | N/A | N/A | 10 min | | PayPal Taiwan | TWD 1 | TWD 999,999 | N/A | N/A | 15 min | | GASH e-wallet | TWD 1 | TWD 50,000 | N/A | N/A | 50 min | | Google Pay Apple Pay Taiwan | TWD 19.5 | TWD 999,999 | N/A | N/A | 25 min | ### Thailand | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ------------------------------------ | ------------------- | ------------------- | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ---------------------- | | 7-Eleven Thailand | THB 1 | THB 49,000 | N/A | N/A | 24 h | | ShopeePay Thailand | THB 0.01 | THB 200,000 | N/A | N/A | 10 min | | AIS | THB 0.01 | THB 50,000 | Only prepaid numbers are allowed. | N/A | 5 min | | Bank Transfers and Cash at Retail TH | THB 1 | THB 49,000 | N/A | N/A | 24 hour | | dtac | THB 1 | THB 500 |

THB 500/day
THB 3,000/month

| N/A | 5 min | | Rabbit LINE Pay | THB 1 | THB 8,000 | N/A | N/A | 35 min | | TrueMoney Cash Card | N/A | N/A | N/A | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 35 min | | TrueMoney Wallet | THB 1 | THB 3,000,000 | N/A | N/A | 35 min | | K PLUS | THB 0.01 | THB 200,000 | THB 2,000,000/Day | N/A | 15 min | | Truemove H | THB 5 | THB 500 | Transactions will be allowed only on prepaid numbers, THB 500/Day and THB 3,000/Month | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 11 min | | One-2-Call Cash Card | THB 0.01 | THB 2,500 | N/A | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 30 min | | PromptPay | THB 1 | THB 100,000 | THB 6,000,000/Month | N/A | 10 min | | Card Payments Thailand | THB 1 | THB 999,999 | N/A | N/A | 20 min | | PayPal Thailand | THB 0.5 | THB 999,999 | N/A | N/A | 15 min | ### Timor Leste | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------- | ------------------- | ------------------- | ------------ | ----------------------------------------------------------------------------------------- | ---------------------- | | Telemor | USD 0.09 | USD 1,000 | N/A | [Fixed price point](/codapay/integration-guides/price-limits/detailed-fixed-price-points) | 10 min | ### Turkey | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | -------------------- | ------------------- | ------------------- | --------------------- | ------------------------------------- | ---------------------- | | Papara | TRY 1 | TRY 50,000 | TRY 500,000 (Monthly) | N/A | 10 min | | Card Payments Turkey | TRY 0.1 | TRY 999,999 | N/A | N/A | 30 min | | Bank Transfer Turkey | TRY 1 | TRY 250,000 | N/A | N/A | 3 Days | ### Great Britain (UK, Scotland, Wales) | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments UK | GBP 0.5 | GBP 5,000 | N/A | N/A | 30 min | | Google Pay Apple Pay UK | GBP 0.5 | GBP 999,999 | N/A | N/A | 15 min | | PayPal UK | GBP 0.01 | GBP 999,999 | N/A | N/A | 10 min | ### United Arab Emirates | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ---------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Etisalat | AED 0.50 | AED 1,000 | N/A | N/A | 90 min | | Payby | AED 0.01 | AED 2,000 | N/A | N/A | 20 min | | Card Payments United Arab Emirates | AED 2 | AED 25,000 | N/A | N/A | 20 min | | PayPal United Arab Emirates | AED 0.05 | N/A | N/A | N/A | 15 min | ### Uruguay | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | Card Payments Uruguay | UYU 25 | UYU 999,999 | N/A | N/A | 15 min | | Cash Payments Uruguay | UYU 1 | UYU 1,500 | N/A | N/A | 14 day | ### United States | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | ----------------------------------------------------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | |

Card Payments US
(Visa, Mastercard & American Express)

| USD 0.5 | USD 9,999 | N/A | N/A | 15 min | | Google Pay Apple Pay US | USD 0.5 | USD 10,000 | N/A | N/A | 15 min | | Cash App | USD 0.01 | USD 700 | N/A | N/A | 10 min | | PayPal US | USD 0.01 | USD 999,999 | N/A | N/A | 10 min 30 sec | ### Vietnam ✍️ Vietnam payments **DO NOT SUPPORT** decimal points. | Payment Channel | Minimum Price Point | Maximum Price Point | Other Limits | Detailed price points (if applicable) | Transactions expire in | | --------------------- | ------------------- | ------------------- | ------------ | ------------------------------------- | ---------------------- | | VTCPay | VND 5,000 | VND 20,000,000 | N/A | N/A | 20 min | | Card Payments Vietnam | VND 13,000 | VND 999,999 | N/A | N/A | 20 min | | MoMo E-Wallet | VND 1,000 | VND 20,000,000 | N/A | N/A | 15 min | | PayPal Vietnam | VND 250 | VND 999,999 | N/A | N/A | 15 min | # Detailed Fixed Price Points Payment Channel Details Fixed Price Points lists specific fixed price points for various payment channels. These fixed price points are applicable for the following channels: * [Indonesia Telkomsel](#indonesia-telkomsel) * [Laos Unitel](#id-1300-laos-unitel) * [Saudi Arabia Mobily](#saudi-arabia-mobily) * [Thailand TrueMoney cash card](#thailand-truemoney-cash-card) * [Thailand One-2-Call Cash Card](#thailand-one-2-call-cash-card) * [Thailand Truemove H](#thailand-truemove-h) * [Timor Leste Telemor](#timor-leste-telemor) * [Taiwan GASH Gift Card](#taiwan-gash-gift-card) *** ## Indonesia Telkomsel {% hint style="info" %} 📘 **Content Meaning** Web/PC Content: Top-ups at the game's top-up center or on the game's PC Mobile content: Refers to mobile phone Game apps Non-Gaming Content: Such as Live streaming {% endhint %} {% hint style="warning" %} 🚧 **Approval Required** This channel has strict price and SKU parameter restrictions. Before applying to go live on this channel, you need to fill out the price application form (Telkomsel submissionv2.xlsx). Provide appropriate information as required, and Coda tech team submits the channel for approval before it can enter production testing and go live. {% endhint %} | Web/PC Content | Mobile Content | Non-Gaming Content | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | |

500
1000
2000
3000
4000
5000
10000
12500
15000
20000
25000
30000
35000
50000
75000
100000
113000
150000
200000
250000
300000
330000
350000
400000
410000
500000

1000
1300
1500
1514
2000
3000
4000
5000
5045
6000
10000
10091
11000
11450
12500
15000
16000
20000
20182
22900
30000
30273
32900
35000
49000
50000
60000
60545
65000
65800
75000
79000
100000
100909
113000
129000
114300
150000
151364
159000
200000
250000
259000
300000
302727
309000
328300
330000
350000
399000
400000
410000
450000
500000

1000
2000
5000
10000
15000
20000
35000
50000
75000
100000
150000
200000
250000

| ## Laos Unitel |

1000
2000
2500
3080
3127
4000
5000
5730
7340
7700
7960
8000
8016
8421
8440
8500
8514
8528
8550
8600
8622
8800
8900
9000
9500
10000
10500
11000
12000
12750
13500
13900
14600
15400
15919
16927
17000
17056
17114
17331
18000
19350
20000
21000
21500
22000
23878
24640
25000
25432
25500
25625
25650
25714
25800
26039
26700
27000
27800
28660
29000
30000
30100
30800
31838
33938
34000
34200
35000
36000
36700
37500
37800
38450
38500
39798
40000
40081
41000
42200
42444
42500
42640
42750
42900
42914
43000
43300
43457
44000
44600
44900
45000
46000
47757
50000
51250
54000
55600
57330
58100
60000
62500
68224
68400
69583
70000
72000
73000
73400
80000
80161
82000
82437
84000
84400
84973
85000
85280
85500
85800
85914
86000
86200
87000
87260
88000
89100
89900
90000
92400
94500
96400

100000
105000
109750
110000
114050
125000
126000
128250
128700
129900
132000
136000
146397
150000
153750
154000
165000
170560
171000
171600
171914
172000
172500
174086
176000
178300
179000
182000
200000
205000
206600
210000
212500
215000
218282
220000
220200
221000
225000
230000
230625
240484
246400
250000
251000
253200
255090
255840
256500
257400
258000
258720
258800
261173
264000
267500
269900
270000
272000
281424
286600
300000
307500
308000
318379
337500
342000
345000
360000
363000
367000
376650
400806
415500
422000
425000
425206
426400
427500
429100
429914
430000
435000
435346
440000
445900
449000
450000
461250
462000
500000
517000
525000
573300
595323
600900
616000
710300
720000
725000
734000
795947
801613
822400
844000
850000
850498
852800
855000
858300
859914
860000
862000
870778
880000
891800
899000
900000
934000
939000
1640000
1725000
2200000

| | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | | | ## Saudi Arabia Mobily |

Mobily internally identifies each transaction using the product ID. Before going live, we require your assistance in providing the item name and price for all tiers. Coda will create a product ID for each denom for Mobily. (This can only be tested in the production environment.)

For example:
Product Name: \

Denomination: 100 Diamonds
Price: 100

Denomination: 200 Diamonds
Price: 200

\*The rest of the denom can be done in the same manner.

| | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ## Thailand TrueMoney cash card |

50
90
150
300
500
1000

| | -------------------------------------------- | ## Thailand One-2-Call Cash Card |

50
100
300
500
1000

| | -------------------------------------- | ## Thailand Truemove H |

5
9
10
15
19
20
25
29
30
32
33
35
49
50
60
69
75
79
90
99
100
149
150
200
249
250
300
349
350
400
500

0.09
0.17
0.2
0.25
0.49
0.5
0.7
0.71
0.81
0.9
0.97
0.99
1
1.05
1.08
1.09
1.1
1.19
1.22
1.33
1.5
1.58
1.74
1.9
1.95
1.99
2
2.16
2.19
2.2
2.37
2.4
2.5
2.6
2.75
2.9
2.99
3
3.02
3.12
3.2
3.3
3.4
3.48
3.5
3.6
3.7
3.74
3.8
3.9
3.99
4
4.3
4.32
4.39
4.44
4.5
4.68
4.86
4.9
4.99
5
5.49
5.5
5.9
5.99
6
6.24
6.5
6.9
6.95
6.99
7
7.1
7.2
7.5
7.56
7.99
8
8.5
9
9.69
9.7
9.99
10
10.99
11
11.99
12
12.2
12.4
12.5
13
14
14.99

15
15.5
16
16.49
17
18
18.74
19.25
19.3
19.4
19.99
20
21
21.65
22
22.49
23
24
24.99
25
25.5
26
26.2
27
27.48
27.99
28
28.12
29
29.1
29.99
30
30.99
32.99
33
33.74
35
35.5
36.08
37.49
39.99
40
42
42.5
44
44.99
45
48.5
48.99
49
49.99
50
54.99
55
55.5
56.24
58.2
59.99
60
67.5
69.99
70
71.07
75
77.6
79.5
80
85
85.5
94.99
95.5
97
99.99
100
109.99
110
118.45
150
168
190
200
300
389.99
500
1000

| | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ## Taiwan GASH Gift Card |

30
33
50
100
150
170
300
330
350
450
490
500
670
990
1000
1200
1490
1690
2000
2690
3000
3290
5000
10000
20000

| | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | {% hint style="success" %} Should you have any questions, please do not hesitate to contact [Coda Support Team](/contact-us). {% endhint %} # Security Guidelines Whether opting for a static or dynamic Transaction Completion Notification URL, prioritizing security is key. Unauthorized access to this URL could enable malicious actors to fabricate payment transactions, leading to potential financial loss. To safeguard against such risks, diligently implement the prescribed security measures outlined below for the protection of the Transaction Completion Notification URL. {% hint style="danger" %} **Make sure your Transaction Completion Notification URL is secure!** {% endhint %} *** ## Implement Checksum A checksum ensures that callback/webhook notifications received from Codapay have not been altered in transit. Partners must validate the checksum before processing the notification. The checksum format differs depending on the type of notification: **Payin**, **Save Card (Only Available in V2 Payin)**, or **Refund/Chargeback**. ### Payin Transactions (V1 / V2) Used for standard payment(Payin) completion notifications. **Formula** ``` txnId + apiKey + orderId + resultCode ``` **Example** * txnId = `3381290433880074215` * apiKey = `5a8ca8f31f19a23c41edd14b29a74fd2` * orderId = `8ae6ffee169b` * resultCode = `0` Checksum string: ``` 33812904338800742155a8ca8f31f19a23c41edd14b29a74fd28ae6ffee169b0 ``` MD5 result: ``` 5cb948816af0b5b61516fd71a17d271b ``` ### Save Card Notifications Triggered when a user adds or removes a saved payment method. **Events** * `PAYMENT_METHOD_ADDED` * `PAYMENT_METHOD_REMOVED` **Formula** ``` eventType + apiKey + shopperId + paymentMethodId + partnerShopperId ``` **Example Payload** ```json { "eventType": "PAYMENT_METHOD_ADDED", "shopper": { "id": "shp_sg197861636b40021", "partnerShopperId": "test_partner_123_Id" }, "paymentMethod": { "id": "pmt_sg1978616a1900024" } } ``` Checksum string: ``` PAYMENT_METHOD_ADDED + apiKey + shp_sg197861636b40021 + pmt_sg1978616a1900024 + test_partner_123_Id ``` → Apply **MD5** hash. ### Refund & Chargeback Notifications Used for refund or chargeback events. **Formula** ``` eventType + apiKey + txnId + orderId + resultCode + statusCode ``` This ensures that refund/chargeback notifications are validated consistently and securely. ### Checksum Comparison Table

Scenario Payload Format Formula Hash Algorithm Example Parameters

Payin (V1/V2) Query String txnId + apiKey + orderId + resultCode MD5 txnId: 3381290433880074215orderId: 8ae6ffee169bresultCode: 0

Save Card (Only Available in V2 Payin)

JSON Body

eventType + apiKey + shopperId + paymentMethodId + partnerShopperId

MD5

eventType: PAYMENT_METHOD_ADDEDshopperId:shp_...

paymentMethodId: pmt_...

Refund / Chargeback

JSON Body

eventType + apiKey + txnId + orderId + resultCode + statusCode

MD5

eventType: REFUND

txnId: 123...

statusCode: 200

## Implement HTTPS This will prevent third parties from message eavesdropping. ## Filtering Merchant IP This whitelisting is based on rendering on the init interface, and only the IP you whitelisted can request orders.\ \ Directions: [Publisher Portal](https://portal.coda.co/) -> Integration -> Security -> Codapay Partner Settings -> Action (Edit IP Address) ### **Filtering Codapay IP** {% hint style="success" %} Only if the transaction callback can get through your firewall and send you a transaction completion notification message. {% endhint %} To ensure that payment callback notifications are successfully received and not rejected by your servers, please take note of the following: 1. If your firewall or server configuration requires IP whitelisting for Codapay egress IPs, please send an email request to our support team at 2. Upon your request, we will provide you with the updated IP ranges or alternative domain/endpoint validation details required for your whitelist configuration. # Brand Guidelines Please see these guidelines on how to present the Codapay payment methods in your checkout process. ## Brand guidelines for Carrier Billing * The operator logos and/or names should be displayed most prominently. * If possible, the words “Pay by mobile” (Singapore or Malaysia), “Potong Pulsa” (Indonesia), “Buy with Load” (Philippines) and “SMS” (Myanmar) should be included. * Powered by Coda logo should be included, but only in a secondary position to the operator logos or names. ## Brand guidelines for Bank Transfer * The Prima, Alto, and ATM Bersama logos should be displayed most prominently. * If possible, the words “Bank Transfer” should be included. * The powered by Coda logo should be included, but only in a secondary position to the ATM network logos or the words “Bank Transfer”. ## Brand Guidelines for Mobile Banking * The m-BCA, Mandiri Mobile, and Go Mobile logos should be displayed most prominently. * If possible, the words “Mobile banking” should be included. * The powered by Coda logo should be included, but only in a secondary position to the mobile banking app logos or the words “Mobile banking”. ## Brand Guidelines for Convenience Store * The logo for the Convenience Store should be displayed most prominently. * If possible, the brand of Convenience Store should be included. * The powered by Coda logo should be included, but only in a secondary position to the Convenience Store provider names or logos. ## Brand guidelines for Vouchers * The logos of the voucher issuers (True Money for Thailand, easyPoints for Myanmar) should be displayed most prominently. * Powered by Coda logo should be included, but only in a secondary position to the Voucher issuer names or logos. ## Brand guidelines for E-wallet * The logos of the E-wallet should be displayed most prominently. * The powered by Coda logo should be included, but only in a secondary position to the E-wallet names or logos. ## Logos Partners can download all of our payment channel logos using the zip file provided below. {% file src="/files/IRL9aEQ1TV1NOzWy3NM9" %} {% hint style="danger" %} **Important Note** Customers do not typically recognize the powered-by Coda logo, we encourage partners to only include it in a secondary position on their payment page. The logos of the individual payment channels that partners implemented should be featured where possible. {% endhint %} # Hosted Payment Page Integration The Hosted Payment Page integration involves directing the customer to a secure, hosted payment page provided by Coda. This page is responsible for collecting payment information and processing transactions. This section details each technical step needed for a successful integration. For an overview of the flow, please refer to the [Getting Started](/codapay/getting-started) guide.


Initiate a payment request	Learn how to initiate a payment request and collect a transaction ID	Initiate a payment request
Display the hosted payment page	Familiarise yourself with how to display the hosted payment page and the flows supported	Display the Hosted Payment Page
Get notified of a transaction status	Receive notifications of transaction status changes as your user progresses through the payment flow.	Get notified of a transaction status change
Check a transaction status	Learn how to check a transaction's status and decide whether to release the purchased item.	Check a transaction status

Explore each section by clicking the relevant links above to dive deeper into the process. # Initiate a payment request Allows you to initiate a payment request and collect your payment transaction ID. ### Pre-requisite When integrating with Codapay APIs, ensure you adhere to the following standards: 1. Use HTTPS protocol. 2. TLS 1.2 or higher

Environment	BaseURL
Sandbox	https://sandbox.codapayments.com/airtime/api/restful/v1.0/Payment
Production	https://airtime.codapayments.com/airtime/api/restful/v1.0/Payment

Note that Codapay APIs have two versions, please refer to [Codapay API Versions](/codapay/integration-guides/codapay-api-versions) for more details to ensure you have selected the right version to integrate with. ### Reference #### Sandbox

Version	Base URL
v2.0	https://sandbox.codapayments.com/airtime/api/restful/v2.0/Payment
v1.0	https://sandbox.codapayments.com/airtime/api/restful/v1.0/Payment

#### Production

Version	Base URL
v2.0	https://airtime.codapayments.com/airtime/api/restful/v2.0/Payment
v1.0	https://airtime.codapayments.com/airtime/api/restful/v1.0/Payment

#### Endpoint **POST**** {Base URL}/init.json** {% hint style="info" %} Codapay's APIs support REST web services. By default, the endpoints displayed are RESTful. {% endhint %} ### Request Parameters

Parameter	Type	Description
initRequest	Object	Mandatory Must be a valid JSON object
initRequest.country	String	Mandatory ISO 3166 country code - refer to Country and Currency Codes
initRequest.payType	String	Mandatory The ID of the payment channel you want to use - refer to the full list available here. Can be set to 0 if you want to use the channel selection page or 1 if you want to use the DCB page - More details here.
initRequest.apiKey	String	Mandatory API key provided by Coda - Refer to Getting started to find out how to get it.
initRequest.projectId	String	*This field is only needed for v2.0 API Mandatory Project ID provided by Coda, unique for each title product - Refer to Getting started to find out how to get it.
initRequest.isTaxInclusiveAmount	Boolean	**This field is only applicable to the v2.0 API. Supported for the U.S. market only. Whether the summed `items[].price` Already includes tax. Applies only when Coda is MoR in a supported tax market (currently the US). When `true`, the item total is treated as tax-inclusive and charged as-is; when `false` (or omitted), it is treated as tax-exclusive and tax is added on top. Defaults to `false`** if omitted, preserving existing behavior. Ignored when Coda is not MoR. → See [Check Status - Tax handling] for how this affects the response and tax breakdown.
initRequest.orderId	String	Mandatory Your unique identifier for the transaction. Must be between 4 to 64 characters.
initRequest.currency	String	Mandatory ISO 4217 currency code - refer to Country and Currency Codes
initRequest.items	Array	Mandatory List of items being purchased by the users US and Canada supports one item only. Multiple items support is WIP.
initRequest.items[].code	String	Optional Code associated with the item on your side This field is mandatory for Taiwan Line Pay integration
initRequest.items[].price	Number	Mandatory Price of the item inclusive of any taxes in the currency specified in the request.
initRequest.items[].name	String	Mandatory Name of the item being purchased. Only supports latin characters.
initRequest.items[].skuImageUrl	String	Optional Publicly accessible URL for your SKU Image asset. Codapay will display this image on the checkout page for optimal checkout context & conversion-friendliness. NOTE: Some payment channels that are using an older version of our client will not display the SKU Image. We aim to ensure all payment channels are upgrade to new client version by end of 2026.
initRequest.profile	Object	Mandatory User profile information of the user making the purchase
initRequest.profile.entry	Array	Mandatory List of key-value pairs for profile information. Specific key-values that can be used to process currently are listed below.
initRequest.profile.entry[].key	String	Key for the profile entry
initRequest.profile.entry[].value	String	Key for the profile entry

#### Profile

Key	Expected value	Description
user_id	String	Mandatory Your user's unique identifier
in_frame_redirect	True or False	Optional If you're using the hosted payment page within an iframe on your website, you can use this parameter to control the behavior after the payment flow is completed. If True - when the user tries to close the Codapay window, the user will be redirected to the landing URL within the iframe If False - when the user tries to close the Codapay window, the user will be redirected to the landing URL on a new tab
return_url	String	Optional This allows you to pass dynamically the return url the user will be redirected to after the payment is complete. This URL may contain the following query strings placeholders which will be replaced by actual values: `{transactionId}` which will be replaced by Codapay Transaction Id `{orderId}` which will be replaced by “orderId“ parameter value This is optional, if this key-value is not used, Codapay will use the return url configured on publisher portal.
need_mno_id	Any value or null	If you initiated the payment with payType = 0 / 1 or carrier billing channels and wish to know which payment channel has been selected by your user, you can pass any non-null value in this field.
email	String	Optional The email address where the successful transaction receipt will be sent. Upon a successful payment, Coda will automatically deliver a digital receipt to this address. This feature is not enabled by default. To activate automated receipt delivery for your titles, please contact the payment enablement team at codapay_integration@coda.co. Receipt example:
client_ip	String	Optional This parameter (client_ip) is used to identify the user’s location and is only required if the payment channel specifically requests it. Must be in IPV4 format.
lang_code	String	Optional This parameter is used to select a language to use for the hosted payment page. The list of languages available for each country can be found here. e.g. en_US

### Response Parameters

Parameter	Type	Description
initResult	Object	Contains the result of the initiation request
initResult.resultCode	Integer	Result code for the initiation request. `resultCode = 0` if the request is successful. Otherwise, the resultCode value is an error. Full list of error Codes is available here.
initResult.resultDesc	String	Description of the error, resultCode is not 0.
initResult.txnId	Integer	Transaction ID for the initiated request. If the transaction initiation failed this value will be 0.
initResult.redirectUrl NEW	String	The URL to the checkout session. Applies to both Codapay Hosted Payment Page integration & Coda Links. Redirect the customers to this URL to proceed with checkout & payment. For example: `https://airtime.codapayments.com/airtime/begin?txn_id=714459463700207221`

### Samples {% tabs %} {% tab title="v2.0 Request" %} ```json { "initRequest": { "country": 158, "payType": 82, "apiKey": "live_****************************", "projectId": 21 //This field is only needed for v2.0 API "orderId": "12321312321314", "currency": 901, "items": [ { "code": "1", "price": 1000.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } } ``` {% endtab %} {% tab title="v1.0 Request " %} ```json { "initRequest": { "country": 158, "payType": 82, "apiKey": "e944d4*****************", "orderId": "12321312321314", "currency": 901, "items": [ { "code": "1", "price": 1000.00, "name": "Test Item" } ], "profile": { "entry": [ { "key": "user_id", "value": "105" } ] } } } ``` {% endtab %} {% tab title="Successful Response" %} ```json { "initResult": { "resultCode": 0, "txnId": 7714940366302672840, "redirectUrl": "https://airtime.codapayments.com/airtime/begin?txn_id=7144594637002072212&browser_type=mobile-web&utm_source=facebook” } } ``` {% endtab %} {% tab title="Failed Response" %} ```json { "initResult": { "resultCode": 103, "resultDesc": "This transaction has been cancelled. No charges were made. (error:103)", "txnId": 0 } } ``` {% endtab %} {% endtabs %} ### Profile Sample {% tabs %} {% tab title="Request" %} ```json "profile": { "entry": [ { "key": "user_id", "value": "test105" }, { "key": "in_frame_redirect", "value": "true" }, { "key": "return_url", "value": "https://www.example.com/{transactionId}/{orderId}/return" }, { "key": "need_mno_id", "value": "YES" } ] } ``` {% endtab %} {% endtabs %} # Display the Hosted Payment Page After obtaining the transaction ID, present the Hosted Payment Page to your user. There are several methods to display the Hosted Payment Page: * Redirect within the existing page * Open in a new tab * Embed within an iFrame * Display within a webview You can redirect the customer to the URL returned in the payment request initiation response. Alternatively, use the [Base URL provided below](#details) with appropriate parameters to open the Hosted Payment Page. ### Pre-requisite * You have received a success response from the [payment request initiation](/codapay/hosted-payment-page-integration/initiate-a-payment-request). ### Method 1 (Preferred): Using `redirectUrl` returned from payment request initiation to open the Hosted Payment Page You can use the `redirectUrl` returned in the Successful response of the payment request initiation to open the Hosted Payment Page. {% hint style="info" %} If you are within a Native App environment, we recommend opening the `redirectUrl` using an **external browser**, rather than the in-app web-views. {% endhint %} {% code overflow="wrap" %} ```json { "initResult": { ... "redirectUrl": "https://airtime.codapayments.com/airtime/begin?txn_id=7144594637002072212", ... } } ``` {% endcode %} #### Optional: Append optional query parameters to the redirectUrl before opening Refer to [#query-parameters](#query-parameters "mention") for a list of supported query parameters *** ### Method 2: Using the Base URL & attaching all query parameters to construct the Hosted Payment Page URL

Environment	Base URL
Sandbox	https://sandbox.codapayments.com/airtime/begin
Production	https://airtime.codapayments.com/airtime/begin

{% hint style="info" %} If you are within a Native App environment, we recommend opening the `redirectUrl` using an **external browser**, rather than the in-app web-views. {% endhint %} #### Query parameters

Parameter	Required	Description
txn_id	Mandatory	Mandatory The transaction ID you've collected after initiating the payment
browser_type	Optional	Optional If your user is on a mobile device, `browser_type=mobile-web` needs to be passed to make sure that the payment page is optimised to the device. If any other value or none is passed, the payment page will be optimised for a desktop view.
utm_souce	Optional	utm_source as it is detected in your page URL. For example, utm_souce=google, utm_source=coda
utm_medium	Optional	utm_medium as it is detected in your page URL. For example, utm_medium=banner, utm_medium=email
utm_campaign	Optional	utm_campaign as it is detected in your page URL. For example, utm_campaign=spring_sale, utm_campaign=new_season_launch
utm_content	Optional	utm_content as it is detected in your page URL. For example, utm_content=, utm_content=email

### Samples {% tabs %} {% tab title="Desktop on Sandbox" %} ``` https://sandbox.codapayments.com/airtime/begin?txn_id=7144594637002072212&utm_source=testing ``` {% endtab %} {% tab title="Mobile in Production" %} ``` https://airtime.codapayments.com/airtime/begin?txn_id=7144594637002072212&browser_type=mobile-web&utm_source=facebook ``` {% endtab %} {% endtabs %} ### Unlocking Marketing analytics on payment page Our payment page supports marketing analytics out-of-the-box. You can pass along UTM parameters from your store's page to the Codapay page. The UTMs will then be available in your payment funnel data analysis & marketing channel attribution analysis.
*\* We recommend that you pass along UTM parameters without any modifications, so that analytics data collected on the hosted payment page can be used together with other analytics data captured on your web page (for instance, data captured using Google Analytics) without any discrepancies.* #### Example: The user landed on your page with this UTM tracked URL:

https://game.webstore.com?utm_source=google&utm_medium=cpc&utm_campaign=123412341234&utm_content=creative_123

Then, when the user makes a purchase, you can pass along the UTMs to the Codapay page URL along with other mandatory URL parameters:

https://airtime.codapayments.com/airtime/begin?txn_id=7144594637002072212&browser_type=mobile-web&utm_source=google&utm_medium=cpc&utm_campaign=123412341234&utm_content=creative_123

### Special Considerations for Webviews #### Handling redirection Some channels may redirect users to their wallet app. To handle the redirections properly when using Webviews, you will need to use [WebViewClient.shouldOverrideUrlLoading](https://developer.android.com/reference/android/webkit/WebViewClient#shouldOverrideUrlLoading$android.webkit.WebView,%20java.lang.String$) using the intents below: | Regions | Channel list | Override URL | Only support external browser | | ------------- | ------------ | --------------------------------------- | ----------------------------- | | Brazil | PicPay | picpay:// | | | Brazil | AmeDigital | amedigital:// | | | Indonesia | GO-PAY | gojek:// | | | Indonesia | Shopee Pay |

shopeeid:// &
shopeepayid://

Android WebView Configuration

When using Android's WebView, configure `WebViewClient` as follows: 1. **Override the `onCreateWindow` Method:** ```java override fun onCreateWindow(view: WebView, dialog: Boolean, userGesture: Boolean, resultMsg: Message): Boolean { val newWebView = WebView(view.context) view.webViewClient?.let { newWebView.webViewClient = it } val webSettings = newWebView.settings setWebSettings(webSettings) (resultMsg.obj as WebView.WebViewTransport).webView = newWebView resultMsg.sendToTarget() return true } ``` 2. **Set WebView Settings:** ```java fun setWebSettings(webSettings: WebSettings) { webSettings.javaScriptEnabled = true webSettings.setSupportMultipleWindows(true) webSettings.domStorageEnabled = true webSettings.loadsImagesAutomatically = true webSettings.mediaPlaybackRequiresUserGesture = false webSettings.cacheMode = WebSettings.LOAD_DEFAULT } ```

ERR_UNKNOWN_URL_SCHEME

**Root Cause** The webview only recognizes standard URL schemes like `http` and `https`. Custom schemes, such as `weixin://` and `qunaraphone://`, are not recognized by the webview, leading to the error `ERR_UNKNOWN_URL_SCHEME`. This error indicates that the webview cannot handle the custom scheme provided by the payment channel. **Solution** To handle custom URL schemes, you need to override the `shouldOverrideUrlLoading` method in `WebViewClient`. This method allows you to intercept and manage URL loading behavior in Webview, ensuring that custom schemes are properly handled. Steps to implement the solution: 1. Implement the `shouldOverrideUrlLoading(WebView view, String url)` method in your `WebViewClient` class. 2. Configure the method to intercept URLs and handle custom schemes: * **Return `true`**: When the URL uses a custom scheme that needs special handling. This indicates that Webview should not handle the URL and allows you to process it as needed. * **Return `false`**: For standard schemes (`http`, `https`), allowing Webview to load the URL as usual. Example implementation: ```kotlin kotlinCopy codeoverride fun shouldOverrideUrlLoading(view: WebView?, url: String?): Boolean { if (url != null && url.startsWith("customscheme://")) { // Handle custom scheme return true } return false // Default behavior for standard schemes } ``` By implementing this method, you can ensure that custom URL schemes are properly redirected or handled according to your application's requirements, preventing the `ERR_UNKNOWN_URL_SCHEME` error.

Screen Rotation Issues

Screen rotation can cause the webview pages to refresh and display errors. **Solution** Add the following to your `AndroidManifest.xml` to prevent activity restart on screen orientation change: ```xml xmlCopy code ``` This ensures that the activity remains stable during screen rotation.

iOS Webview (about:blank)

Implement the `WKUIDelegate` delegate and set it to `_webview.uiDelegate`. Then implement: ```java - (WKWebView *)webView:(WKWebView *)webView createWebViewWithConfiguration:(WKWebViewConfiguration *)configuration forNavigationAction:(WKNavigationAction *)navigationAction windowFeatures:(WKWindowFeatures *)windowFeatures { if (!navigationAction.targetFrame.isMainFrame) { [webView loadRequest:navigationAction.request]; } return nil; } ```

iOS Webview (Capture redirect URL)

WKWebView is located at the iOS system level and cannot be directly accessed or modified via API. Due to the strict limitations of iOS, we recommend: ```java webView(_:createWebViewWith:for:windowFeatures adjust swift func webView(_ webView: WKWebView, createWebViewWith configuration: WKWebViewConfiguration, for navigationAction: WKNavigationAction, windowFeatures: WKWindowFeatures) -> WKWebView? { if navigationAction.targetFrame == nil { webView.load(navigationAction.request) } return nil } { if navigationAction.targetFrame == nil { webView.load(navigationAction.request) } return nil } ```

[^1]: These are UTM parameters added by Marketers to identify where users are coming to your page from. [^2]: Passing these UTM parameters along to Codapay page allows us to map the transaction to the marketing campaigns that brought them to the page. # Redirect URLs for Transaction Status Configure the appropriate redirect URLs to manage transaction status updates for your customers. These URLs determine which page a customer is redirected to after initiating or completing a transaction in Coda's payment interface. ## How to Configure Redirect URLs Partners can configure URLs in the Publisher Portal at any time. Refer to [Set up payments](/codapay/getting-started/set-up-payments) for instructions. Changes will take effect immediately. ## Types of Redirect URLs There are three types of redirect URLs that partners must configure. If categorization is not necessary, partners can reuse the same redirect address. 1. **Complete Landing Page URL**: Redirects customers to a page indicating the completion status of their transaction. 2. **Bank Transfer Transaction Pending Redirect URL**: Redirects customers to a page indicating their bank transfer transaction is pending. 3. **Convenience Store Transaction Pending Redirect URL**: Redirects customers to a page indicating their convenience store payment transaction is pending. ## Complete Landing Page URL When a customer leaves Coda's payment page after completing a carrier billing, e-wallet, or card payment, they are redirected to the Complete Transaction Redirect URL. This URL is accessed using a GET method with the following parameters:

Name	Type	Length	Description
TxnId	Numeric	N/A	Unique TxnId returned from the payment request initiation.
OrderId	String	64	Unique transaction identifier passed in the payment request initiation call.

**Example** ```url http://new.merchant.com/complete.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYYY ``` **Instructions** On this page, partners should state the result of the transaction to the customer. ## Bank Transfer Transaction Pending Redirect URL When a customer leaves Coda's payment page after initiating a bank transfer, they are redirected to the bank transfer transaction pending redirect URL. **This is only for Bank Transfers in Indonesia and Philippines.** This URL is accessed using GET method with the following parameters:

Name	Type	Length	Description
TxnId	Numeric	N/A	Unique TxnId returned from the payment request initiation.
OrderId	String	64	Unique transaction identifier passed in the payment request initiation call.

**Example** ```url http://new.merchant.com/atm-pending.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYY ``` **Instructions** Partners should display a message clarifying the order status, e.g., "Your order is confirmed and pending payment. Please follow the instructions provided to complete your payment at the ATM. Once your payment is completed, we will fulfill your order immediately." ## Convenience Store Transaction Pending Redirect URL When a customer leaves Coda's payment page after initiating a convenience store payment, they are redirected to the convenience store transaction pending redirect URL. This URL is accessed using GET method with the following parameters:

Name	Type	Length	Description
TxnId	Numeric	N/A	Unique TxnId returned from the payment request initiation.
OrderId	String	64	Unique transaction identifier passed in the payment request initiation call.

**Example** ```url http://new.merchant.com/otc-pending.php?TxnId=XXXXXXXXX&OrderId=YYYYYYYYY ``` **Instructions** Partners should display a message clarifying the order status, e.g., "Your order is confirmed and pending payment. Please follow the instructions provided to complete your payment at the convenience store. Once your payment is completed, we will fulfill your order immediately." # Get notified of a transaction status change Receive notifications of transaction status changes as your user progresses through the payment flow. During the payment flow, the transaction status will be one of the following: * Pending * Successful * Failed You will be notified whenever a transaction is marked as 'Successful' or 'Failed' via the Transaction Completion Notification URL configured in the Publisher Portal. ### Pre-requisite * The Transaction "Complete Notification URL" is configured in Publisher Portal. Refer to [Set up payments](/codapay/getting-started/set-up-payments) for detailed instructions. Changes will take effect immediately. ### Notification parameters Notifications are sent to the configured transaction complete notification URL with the appended query parameters below.

Parameters	Description
TxnId	Always The transaction ID generated during the payment request initiation
OrderId	Always Your Order ID, passed during the payment request initiation
*OriginAmount	*Always (v2.0 only) Original amount in OriginCurrency as provided in the initiation request
*OriginCurrency	*Always (v2.0 only) ISO 4217 alphabetic code (USD, IDR, etc). The original currency used in the initiation request to specify the item price. OriginCurrency can be different from PayCurrency.
*PayAmount	*Always (v2.0 only) Final price in PayCurrency charged to the user. Note: TotalPrice always = PayAmount
*PayCurrency	*Always (v2.0 only) ISO 4217 alphabetic code (USD, IDR, etc). Currency used for the actual payment charged to the user.
*SubTotalPrice	*Always (v2.0 only) The net amount of the transaction before taxes. Calculated as: `totalPrice / (1 + payTaxRate)`. This represents the base item price excluding local service or digital taxes.
*PayTaxRate	*Always (v2.0 only) The tax percentage rate applied to the transaction (e.g., `0.08` for 8%). This value is dynamically determined based on the merchant configuration, regional tax laws, or the user’s specific location (Zip Code).
resultDesc	Always The `resultDesc` parameter is designed to assist merchants in accurately analyzing and addressing the causes of transaction failures. If the `resultCode` equals `0`, the `resultDesc` will return Success. If the `resultCode` indicates an error, the `resultDesc` will provide a detailed description of the error.
ResultCode	Always The ResultCode will help indicate the status of the transaction. `ResultCode = 0` means the transaction is successful. `ResultCode =` 431, 481 or 216 means that the transaction is pending. All other ResultCode values mean that the transaction Failed. You can find the full list of error codes and their explanation here.
TotalPrice	Always The total amount the user has paid for the transaction. This will always be in local currency.
PaymentType	Always The PaymentType the user attempted to pay with. PaymentType is equal to the payment channel ID or 1 in case the payment channel is a Carrier Billing.
Checksum	Always The checksum helps verify that the message is sent by Codapay and has not been tampered with. Refer to the Security section for more information on how to use this value.
MnoId	Optional If the need_mno_id parameter was used during payment channel initiation, this parameter will contain the payment channel ID
USDPrice	Optional If a transaction is initiated in a country where USD is not the local currency, the Coda callback parameter (TotalPrice) will default display the user's local currency amount. If you require adding the initial USDPrice to the callback, please configure it from the Publisher Portal. Refer to the USD pricing section for more details.

### Expected Response After sending the notification, Codapay expects an acknowledgment to confirm it has been received. If your application processes the notification successfully, respond with 'ResultCode=0.' Otherwise, return an error code. If no response is received, the notification will be re-sent 3 times at 5-minute intervals. If all attempts fail, an email alert will be triggered. > To subscribe to transaction notifications, go to the [Publisher Portal](https://portal.codapayments.com/). > > Team > Manage Access > Tick "Transaction Notification" > Save Changes ### Sample {% tabs %} {% tab title="v2.0 Notification" %} {% code overflow="wrap" %} ```json5 // Sample for non-USD payments initiated https://? TxnId=7715121708032676249 OrderId=365f5Z619951c1a4b8 TotalPrice=1.00 PaymentType=237 ResultCode=0 Checksum=6b6c5e0f835f9f1442726bed3aedc3c9 PayTaxRate=8.00 //This field is only returned in v2.0 API PayCurrency=MYR //This field is only returned in v2.0 API PayAmount=1.00 //This field is only returned in v2.0 API OriginAmount=1.00 //This field is only returned in v2.0 API OriginCurrency=MYR //This field is only returned in v2.0 API SubTotalPrice=0.93 //This field is only returned in v2.0 API // Sample for USD payments initiated https://? TxnId=7715122576202672831 OrderId=365f5Z619951c1a4b8 TotalPrice=1.17 PaymentType=237 ResultCode=0 Checksum=10741fa6be7e6f2b189f029b3f8a0963 + USDPrice=0.30 PayTaxRate=8.00 //This field is only returned in v2.0 API PayCurrency=MYR //This field is only returned in v2.0 API PayAmount=1.17 //This field is only returned in v2.0 API OriginAmount=0.30 //This field is only returned in v2.0 API OriginCurrency=USD //This field is only returned in v2.0 API SubTotalPrice=1.08 //This field is only returned in v2.0 API ``` {% endcode %} {% endtab %} {% tab title="v1.0 Notification" %} {% code overflow="wrap" %} ```json5 // Sample for non-USD payments initiated https://? TxnId=7178589013775074766 OrderId=12321312321314 TotalPrice=100 PaymentType=101 ResultCode=0 Checksum=e944d44f065eade8157737385a094a57 + USDPrice=10.00 // Sample for non-USD payments initiated https://? TxnId=7178589013775038493 OrderId=12321312321314 TotalPrice=100 PaymentType=101 ResultCode=0 Checksum=10741fa6be7e6f2b189f029b3f8a0963 ``` {% endcode %} {% endtab %} {% tab title="Response" %} {% code overflow="wrap" %} ```json5 ResultCode=0 ``` {% endcode %} {% endtab %} {% endtabs %} ### Failed Transaction Notification In addition to successful transaction notifications, Codapay also supports **failed transaction notifications**. If a transaction does **not** reach a successful state, a notification will also be sent to the configured **Transaction Complete Notification URL** with the relevant transaction details. **Enablement**\ Failed transaction notification is not enabled by default. To enable this feature, please contact your **Coda Account Manager** or the **Integration Support team** at ****. ### Sample {% tabs %} {% tab title="v2.0 Notification" %}

// Sample for failed transaction notification
https://<your_webhook_url>?
  TxnId=7743322396792877759
  OrderId=20250611113402
  TotalPrice=2.00
  PaymentType=421
  ResultCode=750
  Checksum=ef631c0bef3249406cfe5c1350693195
  PayCurrency=MYR //This field is only returned in v2.0 API
  PayAmount=2.0 //This field is only returned in v2.0 API
  OriginAmount=2.0 //This field is only returned in v2.0 API
  OriginCurrency=MYR //This field is only returned in v2.0 API

{% endtab %} {% tab title="v1.0 Notification" %} ```json5 // Sample for failed transaction notification https://? TxnId=7743328618752877897 OrderId=123 TotalPrice=222222210.00 PaymentType=237 ResultCode=415 Checksum=f3a06cf11a0244b0308c8d8acbf53add resultDesc=This transaction has been cancelled. No charges were made. (error:415) ``` {% endtab %} {% endtabs %} ### Checking a transaction status We highly recommend using the [InquiryPaymentResult API ](/codapay/hosted-payment-page-integration/check-a-transaction-status)call after receiving the purchase notification webhook. This will help reconcile the transaction status between your system and Coda's before releasing the purchased item. # Fraud and Chargeback Notifications This reference describes the webhook notifications Coda sends to keep your backend informed of chargeback lifecycle changes and early fraud warnings on your transactions. > **Note:** Chargeback and Fraud notification will be sent via POST method ### Overview Codapay uses webhooks to notify your "Complete Notification URL" whenever a chargeback progresses through its lifecycle, or an early fraud warning is received on one of your transactions. > Ensure your "Complete Notification URL" is configured in the Publisher Portal. Refer to the [Set up payments](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#) guide for detailed instructions. ### Eligibility and Activation Fraud and Chargeback Notifications functionality is only available for merchants who have been explicitly enabled for this feature. To enable saved card functionality, contact your Codapay account manager or support team. ### Event Types #### Chargeback Events For chargeback lifecycle events, your endpoint should be prepared to handle the following `eventType` values: | Event Type | Description | | -------------------- | ------------------------------------------------------------------------ | | `chargeback_created` | A chargeback has been raised against a transaction | | `dispute_sent` | The chargeback has been escalated and a dispute submitted to the gateway | | `dispute_lost` | The dispute was resolved in the customer's favour | | `dispute_won` | The dispute was resolved in the merchant's favour | #### Fraud Events For fraud events, your endpoint should be prepared to handle the following `eventType` values: | Event Type | Description | | -------------------- | ---------------------------------------------------------- | | `fraud_notification` | An early fraud warning has been received for a transaction | ### Notification Payload Structure Notifications are sent as a `POST` request with a JSON body. | Field | Type | Description | | ------------------- | -------------- | -------------------------------------------------------------------------------------------- | | eventType | string | The specific event type being reported (e.g., `chargeback_created`) | | timestamp | string | Notification timestamp | | data.chargebackId | string | Coda's internal chargeback identifier | | data.stage | string | Lifecycle stage of the chargeback. See [Stage Values](#stage-values) below | | data.txnId | string | Coda's internal transaction ID | | data.reason | string | Chargeback reason as provided by the Issuing Bank (e.g. Other Fraud-Card Absent Environment) | | data.outcome | string \| null | Final outcome of a dispute: WON, LOST, or null if not yet resolved. | | data.amountValue | decimal | Transaction amount | | data.amountCurrency | string | ISO 4217 currency code (e.g. CHF, USD) | | data.orderId | string | Your order ID (if provided) | ### Stage Values | Stage | Meaning | | --------------------- | ------------------------------------------------- | | `CHARGEBACK` | Chargeback has been created | | `DISPUTE_SENT` | Dispute submitted to gateway | | `DISPUTE_LOST` | Dispute closed — outcome: lost | | `DISPUTE_WON` | Dispute closed — outcome: won | | `EARLY_FRAUD_WARNING` | Fraud signal received before chargeback is raised | ### Chargeback Notification Examples `chargeback_created` ```json { "eventType": "chargeback_created", "timestamp": "1773860416000", "data": { "chargebackId": "CBKJTNRS9XDNBVQ9", "stage": "CHARGEBACK", "txnId": "7677293394619242496", "reason": "Other Fraud-Card Absent Environment", "outcome": null, "amountValue": 100, "amountCurrency": "CHF", "orderId": "c8856951-b495-4e9b-8b48-01123cf4f5eb" } } ``` `dispute_sent` ```json { "eventType": "dispute_sent", "timestamp": "1773860416000", "data": { "chargebackId": "CBKJTNRS9XDNBVQ9", "stage": "DISPUTE_SENT", "txnId": "7677293394619242496", "reason": "Other Fraud-Card Absent Environment", "outcome": null, "amountValue": 100, "amountCurrency": "CHF", "orderId": "c8856951-b495-4e9b-8b48-01123cf4f5eb" } } ``` `dispute_lost` ```json { "eventType": "dispute_lost", "timestamp": "1773860416000", "data": { "chargebackId": "CBKJTNRS9XDNBVQ9", "stage": "DISPUTE_LOST", "txnId": "7677293394619242496", "reason": "Other Fraud-Card Absent Environment", "outcome": "LOST", "amountValue": 100, "amountCurrency": "CHF", "orderId": "c8856951-b495-4e9b-8b48-01123cf4f5eb" } } ``` `dispute_won` ```json { "eventType": "dispute_won", "timestamp": "1773860416000", "data": { "chargebackId": "CBKJTNRS9XDNBVQ9", "stage": "DISPUTE_WON", "txnId": "7677293394619242496", "reason": "Other Fraud-Card Absent Environment", "outcome": "WON", "amountValue": 100, "amountCurrency": "CHF", "orderId": "c8856951-b495-4e9b-8b48-01123cf4f5eb" } } ``` ### Fraud Notification Example `fraud_notification` ```json { "eventType": "fraud_notification", "timestamp": "1773860416000", "data": { "chargebackId": "CBKJTNRS9XDNBVQ9", "stage": "EARLY_FRAUD_WARNING", "txnId": "7677293394619242496", "reason": "Other Fraud-Card Absent Environment", "amountValue": 100, "amountCurrency": "CHF", "orderId": "c8856951-b495-4e9b-8b48-01123cf4f5eb" } } ``` ### Notification Signature Verification Every POST notification includes two headers that allow you to verify the request originated from Codapay and has not been tampered with: | Header | Description | | ---------------- | ---------------------------------------------------------------------------------- | | `X-Request-Time` | The timestamp of the request, represented as epoch milliseconds (string of digits) | | `X-Signature` | HMAC-SHA512 hex digest computed by Codapay using your merchant API key | #### How It Works Codapay and your server both agree on a single UTF-8 string to sign: ``` X-Request-Time + "." + raw POST body (UTF-8) ``` The HMAC-SHA512 algorithm is applied to this string using your merchant **API key**, producing a **128-character lowercase hexadecimal** digest. Codapay sends this digest in the `X-Signature` header. Your server must recompute the same hex digest and compare it to the received value. #### Validation Steps 1. Read the `X-Request-Time` and `X-Signature` headers from the incoming request. 2. Read the **raw body** bytes of the request. 3. Build the signed string: `requestTime + "." + body` (interpreted as UTF-8). 4. Compute the expected signature: `HMAC-SHA512(secretKey, signedString)` → lowercase hex. 5. Compare `expectedHex` to the `X-Signature` header value using a **constant-time** comparison to prevent timing attacks. The comparison is case-insensitive. If the values do not match, reject the request. #### Example — Java ```java import javax.crypto.Mac; import javax.crypto.spec.SecretKeySpec; import java.nio.charset.StandardCharsets; public class SignatureValidator { private static final String HMAC_SHA512 = "HmacSHA512"; public static boolean validate(String secretKey, String requestTime, byte[] body, String xSignature) { String bodyUtf8 = new String(body, StandardCharsets.UTF_8); String text = requestTime + "." + bodyUtf8; String expected = hmacSha512Hex(secretKey, text); return MessageDigest.isEqual( expected.toLowerCase().getBytes(), xSignature.toLowerCase().getBytes() ); } private static String hmacSha512Hex(String secretKey, String text) { try { Mac mac = Mac.getInstance(HMAC_SHA512); mac.init(new SecretKeySpec(secretKey.getBytes(StandardCharsets.UTF_8), HMAC_SHA512)); byte[] raw = mac.doFinal(text.getBytes(StandardCharsets.UTF_8)); return HEX.formatHex(raw); } catch (Exception e) { throw new IllegalStateException("HMAC-SHA512 not available", e); } } } ``` ### Responding to Notifications To acknowledge receipt of the notification, your server must respond with a `200 OK` and the following JSON body: ```json { "ResultCode": 0 } ``` Retry Policy: If no valid response is received, Codapay will re-send the notification 3 times at 5-minute intervals. If all attempts fail, an email alert will be triggered to your technical contact. # Activate POST Notifications This reference describes how to receive and process server-to-server webhook notifications from Codapay. These notifications keep your backend synchronized with the transaction status as a user progresses through the payment flow. Codapay supports two notification methods: * **GET Notifications (Legacy)** — Transaction status is sent as query parameters appended to your notification URL. * **POST Notifications** — Transaction status is sent as a JSON body in a `POST` request to your notification URL. > **Note:** GET notifications are the default method. To activate POST notifications, please contact your Codapay account manager. *** ## GET Notifications (Legacy) Receive notifications of transaction status changes as your user progresses through the payment flow. During the payment flow, the transaction status will be one of the following: * Pending * Successful * Failed You will be notified whenever a transaction is marked as 'Successful' or 'Failed' via the Transaction Completion Notification URL configured in the Publisher Portal. ### Pre-requisite * The Transaction "Complete Notification URL" is configured in Publisher Portal. Refer to [Set up payments](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#) for detailed instructions. Changes will take effect immediately. ### Notification parameters Notifications are sent to the configured transaction complete notification URL with the appended query parameters below: | Parameters | Description | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | TxnId |

Always
The transaction ID generated during the payment request initiation

| | OrderId |

Always
Your Order ID, passed during the payment request initiation

| | \*OriginAmount |

\*Always (v2.0 only)
Original amount in OriginCurrency as provided in the initiation request

| | \*OriginCurrency |

\*Always (v2.0 only)
ISO 4217 alphabetic code (USD, GBP, etc). The original currency used in the initiation request to specify the item price. OriginCurrency can be different from PayCurrency.

| | \*PayAmount |

\*Always (v2.0 only)
Final price in PayCurrency charged to the user. Note: TotalPrice always = PayAmount

| | \*PayCurrency |

\*Always (v2.0 only)
ISO 4217 alphabetic code (USD, GBP, etc). Currency used for the actual payment charged to the user.

| | \*SubTotalPrice |

\*Always (v2.0 only)
The net amount of the transaction before taxes.
Calculated as: totalPrice / (1 + payTaxRate). This represents the base item price excluding local service or digital taxes.

| | \*PayTaxRate |

\*Always (v2.0 only)
The tax percentage rate applied to the transaction (e.g., 0.10 for 10%). This value is dynamically determined based on the merchant configuration, regional tax laws, or the user's specific location (Zip Code).

| | resultDesc |

Always

The resultDesc parameter is designed to assist merchants in accurately analyzing and addressing the causes of transaction failures.

If the resultCode equals 0, the resultDesc will return Success.

If the resultCode indicates an error, the resultDesc will provide a detailed description of the error.

| | ResultCode |

Always

The ResultCode will help indicate the status of the transaction.

ResultCode = 0 means the transaction is successful.

ResultCode = 431, 481 or 216 means that the transaction is pending.

All other ResultCode values mean that the transaction Failed. You can find the full list of error codes and their explanation here.

| | TotalPrice |

Always

The total amount the user has paid for the transaction. This will always be in local currency.

| | PaymentType |

Always

The PaymentType the user attempted to pay with.

PaymentType is equal to the payment channel ID or 1 in case the payment channel is a Carrier Billing.

| | Checksum |

Always
The Checksum helps verify that the message is sent by Codapay and has not been tampered with. Refer to the Security section for more information on how to use this value.

| | MnoId |

Optional

If the need\_mno\_id parameter was used during payment channel initiation, this parameter will contain the payment channel ID

| | USDPrice |

Optional
If a transaction is initiated in a country where USD is not the local currency, the Coda callback parameter (TotalPrice) will default display the user's local currency amount.

If you require adding the initial USDPrice to the callback, please configure it from the Publisher Portal. Refer to the USD report section for more details.

| ### Expected Response After sending the notification, Codapay expects an acknowledgement to confirm it has been received. If your application processes the notification successfully, respond with `ResultCode=0`. Otherwise, return an error code. If no response is received, the notification will be re-sent 3 times at 5-minute intervals. If all attempts fail, an email alert will be triggered. > To subscribe to transaction notifications, go to the [Publisher Portal](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#). Team > Manage Access > Tick "Transaction Notification" > Save Changes ### Sample {% tabs %} {% tab title="v2.0 Notification" %} {% code overflow="wrap" %} ```json5 // Sample for non-USD payments initiated https://? TxnId=7715121708032676249 OrderId=365f5Z619951c1a4b8 TotalPrice=1.00 PaymentType=237 ResultCode=0 Checksum=6b6c5e0f835f9f1442726bed3aedc3c9 PayTaxRate=8.00 //This field is only returned in v2.0 API PayCurrency=MYR //This field is only returned in v2.0 API PayAmount=1.00 //This field is only returned in v2.0 API OriginAmount=1.00 //This field is only returned in v2.0 API OriginCurrency=MYR //This field is only returned in v2.0 API SubTotalPrice=0.93 //This field is only returned in v2.0 API // Sample for USD payments initiated https://? TxnId=7715122576202672831 OrderId=365f5Z619951c1a4b8 TotalPrice=1.17 PaymentType=237 ResultCode=0 Checksum=10741fa6be7e6f2b189f029b3f8a0963 + USDPrice=0.30 PayTaxRate=8.00 //This field is only returned in v2.0 API PayCurrency=MYR //This field is only returned in v2.0 API PayAmount=1.17 //This field is only returned in v2.0 API OriginAmount=0.30 //This field is only returned in v2.0 API OriginCurrency=USD //This field is only returned in v2.0 API SubTotalPrice=1.08 //This field is only returned in v2.0 API ``` {% endcode %} {% endtab %} {% tab title="v1.0 Notification" %} {% code overflow="wrap" %} ```json5 // Sample for non-USD payments initiated https://? TxnId=7178589013775074766 OrderId=12321312321314 TotalPrice=100 PaymentType=101 ResultCode=0 Checksum=e944d44f065eade8157737385a094a57 + USDPrice=10.00 // Sample for non-USD payments initiated https://? TxnId=7178589013775038493 OrderId=12321312321314 TotalPrice=100 PaymentType=101 ResultCode=0 Checksum=10741fa6be7e6f2b189f029b3f8a0963 ``` {% endcode %} {% endtab %} {% tab title="Response" %} {% code overflow="wrap" %} ```json5 ResultCode=0 ``` {% endcode %} {% endtab %} {% endtabs %} ### Checking a transaction status We highly recommend using the [inquiryPaymentResult API](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#) call after receiving the purchase notification webhook. This will help reconcile the transaction status between your system and Coda's before releasing the purchased item. *** ## POST Notifications POST notifications provide a more structured and extensible notification format using JSON payloads delivered via `POST` requests. > **Note:** POST notifications must be activated for your account. Contact your Codapay account manager to enable this feature. ### Overview Codapay uses webhooks to notify your "Complete Notification URL" whenever a transaction reaches a final state or a critical milestone. > Ensure your "Complete Notification URL" is configured in the Publisher Portal. Refer to the [Set up payments](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#) guide for detailed instructions. ### Event Types For Codapay integrations, your endpoint should be prepared to handle the following `eventType` values: | Event Type | Type | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------- | | `CHARGE_SUCCESSFUL` | [Transaction Notification](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#transaction-notifications) | The payment transaction is successfully completed. | | `CHARGE_FAILED` | [Transaction Notification](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#transaction-notifications) | The payment transaction failed. | | `SHOPPER_CREATED` | [Shopper Notification](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#shopper-notifications) | A new shopper profile is created. | | `PAYMENT_METHOD_ADDED` | [Payment Method Notification](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#payment-method-notifications) | The shopper successfully saved a new payment method. | | `PAYMENT_METHOD_REMOVED` | [Payment Method Notification](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#payment-method-notifications) | The shopper removed a saved payment method. | ### Notification Payload Structure Notifications are sent as a `POST` request with a JSON body. Each type of notification has a specific structure and content. #### **Transaction Notifications**

Field	Type	Description
eventType	string	The specific event type being reported (e.g., `CHARGE_SUCCESSFUL`)
txnId	string	The unique transaction ID generated by Coda
orderId	string	The merchant-side unique identifier for the order
checksum	string	A security hash used to verify that the notification payload has not been tampered with
chargedAt	string	Timestamp indicating when the transaction was processed.
amountValue	decimal	The final amount charged to the user in the billing currency
amountCurrency	string	The ISO 4217 currency code for the charged amount (e.g., `MYR`)
originalValue	decimal	The original price of the item before any currency conversions
originalCurrency	string	The ISO 4217 currency code for the original price
resultCode	integer	Status code of the transaction. `0` indicates success; other values indicate errors.
resultDesc	string	A human-readable description of the transaction result.
shopper	object	An object containing shopper details such as ID, email, or partner-specific identifiers.
paymentMethod	object	Information regarding the payment instrument used (e.g., card type, last four digits).
transactionData	object	A flexible object containing supplementary metadata specific to the transaction or payment channel.

**Successful Notification Example** ```json { "eventType": "CHARGE_SUCCESSFUL", "txnId": "1a2b3c4d5e6f7890", "orderId": "2a5eb9fe-3fc5-4a98-9f83-235b3f0c5d0f", "checksum": "f0c1eb25c01e4d5fd2fe8eb4091b82bc", "chargedAt": "2026-06-01T06:00:002", "amountValue": 59.0, "amountCurrency": "MYR", "originalValue": 15.0, "originalCurrency": "MYR", "resultCode": 0, "resultDesc": "Success", "shopper": {}, "paymentMethod": {}, "transactionData": {} } ``` **Failed Notification Example** When an event like `CHARGE_FAILED` occurs, the `resultCode` will contain a non-zero value. ```json { "eventType": "CHARGE_FAILED", "txnId": "1a2b3c4d5e6f7890", "orderId": "2a5eb9fe-3fc5-4a98-9f83-235b3f0c5d0f", "checksum": "f0c1eb25c01e4d5fd2fe8eb4091b82bc", "chargedAt": "2026-06-01T06:00:002", "amountValue": 59.0, "amountCurrency": "MYR", "originalValue": 15.0, "originalCurrency": "MYR", "resultCode": 706, "resultDesc": "Failed", "shopper": {}, "paymentMethod": {}, "transactionData": {} } ``` > You can find the full list of error codes and their meanings available [here](https://claude.ai/chat/cb09ca98-8996-43b7-87cb-cd20a04c1dea#). #### **Shopper Notifications** | Field | Type | Description | | ------------------ | ------ | --------------------------------------------------------------------------------------- | | eventType | string | The specific event type being reported (e.g., `SHOPPER_CREATED`) | | shopperId | string | The unique shopper ID generated by Coda | | partnerShopperId | string | The merchant-side unique identifier for the shopper | | checksum | string | A security hash used to verify that the notification payload has not been tampered with | | status | string | The status of the shopperld | | shopperInformation | object | Additional information about the shopper | **Notification Example** ```json { "eventType": "SHOPPER_CREATED", "shopperId": "shp_sg18bfbb8894ea0008", "partnerShopperId": "partner-shopper-345", "checksum": "?6c1eb25c01e4d5fd2fe8eb4091b82bc", "status": "active", "shopperInformation": { "email": "shopper@cool-shopper.com", "phoneNumber": "0553728274", "billingInformation": { "firstName": "John", "lastName": "Doe", "documentType": "CPF", "documentId": "18F2345432345", "address": "33 Main St.", "city": "Awesome City", "region": "CA", "country": "US", "zipCode": "91220" } } } ``` **Payment Method Notifications** | Field | Type | Description | | ------------- | ------ | --------------------------------------------------------------------------------------------- | | eventType | string | The specific event type being reported (e.g., `SHOPPER_CREATED`) | | timestamp | string | The timestamp of when the event occurred | | checksum | string | A security hash used to verify that the notification payload has not been tampered with | | status | string | The status of the link between the shopperId and the payment method | | shopper | object | An object containing shopper details such as ID, email, or partner-specific identifiers. | | paymentMethod | object | Information regarding the payment instrument used (e.g., token, card type, last four digits). | ### Responding to Notifications To acknowledge receipt of the notification, your server must respond with a `200 OK` and the following JSON body: ```json { "ResultCode": 0 } ``` Retry Policy: If no valid response is received, Codapay will re-send the notification 3 times at 5-minute intervals. If all attempts fail, an email alert will be triggered to your technical contact. --- [Next Page](/llms-full.txt/1)

CODAPAY

CODASHOP

WEBSTORE