Pro Direct Payment allows your customers to make payments directly without adding products to the cart or completing the standard checkout process. All payments are recorded as regular orders, visible to both the store admin and the customer. Fully compatible with PayTR and all other OpenCart payment gateways.

Pro Direct Payment is a powerful direct payment module designed for OpenCart.
Your customers can make a payment simply by filling in fields such as name, email, phone, and description—without selecting any product or going through cart steps.

Once the payment is completed, the transaction is stored as a normal order within the OpenCart order system. This ensures full visibility in both the admin panel and the customer’s order history.

Click here for Live Demo

Admin: demo
Parola: demo

Click for Interface Demo

The module is fully compatible with PayTR and other payment gateways, including those requiring server-to-server confirmation. The order status updates automatically after payment confirmation.
It also includes a comprehensive reporting panel that allows filtering, viewing, and managing all direct payments.

1. Direct Payment Without Cart
Customers can pay instantly without adding any product to the cart.

2. Virtual Payment Product System
A predefined “Payment Product” is selected from module settings.
This product is used to generate orders for all direct payments.

3. Advanced Form Field Management
Each field can be configured as:
Hidden
Visible
Required
Supported fields:
Name (always required)
Email
Phone
Description (Invoice / Reference Number)
Company Name
Tax ID
Tax Office
All labels support multi-language (TR / EN / RTL).

4. Optional Login Requirement
You may require customers to log in before viewing the payment form.
If not logged in → redirected to login page → automatically returned to the form after login.

5. Works With All OpenCart Payment Gateways
Compatible with:
PayTR, iyzico, Stripe, PayPal, PayU, Klarna, all bank POS systems and any gateway that uses OpenCart’s standard payment structure.

6. PayTR Auto-Approval Support
Fully supports PayTR server callbacks.
Order status updates automatically after payment confirmation.

7. Full Order System Integration
All direct payments are stored as regular orders:
Shown in admin order list
Trigger email notifications
Managed just like normal orders
Visible in customer order history

8. Advanced Reporting Panel
Includes a dedicated reporting page for all direct payments:
Date range filters
Customer name / email filter
Amount filter
Delete option
Export-ready data structure

9. Google reCAPTCHA v2 / v3
Ensures security against spam and bots.

10. Multi-language & RTL Support
Fully compatible with RTL languages (Arabic, Hebrew, Persian).
All text and labels come from language files.

11. Clean OCMOD Structure
No core files are modified.

How It Works
Select a “Direct Payment Product” from module settings.
Configure form fields (on/off/required).
Customer fills out the payment form.
Pressing “Pay Now” sends the user directly to the selected payment gateway.
After successful payment, a standard order is created.
Admin and customer can view it like any regular order.
All direct payments appear in the reporting panel.


Testing & Compatibility
Works seamlessly with all default themes
Fully compatible with Journal3
Tested with multiple payment gateways
No core modification required

Included in the Package
OCMOD installation file
Admin + catalog module files
English, Turkish, RTL language files
Installation guide
Support instructions

USAGE SCENARIOS (Detailed English Version)
1. Scenario – Creating a Dedicated Product for Direct Payment (Most Common Use Case)

Admin creates a product that is used only for direct payment.

How It Works

A new product is created (e.g., “Direct Payment Product”).

Product price does NOT matter (form amount overrides it).

Product can be hidden from the catalog if desired.

This product is selected in the module settings.

When to Use

When you want payments to be fully independent from store products
For service fees, consulting, deposits, project payments
When the product should not appear in categories

2. Scenario – Using a Regular Store Product for Direct Payment

A normal product currently being sold can also be used for direct payments.

How It Works

Admin selects an existing product in the module

IMPORTANT: "Hide from catalog" must NOT be enabled

Product stays visible and buyable normally

When using the direct payment form:

The amount entered replaces the product price

A normal order is created

When to Use

When you want the same product used for both selling and direct payment
When you prefer payment gateways to see a standard product sale
When you don’t want to create extra products

3. Scenario – Hiding the Product (Only for Direct Payment Use)

Admin hides the product so customers cannot see it in the store.

How It Works

Only the module uses the product

It never appears in categories

Works only as a technical product behind the scenes

When to Use

For internal or private fee collection
When product listing should stay clean

4. Scenario – Allowing Guest Payments (No Login Required)

Customers can make payments without creating an account.

How It Works

Customer fills the form

Clicks “Pay”

Order is created based on email

No customer account required

When to Use

Fees, invoices, deposits, donations
Fast and simple payment without registration

5. Scenario – Require Login Before Payment

If guest checkout is disabled, only members can pay.

How It Works

Users must log in

Orders appear in their account history

When to Use

Dealer-only systems
B2B payments
Customer-specific fee collection

6. Scenario – Using Google reCAPTCHA for Protection

Helps prevent spam submissions.

7. Scenario – Reporting & Record Deletion

Admin can view and delete all payment records.

When to Use

Monthly accounting
Manual reconciliation
Cleaning old or test records