}
}
```
## **Key Parameters**
Here are the essential parameters for configuring your subscription plans:
* **`plan_name`**: Name of the subscription plan.
* **`plan_desc`**: Description of the subscription plan.
* **`cycle_type`**: Frequency of recurrence (e.g., DAYS, WEEKLY or MONTHLY).
* **`cycle_interval`**: Specifies how often the billing cycle repeats.
* **`max_cycle_count`**: Maximum number of cycles for the subscription.
* **`has_trial_period`**: Indicates if a trial period is included.
* **`trial_period_duration_type`**: Unit for the trial period duration (e.g., DAYS).
* **`trial_period_duration`**: Length of the trial period.
* **`has_discount`**: Specifies whether a discount applies.
* **`discount_percentage`**: Discount percentage on the subscription price.
* **`discount_duration`**: Length of time the discount is applied.
## **To configure recurring payments**
* Login to DASGateway and click on the Merchant detail screen.
Navigate to your product list and select the Subscription product from the added product list.
Within the Subscription Product, create a new subscription plan by specifying details such as the plan name, billing frequency, and payment amount.
Once a subscription plan is created, subscription plans will appear in your list of available plan list. You can review, update, or duplicate plans as necessary.
To start a subscription, select a plan and assign it to a customer. Specify the link expiry date and plan start date, then click the submit button. A unique enrollment link will be generated.
Share the generated (HPP) link with the customer. They can use the link to review the plan, enter payment information, and complete enrollment.
Once the customer subscribes, their details are saved in the subscriber management section. You can access and update subscriber information as required.
## **Pause, Cancel, and Resume Active Subscription**
Managing Active Subscriptions: Pause, Cancel, and Resume
**1. Pause Subscription**
Purpose: This will temporarily stop the subscription without permanently canceling it.
Steps:
* Click on the subscriber management section.
* Select the active subscription you wish to pause.
* Click the "Pause" option and confirm the action.
Impact:
* No further charges will be made while the subscription is paused.
* The subscription can be resumed at any time by the merchant or user.
**2. Cancel Subscription**
Purpose: It will permanently stop the subscription and prevent any future billing.
Steps:
* Go to the subscriber management section.
* Choose the subscription to be canceled.
* Click the Cancel button and confirm the action.
Impact:
* The subscription is terminated immediately, or based on the end-of-billing-cycle option if supported.
* Customers will no longer receive services under the canceled subscription.
**3. Resume Subscription**
Purpose: This will reactivate a paused subscription to continue billing and service.
Process :
* Locate the paused subscription in the subscriber management section.
* Select the "Resume" option and confirm the action.
Impact:
* Billing resumes according to the original subscription terms.
* Services are resumed for the customer.
## **Best Practices for Subscription Management**
* **Create Distinct Plan Names**: Use clear and specific names for subscription plans to make management easier.
* **Set Appropriate Billing Intervals**: Ensure the billing frequency and amount match customer expectations to reduce churn.
* **Review Subscriber Details Regularly**: Keep subscriber information updated and review subscription statuses periodically.
## **Next Steps**
To start managing subscriptions, log in to your account and access the Subscription product. For further assistance or support, feel free to contact our team.
For detailed information about all merchant features and functionalities, you can download our comprehensive Merchant User Guide.
If you need further assistance, please [reach out to our support team](./support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.
# Merchant Settlement
Source: https://docs.paymentoptions.com/documentation/settlement/merchantsettlement
Understand how Payment Options handles merchant settlements and how to interpret your settlement reports.
# Settlement Process & Processing Summary
In the world of payments, **settlement** is the final and most crucial step. It’s the process where the merchant receives the actual funds from the card transactions processed via Payment Options. This page outlines how settlements work on our platform and explains the key metrics used in your merchant settlement reports.
***
## Payment Options Settlement Process
Payment Options manages payment processing across multiple **acquirers** and **payment methods**, ensuring that merchants get paid efficiently and securely.
### Step-by-Step Breakdown
### 1. **Transaction Initiation**
* A customer initiates a payment on the merchant’s website or app.
* Payment Options securely routes this transaction to the appropriate acquirer based on configuration.
* The acquirer **authorizes** the transaction after validating the card and available funds.
* If the authorization is successful, the transaction is tagged as **"Authorized"**.
* Depending on the merchant’s settings:
* **Purchase (Auto Capture)**: Payment Options automatically captures the amount.
* **Manual Capture**: The merchant captures the amount after fulfilling the service or product.
* Only **captured** transactions are considered eligible for settlement.
![Transaction Lifecycle Flow]()
### 2. **Settlement**
* Payment Options initiates the settlement process:
* Reconciles incoming settlement data from the acquirer with internal transaction records.
* Deducts the **Merchant Discount Rate (MDR)** and any applicable fees.
* Transfers the **net amount** to the merchant’s designated bank account as per the scheduled Payout Date.
* Merchants receive a **Settlement Report** on their defined cycle:
* **Daily**
* **Weekly**
* **Monthly**
![Statement Flow]()
### 3. **Merchant Payout**
* After reconciliation and fund transfer initiation, the final amount is credited to the merchant’s bank account.
* Settlement timelines may vary, depending on acquirer and settlement agreement.
![Reporting Metrics Logic Flow]()
***
## Processing Summary Definitions
These definitions help merchants interpret the figures shown in their **settlement reports**.
### 1. **Purchase / Capture Sales Amount**
**Definition**:
Total transaction amount where the payment was successfully captured.
**Includes**:
* Transactions where:
* `transaction_type = PURCHASE` and `transaction_status = Captured`
* OR
* `transaction_type = CAPTURE` and `transaction_status = Captured`
***
### 2. **Refund Amount**
**Definition**:
The total amount refunded to customers.
**Includes**:
* Transactions where:
* `transaction_type = REFUND` and `transaction_status = Refunded`
***
### 3. **Successful Transaction Count**
**Definition**:
Total number of successfully processed transactions.
**Includes**:
* Transactions where:
* `transaction_type = PURCHASE` and `transaction_status IN (Captured, Authorised)`
* PLUS
* `transaction_type = AUTHORISATION` and `transaction_status = Authorised`
***
### 4. **Declined Transaction Count**
**Definition**:
Count of all transactions that were not successful (i.e., declined or failed during processing).
**Includes**:
* Transactions where:
* `transaction_type = PURCHASE` and `transaction_status = NOT SUCCESSFUL`
* PLUS
* `transaction_type = AUTHORISATION` and `transaction_status = NOT SUCCESSFUL`
***
### 5. **Refund Fee Count**
**Definition**:
Number of successful refund transactions.
**Includes**:
* Transactions where:
* `transaction_type = REFUND` and `transaction_status = Refunded`
***
## Why This Matters
Understanding how settlement works ensures better **cash flow visibility** and allows your finance team to reconcile reports accurately. Our reports are designed to reflect the **real-time financial health** of your transactions — showing not only what was processed but also what was **paid out**.
***
# API DOCs Update log
Source: https://docs.paymentoptions.com/releases/apiupdate
Detailed log of API endpoint updates, new features, and improvements.
## **Overview**
The API Update Logs page documents changes, improvements, and updates specifically to the Payment Options API endpoints. This log helps developers stay informed about new endpoints, enhanced functionality, and modifications to existing API behaviors, ensuring smooth integration and usage.
***
### **API Version History**
#### Key Updates
* Introduced **Purchase API (v2)** and **Authorization API (v2)** for improved structure and future scalability.
* Enhanced support for evolving integration needs and upcoming compliance standards.
> **Notice**:\
> **Purchase API (v1)** and **Authorization API (v1)** are scheduled for deprecation.\
> Please migrate to v2 for all future integrations.
#### Key Features
* Core API endpoints for fundamental payment processing functionality.
* Initial support for essential payment methods (e.g., credit card transactions).
* Basic authentication setup, including security protocols to safeguard API access.
* Standard error handling with HTTP response codes for reliable troubleshooting.
***
## **Future Updates**
Each new version will be added as a separate accordion section here, highlighting key improvements and endpoint-specific changes to help developers stay updated and adapt to new features seamlessly.
***
## **Additional Resources**
Overview of all recent system revisions and enhancements, beyond API-specific changes.
Summarized release notes, with feature additions and bug fixes for each version of the gateway.
This page will be continuously updated to reflect the latest changes to API endpoints, new functionality, and improvements. For a broader view of system changes, visit the **Revision & Enhancement** and **Gateway Release Notes** sections.
# Gateway Release Notes
Source: https://docs.paymentoptions.com/releases/releasenotes
List of all releases with links to detailed notes for each version.
## **Overview**
This page provides a quick summary of each release, highlighting major updates and new features. For detailed release information, click on a specific version to view the complete release notes.
***
## **Release History**
### Features & Enhancements
* **Google Pay 3DS Support** for SCA/PSD2 compliance.
* **Traditional Chinese Language Support** across V3 Gateway and Hosted Payment Page (HPP).
* **Real-Time Refund Status Synchronisation** for supported acquirers.
* **Maximum Transaction Amount Limit** introduced as an additional transaction safeguard.
* **Extended Public Key Support:** Merchants can now submit **encrypted card details** using the Extended Public Key mechanism instead of sending **raw card data** in payment requests.
### DASPAY Readiness
* **DASPAY readiness has been completed**, including APIs, merchant configurations, payment flows, and Catalog capabilities.
* **Merchant-Level Tax & Service Charge Configuration** for Catalog Cart.
### Fixes & Improvements
* Fixed timeout issues affecting **Transaction Search and Preset Filters**.
* Fixed an issue when filtering transactions by **QR Product Type**.
* Fixed an issue where **Chargeback Email Notifications** were not delivered to updated email addresses.
* Corrected **Issuing Country** information displayed in Transaction Reports.
* Updated the **Phone Number** field on Hosted Payment Page (HPP) to support a maximum of **11 digits, depending on the applicable country code**.
### Features or Enhancements Related to Merchants & Partners
#### Transaction & Reporting Enhancements
* New Feature: **View Exact Fee Deductions Within Transaction Details**\
Allows users to easily view fee deductions directly within transaction details.
* Enhanced transaction download experience with improved report usability
* Retain previously used values in transaction download parameters for quicker report generation
* Added card details such as **Issuing Bank**, **Issuing Country**, and **BIN** in Transaction Reports
* Added **Schedule Name** prefix in transaction download files
* Improved Merchant View screen with **Advanced Filter** support
* Enhanced Business Location filtering with entity country support
* Display pricing and RR balance information within Merchant View
* Added **Customer Service Number** under Product Details
#### Disputes & Operations
* New Feature: **Custom Preference Lists for Dispute Management**\
Allows users to create and manage personalized preference lists for dispute handling.
* Improved webhook responses by including **Service** information for selected payment methods
* Enhanced release tour integration with notification support
#### Onboarding & Access
* New Feature: **Traditional Chinese Language Support in V3 Self-Onboarding**\
Added Traditional Chinese language support to improve onboarding accessibility for more users.
#### Critical Fixes & Stability Improvements
* Fixed payment issues affecting some iOS Chrome users
* Fixed duplicate transactions appearing in scheduled transaction reports
* Fixed refund notifications being triggered for unsuccessful refund transactions
### Features or Enhancements Related to Merchants & Partners
* New Feature: **Preset Filters on Transaction List**\
Allows users to quickly apply commonly used filters to find transactions faster.
* New Feature: **Improved Transaction Download**\
Enhances transaction download performance, allowing reports to be generated more efficiently.
* New Feature: **Transaction Report Preferences**\
Allows users to customize which fields are included when downloading transaction reports.
* New Feature: **Release Tour for New Features & Enhancements**\
Introduces a guided tour highlighting new features and improvements available in the system.
* New Feature: **Card Scheme Information for Apple Pay & Google Pay**\
Displays the card brand (such as Visa or Mastercard) and related information for successful Apple Pay and Google Pay transactions.
* New Feature: **Staff Access Role for Merchants (DASPay Integration)**\
Allows merchants to create staff users with limited access to help manage operations.
### Minor Enhancements
* Added **thousand separators** to amounts displayed in Transaction Summary statistics for improved readability
* Enhanced summary statistics to reflect filters applied on the transaction list
* Updated **Integration Method** filter to allow single selection for easier filtering
* Added **Payment Type** and **Card Scheme** options to advanced transaction filters
* Removed expiry date requirement for **ID documents** during merchant self-onboarding
* Improved **currency selection** based on the selected entity during self-onboarding
* Improved flexibility of **statement preference settings**
### Features or Enhancements Related to Merchants & Partners
* New Feature: **DASPAY Device Management**\
Enables onboarded merchants to manage their registered devices directly within the system.
### Minor Enhancements
* Increased file upload limit from **3 to 5** in Self On-boarding
* Updated **Contains** operator logic in Next Gen Filter to support comma-separated strings
* Display **Merchant Catalog** tab for merchants subscribed to DASPay product
* Added **default product image** when no image is uploaded in Merchant Catalog
* Added dropdown filter values for **Food Size** and **Portion Size** in Merchant Catalog
* Display a **default image** on Edit Product screen when no image was uploaded during creation
* Updated **Lost Funds date** to reflect the case creation date for Chargeback
### Features or Enhancements Related to Merchants & Partners
* New Feature: **Tokenization Implementation** for AsiaBill Acquirer
* New Feature: **SubURL added to Sub-Merchant Information** in Payment Requests for Worldpay Integration
### Minor Enhancements
* Discontinue the **V2 (legacy) screens** from V3 Gateway
* Include **updated webhook URL** in previous comments
* Update **translation** on Merchant Details tab
* Remove **Scroll Bar** on Merchant Settings tab
* Add **‘Not Submitted’ Status** in filter on Merchant/Partner under Sales Lead
* Preference (column) now only gets added after clicking **Apply button**
* Minor update in **Transaction Count Download**
* Identify **Payment Type and Schemes** on Transaction Details page
* UI modifications on **Refund Percentage** screen
* Interface improvement for **Release Notes / Change Log**
* Add **‘Food Type’ and ‘Portion Size’** fields on Add Product screen in Merchant Catalog
* Document type update in **Self On-boarding**
* Add **Refund Balance Summary** under Merchant Details
### Major Enhancements
* Merchant Settlement Statement: Implementation of **Bi-Monthly Statement Cycle**
### Performance Improvements
* Improved **Statement List** performance by moving data formatting from DB to UI
* Improved **Transaction List** performance when using Advanced Filters
### Features or Enhancements Related to Merchants & Partners
* New Integration: **Cybersource Acquirer** (3DS & Non-3DS)
* New Integration: **YOQO Acquirer** (3DS)
* New Integration: **Google Pay**
* New Feature: **Stats Tiles** (Total Sales, Total Refund, Approval Ratio) added as Quick Stats on Transaction UI
* New Feature: **Browser Information** now displayed on Transaction Detail screen
* New Feature: **Merchant Settings** tab added to Merchant Details
* New Feature: **IP Whitelisting Configuration & Webhook URL Configuration** in Merchant Settings
* New Feature: **Merchant Catalogue** tab added to Merchant Details
### Minor Enhancements
* Standardized terminology from **Login/Logout** to **Sign In/Sign Out** across DAS Gateway
* Added **Logical Operator (AND/OR)** in Next Gen Filter between conditions
* Added **Email Notifications** for Primary Contact (Merchant) under User Settings
* Display **Merchant ID** field in User Profile and Merchant screen for Merchant Users
* Allow **currency selection for Aggregation** under User Profile
* Display **Acquirer MID** on Product Details page for Merchant login
* Added **Payment Type** (Card Payment or APM) separated from Scheme
* Transaction Download updated to accommodate **Payment Type**
* Display all logged cases in **Chargeback History** for a Transaction in Chargeback UI
* JP Translation: Billing Cycle value on Subscription HPP
* JP Translation: Billing Cycle value in Subscription Email
### Chargeback Enhancements
* Renamed **Amount** field to **Dispute Amount** for Chargeback Case
* Unified all Chargeback notifications to a **single email template**
* Highlight indicator dot only for stages where user is present in Chargeback History
* Email notifications sent to Merchant for **any edits to existing Chargebacks**
* Support reopening/closure of a Chargeback (via Edit) in Case Discussion
* UI updates on Transaction Details screen related to Chargeback
* Display **System\_User** for automated updates in Chargeback cases
* Removed **‘Internal Dispute’** from Chargeback case type list
* Added internal **‘Case Created’** stage in Chargeback Case Discussion
### Features or Enhancements Related to Merchants & Partners
* External users (Merchant/Partner) support enabled
* New Integration: **Cybersource Acquirer** (3DS & Non-3DS)
* New Integration: **YOQO Acquirer** (3DS)
### Minor Enhancements
* Auto-populate **City** & **Address** based on postcode during Onboarding
* Password Policy: Enforced **minimum 14-character** requirement
* Amount formatting: Added **currency symbol prefix** across DAS Gateway
* Transaction List: Added **Acquirer** & **Acquirer MID** columns for Merchant login
* Transaction List: Added **Integration Type** field and column
* Transaction Download Report: Included **Integration Type**
* Gateway: Updated **Gateway Response** message formatting
* Gateway (Asiabill): Mapped **Response Code** to **Acquirer Message**
* Product Page: Renamed **Connection Methods** field to **Integration Type**
* HPP Page (EN/JP): Improved **Expiry Date** field (manual input + dropdown)
* Chargeback: Included **JP Sales Team** in notifications for JP merchants
* Chargeback: Added new **Case Type** – *Evidence under Review*
* DAS Gateway: Unified field name **Reason Description** across all screens
* Chargeback Email: Standardized **subject line** across all notifications
* Chargeback Report: Added **Merchant Account (English)** parameter
* Chargeback: Removed *Sent to Acquirer* option for **Auto Representment** case
* Chargeback: Added **email notifications** for *Evidence under Review* case
* Statements UI: Added **Deselect All** button for selected statements
* Partner View: Renamed **Reseller** tab to **Partner** for partner user accounts
### Features & Enhancements Related to Merchants & Partners
* eKYC for Reseller Stakeholders
* Multiple statements download in DAS Gateway
* User preference for transaction & statement list columns
* Custom date-time format across DAS Gateway
* File type preference (Excel/CSV) for transaction & chargeback downloads
* Smart copy on key fields
* Export to Excel on Public Holiday UI
* Block refund (condition-based)
* Payment intermediate interface for seamless Merchant integration
### UI & UX Enhancements
* Redesigned:
* Merchant View Page
* Partner Details Page
* Improved:
* Alignment for Integration Method on Transaction List UI
* Statement & Transaction Screens for better visibility
* Chargeback Notification Email content
* Merchant View list tooltips for product count
* Adjusted column widths across DAS Gateway
* Added:
* Acquirer details on Product View, Product Info, and Drawers
* Dropdown for IsWhitelisted filter in Statement Transactions
* Transaction ID column in Transaction List & Advanced Filters
* Tooltip for failed transactions (Response Code & Gateway Response)
* Removed:
* Excessive whitespace on Transaction List UI
* Decimal places for JPY currency on Statement UI
* Updated Password Policy to comply with PCI Guidelines
### Minor Enhancements
* Unified field names (Subsidiary/Entity/Country) across Gateway
* Improved Self Onboarding: Data saving via Step buttons
* Prevented product display for pending DASMID on Merchant Page
* Limited multiple statement downloads
* Standardized Chargeback Email content
* Added Billing Dates & Next Billing Date for Subscription (HPP)
* Added Comment function for Subscription (HPP)
* Japanese Translation for Self Onboarding Final Step Page
### Production Defect Fixes
* Fixed:
* Transaction download failure for external users
* Dispute email missing currency in amount field
* UI issues on HPP Page (IBEC)
* Multiple email notifications on successful payment refresh
### Features or Enhancements Related to Merchants & Partners
* e-KYC Integration on auto onboarding
* Updated Links: Implemented across the Gateway for easier navigation
* Improved Loading Screens
* New Payment Integrations: PayPay, Pay-easy, and Konbini (New APM options for JP region)
* UI Improvements:
* Default column selections in various interfaces
* Terms & Conditions updated
### Minor Fixes and Enhancements
* Updated Error Descriptions
* Miscellaneous: Improved navigation, sub-user settings, and email notifications
### Defect Fixes
* Resolved the issue of multiple webhooks being sent for a single transaction
* Resolved problems preventing resellers from viewing their approved merchants
* Fixed problems with transaction responses, including Google Pay and chargeback errors
* Resolved an issue where certain transactions returned inconsistent response codes
### Features or Enhancements Related to Merchants & Partners
* HPP Page Updates
* Added new fields for enhanced cardholder input
* Included accessibility options for better usability
* Enhanced support for memo text input
* Pay by Link enhancements: Added a link name column within the transaction lists and reports for easier identification
* Subscription Notifications: Enhancement to remove time zone offset from start date, end date, and link expiry date from subscription email notification
### Minor Fixes and Enhancements
* Password Management: Users will now be required to reset passwords every 90 days
* Transaction Management: Improved filtering and sorting for transactions, and added new notifications for expired passwords on the gateway
* Legacy Screen Notices: Added messages to inform users when they are on outdated screens in the system
* Referrals: Added a referral count to the Partner list
This Release Notes section will continue to grow as new versions of the gateway are released. Bookmark this page to stay up-to-date with the latest improvements and features.
# Revision & Enhancement
Source: https://docs.paymentoptions.com/releases/revisions
Log of all significant revisions and enhancements to the product.
## **Overview**
The Revision & Enhancement log records major updates, feature improvements, and optimizations made to the system. This format allows users to easily view the latest changes, with each version stored in an expandable section.
***
### **Revisions by Version**
#### Updates & Changes
| **Change** | **Description** |
| :----------------------------------- | :----------------------------------------------------------------------------------------------------------- |
| **Refund API – E-Wallet Limitation** | Refunds are **not supported** for transactions made using **PayPay, Pay-Easy, and Konbini** payment methods. |
**Note:** This update is a **documentation clarification** and does not introduce any functional API changes.
#### Updates & Changes
| **Change** | **Description** |
| :-------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **DEV API Base URL Update** | The **DEV environment** API base URL has been changed from `https://api-dev.paymentoptions.com/api/v1` to `https://api-dev.paymentoptions.com`. All DEV API endpoints in the documentation have been updated accordingly. |
**Note:** This update only affects the DEV environment. Please update any development or staging integrations to use the new base URL.
#### New Enhancements
| **Feature** | **Description** |
| :----------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Gateway Error Codes Update** | Updated and refined **Gateway Error Codes** in documentation to include detailed response codes, messages, and applied levels for better clarity and troubleshooting. |
#### New Enhancements
| **Feature** | **Description** |
| :------------------------------ | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **E-Wallets Section Expanded** | Added **Apple Pay** and **Google Pay** under the `Documentation → Payment Methods → E-Wallets` section. [View Section](/documentation/paymentmethods/ewallets) |
| **Supported E-Wallets Updated** | Moved **PayPay**, **Gcash**, **PayEasy**, and **Konbini** from the upcoming list to the official list of supported e-wallets. |
| **HPP API Update** | Updated the `Hosted Payment Page` API reference with configuration for **Apple Pay** and **Google Pay** button priority. [View API](/api-reference/en/hpp/generate-link) |
| **Tokenization Flow Updated** | Replaced the **Generate Token API** flow diagram with a new version to better explain token handling and reassure merchants that card details are not stored. |
#### New Enhancements
| **Feature** | **Description** |
| :---------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **New Documentation Section** | Added a new page under `Documentation → Settlement` titled **"Merchant Settlement"**.
This page explains how Payment Options handles merchant settlements, outlines the full settlement process, and defines key reporting metrics. [View Page](/documentation/settlement/merchantsettlement) |
#### New Enhancements
| **Feature** | **Description** |
| :---------------------- | :--------------------------------------------------------------------------------------------- |
| **API Response Update** | Added the `merchant_ip` field under **device\_details** in the API response, where applicable. |
#### New Enhancements
| **Feature** | **Description** |
| :--------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Introduction to Payments** | Added a new section under `Documentation → Payments` titled "Introduction to Payments" which includes:
- Key Participants in the Card Payments Ecosystem
- How Card Payments Work – From Initiation to Authorization
- Settlement – How Merchants Receive Their Funds
- Our Role – What We Offer and How We Simplify Payments. [View Section](/documentation/payments/paymentintro) |
| **API Navigation Update** | Added **Purchase API (V2)** and **Authorisation API (V2)** under the **Server To Server** section in the API Reference. |
#### New Enhancements
| **Feature** | **Description** |
| :---------------------- | :------------------------------------------------------------------- |
| **Language Navigation** | Minor updates on the language navigation for better user experience. |
#### New Enhancements
| **Feature** | **Description** |
| :------------------- | :------------------------------------------------------------------------ |
| **JP Documentation** | Implemented the Japanese version of the documentation. |
| **API Endpoints** | Minor updates on creating submenu of API Endpoints for better navigation. |
#### New Enhancements
| **Feature** | **Description** |
| :----------------------- | :----------------------------------------------------------------------------------------------------------------------------------------- |
| **API Reference** | Added the 3D Secure Integration API to the Server-to-Server API Reference. |
| **API Endpoints** | Updated the order of Authorization and Body attributes to align with the cURL payload. |
| **Gateway Error Codes** | Reviewed and updated error messages in the Error and Response sections of the API Reference. |
| **Gateway Release Note** | Updated the Release History for Gateway Release Notes. Included features and enhancements related to Merchants and Partners in Release 21. |
#### Highlights
* **Platform Migration**: Moved to the Mintlify platform with a refreshed interface, interactive features, and AI-powered search.
* **Expanded Payment Methods**: Added support for new e-wallets like Apple Pay and Google Pay.
* **Enhanced Security & Compliance**: PCI DSS 4.0 compliance, new 3DS protocols, and additional data security measures.
* **Localization & Accessibility**: Launched Japanese language support, with potential for further localization.
#### Additional Improvements
| **Feature** | **Description** |
| :--------------------------------------- | :------------------------------------------------------------------------------------------------------------ |
| **AI-Powered Search** | New intelligent search function to improve navigation and help users find content quickly. |
| **User Interface Enhancements** | Improved navigation with categorized sections and direct access to FAQs and guides. |
| **Diagrams, Flowcharts & Process Flows** | Added visual aids, including flowcharts and process flows, to illustrate key integrations and configurations. |
| **Gateway Access Links** | Provided direct links to gateway features and tools for easy integration and account management. |
| **Performance Optimizations** | Improved API response times to handle high traffic volumes. |
***
## **Additional Resources**
Detailed logs of API-specific updates, new endpoints, and code examples.
Recent release notes, highlighting new features, bug fixes, and other updates on the gateway.
This log will be continuously updated as the Payment Options Gateway evolves. For a closer look at specific updates, refer to **Gateway Release Notes** and **API Update Logs**. Visual aids such as diagrams, flowcharts, and process flows are integrated throughout the documentation to simplify understanding of complex setups and integrations.
# AI Chatbot
Source: https://docs.paymentoptions.com/support/aichat
Learn how to use the integrated AI chatbot and search feature to get real-time assistance with Gateway documentation and troubleshooting.
Our integrated **AI Chatbot** is designed to provide real-time assistance and quick answers to your questions while navigating the Gateway documentation. Powered by advanced AI technology, this tool helps you find relevant information, troubleshooting tips, and usage instructions without having to search manually.
### **Why Use the AI Chatbot?**
* **Instant Answers**: Receive quick responses to common questions, helping you save time and stay focused.
* **Search Documentation**: The chatbot is directly integrated with our documentation, making it easy to pull up guides, API references, and troubleshooting articles.
* **24/7 Assistance**: Access the AI chatbot anytime for around-the-clock support, without waiting for a support representative.
* **Troubleshooting Help**: Get suggestions for resolving common issues as you work through different aspects of the Gateway.
### **How to Access the AI Chatbot**
To start using the AI chatbot:
1. **Use the Search Bar**: At the top of any page in our documentation, enter your question or keyword into the search bar.
2. **Instant Suggestions**: As you type, the AI chatbot will provide suggested articles and answers, helping you find relevant information faster.
3. **Explore Results**: Click on a suggestion or press **Enter** to view detailed responses and related documentation that address your query.
The AI Chatbot is designed for informational and troubleshooting assistance. For more complex issues or account-specific help, please [contact our support team](./support/contact).
## **Tips for Effective Use**
* **Be Specific**: For the best results, ask specific questions (e.g., "How do I set up a Subscription product?" rather than "Setup help").
* **Explore Suggestions**: The chatbot often provides links to relevant documentation. Click these links to explore the full guides.
* **Try Multiple Queries**: If the first response isn’t helpful, try rephrasing your question or breaking it into smaller parts.
***
## **What Can the AI Chatbot Help With?**
Find guides on using Gateway features, setting up products, and navigating your account.
Access API references, endpoint details, and authentication methods directly within the chat.
Get solutions to common issues, including payment errors, account access, and integration challenges.
Discover tips and best practices for maximizing the functionality of the Gateway.
***
## **Need Further Assistance?**
For complex or account-specific issues, please [reach out to our support team](./support/contact). Our team is ready to assist with any questions the AI chatbot can’t address.
# Contact Support
Source: https://docs.paymentoptions.com/support/contact
Reach out to our support team for assistance with Gateway-related issues or questions.
Our support team is here to help with any questions or issues you may encounter while using the Gateway. Whether you need technical assistance, have account-related inquiries, or want guidance on using specific features, we’re here to assist you.
## **When to Contact Support**
If you’re new to the Gateway, we recommend reviewing the [Onboarding Checklist](/documentation/checklist) first. If you still have questions, contact us for personalized help.
For API errors, payment processing issues, or plugin installation problems, please reach out to our support team. You can also check our [FAQs & Troubleshooting](./faqs) for quick solutions.
For inquiries related to billing, account upgrades, or changes, contact support, and we’ll guide you through the necessary steps.
## **How to Reach Us**
For detailed inquiries or when you need to share documentation, please email us at **[support@paymentoptions.com](mailto:support@paymentoptions.com)**. We aim to respond within 1-2 business days.
Use the **AI Chatbot** available in the search bar for instant answers to common questions. For real-time support with a representative, our live chat is available during business hours.
# FAQs & Troubleshooting
Source: https://docs.paymentoptions.com/support/faqs
Frequently asked questions and troubleshooting guide for merchants using the Gateway.
Welcome to the **FAQs & Troubleshooting** section. Here, you’ll find answers to commonly asked questions, along with solutions for common issues you might encounter while using the Gateway. This section is designed to help you get the most out of our products and resolve issues quickly.
## **Frequently Asked Questions**
Visit our [Create an Account](/documentation/createaccount) page for step-by-step instructions on setting up your merchant account.
For a full list of required documents, see our [Onboarding Checklist](/documentation/checklist).
Once your account is set up, navigate to the **Products** tab and select the products you want to enable. Each product guide provides further details.
A Payment MID (Merchant Identification Number) is a unique identifier assigned to a business by Payment Options. This number is used to track and authenticate transactions made by the merchant, ensuring that payments are processed and settled to the correct business account.
An acquirer (also called an acquiring bank, acquiring financial institution, or merchant bank) is a financial institution or payment processor that partners with merchants to enable them to accept credit card, debit card, and other electronic payments. The acquirer provides the merchant with a merchant account and facilitates the authorization, processing, and settlement of transactions between the merchant and the customer's bank (the issuer).
Customers that will use Payment Options as their payment gateway are merchants.
Customers that onboard other merchants onto the Payment Options gateway services are partners.
An API (Application Programming Interface) is a set of rules, protocols, and tools that allows different software applications to communicate and interact with each other. It defines the methods and data formats that applications can use to request and exchange information. For more information, [Click here](https://en.wikipedia.org/wiki/API).
An issuer is a bank or financial institution that provides credit cards, debit cards, or other payment cards to consumers (cardholders). The issuer is responsible for approving the cardholder's application, managing their account, and making sure the funds are available for purchases or withdrawals.
Dasgateway is the name of our payment gateway platform. To access Dasgateway, please log in to your merchant or partner account [here](https://me.paymentoptions.com/login).
A payment gateway is a service that authorizes and processes payments for online and in-store transactions. It securely transfers payment information between the customer, merchant, and bank.
The payment gateway encrypts sensitive payment information, verifies transaction details, and communicates with the bank to authorize the payment. It then returns the status of the transaction (approved/declined).
Our payment gateway supports various payment methods, including credit/debit cards, digital wallets, and alternative payment methods like Google Pay, Apple Pay, and PayPay. For more information, please refer to the [payment methods](/documentation/paymentmethods/cardschemes) segment.
Yes, our payment gateway uses industry-standard security protocols such as SSL encryption, tokenization, and PCI-DSS compliance to ensure that your transactions are safe and secure.
You can integrate our payment gateway using our API or pre-built plugins for popular platforms such as WooCommerce, OpenCart, and Magento. We provide detailed documentation and developer support for the integration process in our [guide](/support/merchantguide) section.
The setup fees may vary depending on the plan you choose. Please refer to our [pricing page](https://www.paymentoptions.com/ja/pricing/) for detailed information about our fee structure and subscription plans.
Most transactions are processed in real-time, meaning payments are authorized and confirmed instantly.
If a payment fails, the payment gateway will notify both the customer and the merchant. The customer can attempt to re-enter payment details or use a different payment method.
Yes, our payment gateway supports recurring billing and subscription payments. You can set up automated payments for your customers based on your subscription model. For more information, please refer to the [Subscription](/api-reference/en/subscription/create-subscription) page.
Yes, depending on your needs, our payment gateway supports international payments. It allows you to accept payments in multiple currencies and from different countries. Please [contact support](/support/contact) for more information on the availability of multiple currencies on your account.
We charge transaction fees, which vary depending on the volume of payments processed and the payment methods used. Please refer to our [pricing page](https://www.paymentoptions.com/ja/pricing/) for a breakdown of fees.
You can access your transaction history through the merchant dashboard, where you can see details of all successful, pending, and failed transactions.
Our [support](/support/contact) team is available via email, and phone. We also have a comprehensive help center with troubleshooting guides, FAQs, and tutorials.
Yes, our payment gateway allows you to issue refunds directly from the merchant dashboard for both full and partial refunds.
We use advanced fraud protection tools and 3D Secure authentication to help prevent unauthorized transactions. You will also receive alerts in case of any suspicious activity.
Yes, you can customize the look and feel of the payment form to match your brand’s identity using our API.
PCI (Payment Card Industry) compliance is a set of security standards to ensure the secure handling of cardholder data. Our payment gateway is PCI-DSS compliant, so you don’t need to worry about it, but we recommend that you follow best practices for your business as well.
Yes, our payment gateway is fully compatible with mobile apps, however we do not provide SDKs for development.
You can update your payment settings, bank details, and account information by contacting our [support](/support/contact) team.
Yes, we do have a sub user feature, please contact the [support](/support/contact) team to set up your new sub user.
Yes, please contact the [support](/support/contact) team as we offer a sandbox or test environment where you can simulate payments and ensure that everything works correctly before you start processing live transactions.
Our Gateway supports multiple payment methods, including credit cards, e-wallets, QR codes, and more. Check the [Supported Card Schemes](/documentation/paymentmethods/cardschemes) and [E-Wallets](/documentation/paymentmethods/ewallets) sections for details.
3D Secure is enabled at the product level. Visit the **Secure Payment** section to understand how to configure 3DS for enhanced transaction security.
Yes, our Gateway supports multiple currencies. For a list of supported currencies, refer to the [Currency Guide](/documentation/paymentmethods/currency).
A chargeback is a process in which a credit card or debit card transaction is reversed by the cardholder's bank (the issuer) after a customer disputes a charge. Essentially, a chargeback allows the customer to get their money back if they believe a transaction was fraudulent, erroneous, or otherwise problematic.
A refund is the return of money to a customer after they have paid for goods or services, typically because the customer is dissatisfied with the purchase or because there was an issue with the product or service. A refund is a voluntary action by the merchant (or seller), unlike a chargeback, which is initiated by the customer through their bank.
You can generate HPP links directly from the HPP product dashboard. For details, see the [HPP Guide](/api-reference/en/hpp/generate-link).
Our API uses HTTP Basic Authentication with an API key in the `Authorization` header. Refer to the [API Authentication](/api-reference/en/authentication) page for details.
Plugins for platforms like WooCommerce, Magento, and OpenCart are available on our [Website Plugins](/support/plugins-woocommerce) page.
The API supports JPY, PHP, USD. Please refer to the [Currencies](/documentation/paymentmethods/currency) section in the documentation for a complete list.
Please refer to the [changelog](/logs/apiupdate).
Yes, please refer to the [webhook handler](/api-reference/en/webhook-handler) page.
Weekly Statements: Weekly statements cover the period from Monday to Sunday and are released on the following Monday of the next week.
Monthly Statements: Monthly statements cover the period from the 1st to the end of the month and are released on the second Monday of the following month. Note: If the scheduled Monday falls on a holiday, statements will be released on the next business day.
Yes, you may see it in real time on your [Dasgateway](https://me.paymentoptions.com/login) page.
On the Transaction page, press the "Additional column" button on the top left and select the fields you wish to be added.
Please reach out to your sales representitive, or if you have any additional questions or concerns, please contact our [customer support team](/support/contact). We are happy to assist you with the account termination process.
Please note: Once your account is terminated, all data associated with it may be permanently deleted, and you will no longer have access to any services associated with your account.
Please refer to: [Generate HPP](/api-reference/en/hpp/generate-link)
***
## **Troubleshooting Guide**
This section addresses common issues users encounter. If you’re experiencing a specific problem, review the solutions below.
Go to the login page and click **Forgot Password**. Follow the instructions to reset your password via email.
Double-check your username and password. Ensure you’re using the correct credentials associated with your account. If the issue persists, contact support.
This error occurs when the cardholder's account has insufficient funds. Ask the customer to try another card or contact their bank.
Ensure the customer has completed the 3D Secure authentication step. For more on 3DS, see the [Secure Payment](/documentation/paymentmethods/securepayment) page.
Review the [Response Codes](/api-reference/en/error-and-reponse/responsecodes) page for information on decline codes. Contact support if the issue is unresolved.
This error indicates incorrect API credentials. Verify the `Authorization` header in your request and ensure your API key is correctly formatted.
Ensure you’re using the correct plugin version for your e-commerce platform. Follow the instructions in the relevant [Installation Guide](/support/plugins-woocommerce).
Make sure the webhook URL is publicly accessible and registered correctly in the API payload. Refer to [Webhook Handler Setup](/api-reference/en/webhook-handler) for configuration steps.
***
## **Need More Help?**
If you need further assistance, please [reach out to our support team](/support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.
# Magento 2
Source: https://docs.paymentoptions.com/support/plugins-magento
Integration Guide for Magento 2
![Magento 2]()
* **Description**: Seamlessly connect the Gateway with Magento 2.
## **Install Extension**
Download the latest Source code zip file from the Payment Options GitHub
( Use the download Link : [https://github.com/paymentoptions/magento2-extension](https://github.com/paymentoptions/magento2-extension) ).
Extract the magento2-extension.zip.
Place the extracted files into `app/code/Agtech/Paymentoptions/` folder under Magento root path
Check your Magento Mode:
Run `php bin/magento deploy:mode:show` to find your mode
If your Magento mode is "production", please run the below commands:
* `php bin/magento cache:clean`
* `php bin/magento cache:flush`
* `php bin/magento setup:upgrade`
* `php bin/magento setup:di:compile`
* `php bin/magento setup:static-content:deploy`
If your Magento mode is "default" (or) "developer", please run the below commands:
* `php bin/magento setup:upgrade`
* `php bin/magento setup:di:compile`
* `php bin/magento setup:static-content:deploy -f`
## **Configure Extension**
Log in to your Magento Store Backend
Choose Stores on the Admin sidebar to the left. Now go to Settings > Configuration.
In the Configuration page, click on Sales on the left and choose Payment Methods
On the Payment Methods page, navigate to “Payment Options” Payment Section.
* Enabled - select yes to enable the “Payment Options” Payment Method
* Mode - select sandbox or live mode
* Title - This title will show under the payment methods section on the checkout page of Magento
* Access Token - Enter Your `Secret Key` received from Payment Options.
* Merchant ID - Enter Your `Merchant ID` received from Payment Options.
* Debug - select yes to enable the debug, this will log Payment Options API calls under var/log/debug.log file
* Countries - Allow all countries or select specific countries to access this payment method
Click Save Config.
Refresh Magento Cache.
![Refresh image]()
## **Front View**
It will show on the checkout page under the payment Methods section
Select “Payment Options” payment option: It will show like below:
![Front View]()
Click on “Place Order” Button: It will redirect you on payment page
![Front View]()
Make payment using any of the options provided above.
After making a successful payment, it will redirect to the success page.
![Front View]()
### Admin View
![Admin View image]()
If you need further assistance, please [reach out to our support team](./support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.
# OpenCart
Source: https://docs.paymentoptions.com/support/plugins-opencart
Installation Guide for Opencart 3.0.x.x – 3.1.x.x
![Opencart]()
* **Description**: Enable Gateway payments for OpenCart.
## **Mandatory requirements to be in the machine while installation**
* PHP version 5.6+
* cURL
* OpenSSL
* Opencart 3.0.x.x or 3.1.x.x
* Installation can be done only through the cPanel/FTP/Admin Panel. This module may not support one-page checkout template
## **SME Dasgateway payment module installation**
Module Installation can be done through
* FTP Server/cPanel OR
* Admin Panel
## **Module installation through FTP Server/cPanel**
Install Opencart 3.0.x.x or above on your server
Download the latest Source code zip file from the Payment Options GitHub
( Use the download Link : [https://github.com/paymentoptions/opencart-extension](https://github.com/paymentoptions/opencart-extension) )
Unzip “dasgatewayqr\_oc\_payment\_module\_3-0-x.ocmod.zip”
Upload the ‘admin’ and ‘catalogue’ folders into your Opencart route directory through the FTP client
## **Module Installation through Admin Panel**
Login to the admin panel with credentials
Download the latest binary zip file from the Payment Options GitHub
( Use the download Link : [https://github.com/paymentoptions/opencart-extension/releases](https://github.com/paymentoptions/opencart-extension/releases) )
Unzip “dasgatewayqr\_oc\_payment\_module\_3-0-x.ocmod.zip”
![unzip image]()
Go to your Opencart store admin using username and password, click on the extension option under the Extension menu and select the Payments option from the dropdown list at the top of the screen
![extention image]()
Under the Payment List, you will find the “SME Dasgateway” Payment option
Install the “SME Dasgateway” Payment module by clicking the “+” option
![extention image]()
From the list select the SME category
![extention image]()
After completing the installation, click the edit button to open the “SME Dasgateway” configuration page
Access Token - Enter Your `Secret API Key` received from Payment Options
Merchant ID - Enter Your `Merchant ID` received from Payment Options
Toggle Live or Test to select the processing environment
Set sort order and enable the module to enable the payment option on the Payment Page
![extention image]()
If you need further assistance, please [reach out to our support team](./support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.
# WooCommerce
Source: https://docs.paymentoptions.com/support/plugins-woocommerce
Installation Guide for WooCommerce
![WooCommerce]()
* **Description**: Accept secure payments in your WooCommerce store.
## **Steps for Manual Installation**
First, you need to [download the plugin from the source](https://github.com/Kavi-PO/woocommerce-plugin.git) (which will be a zip file).
Next, you need to go to the WordPress admin area and visit Plugins
» Add New page.
After that, click on the 'Upload Plugin' button on top of the page.
This will reveal the plugin upload form. Here you need to click on the 'Choose File' button and select the plugin file you downloaded earlier to your computer.
After you have selected the file, you need to click on the 'Install Now' button.
WordPress will now upload the plugin file from your computer and install it for you. You will see a success message like this after the installation is finished.
Once installed, you need to click on the Activate Plugin link to start using the plugin.
After activation, you need to enable plugin & configure payment options like Merchant ID, API key provided by payment options.
After configured, click the 'Save' button.
## **Screenshots**
### Backend
![Backend image]()
![Backend image]()
![Backend image]()
### Frontend
![Frontend image]()
If you need further assistance, please [reach out to our support team](./support/contact). Our team is here to help you troubleshoot and resolve any issues you may be experiencing.