Paymentz

Paymentz: Merchant Overview, Pricing, APIs, And Supported Payment Flows

Paymentz is a payment platform designed to help merchants accept and manage payments using hosted checkout and API-driven integrations. It supports online checkout flows for web and mobile apps, provides REST APIs for transaction processing, and includes additional workflows such as invoices (payment links), QR-based payments, and marketplace-style split workflows. It also includes merchant and partner back-office interfaces for monitoring activity, reviewing charges, and managing transaction operations.

What Paymentz Provides For Merchants

Paymentz offers multiple integration surfaces that cover different merchant operating models:

• Hosted checkout for web and mobile (a redirect to a hosted payment page, then return to the merchant).

• REST API integration for purchases, recurring payments, refunds, and payouts.

• Invoice generation that can send a payment link to customers.

• QR checkout workflows (including a dynamic QR response flow).

• Back-office operations for actions such as capture, refund, cancellation, and inquiry.

• Merchant and partner dashboards with transaction charts and reports.

Payment Acceptance Channels And Checkout Options

Hosted Checkout For Web

Paymentz supports a standard hosted checkout workflow where the merchant posts an initial request to a hosted checkout endpoint, the customer enters payment details on the hosted page, and the customer is redirected back to the merchant’s redirect URL with the payment outcome. The workflow relies on merchant-provided parameters such as transaction identifiers and redirect URLs.

Hosted Checkout For Mobile Apps

Paymentz provides mobile integration guides and SDK-oriented flows for:

• Android

• iOS

• React Native wrapper around Android and iOS SDKs

• Flutter plugin-based integration

The mobile pattern mirrors the web flow: the app initiates the request, the customer completes payment on the hosted checkout page, and the app receives the result.

REST API Integration (Server-To-Server)

Paymentz’s REST integration is documented as supporting purchase transactions as well as operational flows such as refunds and payouts. The REST model uses:

• POST-based API calls

• Auth tokens in request headers

• Callback/notification URLs for asynchronous flows where applicable

• Checksum-based request validation (MD5 hashing in the documented workflows)

• TLS requirements for securing transport

This model is typically used when merchants want tighter control over payment orchestration and post-payment operations, while still using Paymentz for payment processing and status tracking.

Virtual Checkout (Merchant-Initiated Payments)

Paymentz documentation includes “Virtual Checkout” as a back-office feature and describes it as being used by merchants to place transactions on behalf of the cardholder. This is operationally similar to a merchant-initiated entry flow (commonly associated with virtual terminal use cases), with URL-based access managed through the partner back-office interface and referenced in user-guide materials.

Invoices And Payment Links

Paymentz includes an invoice capability where merchants can generate an invoice via API. The REST overview describes invoicing as generating an invoice for customers and informing them through email, where customers can pay using a payment link included in the email. This supports common “pay-by-link” and remote billing scenarios.

QR Checkout

Paymentz documents QR-based payment workflows, including a Dynamic QR Checkout API where payment data is sent to the server and the merchant receives dynamic QR details in response. The QR workflow documentation also describes static and dynamic QR payment types and follow-up steps (verification and confirmation/status flows).

Payment Methods And Schemes

Card Payments

The REST overview references support for card payments and lists common schemes including:

• Visa

• Mastercard

• Maestro

• American Express (AMEX)

• JCB

• CUP (China UnionPay)

Bank-Account Based Payments

The REST API specifications include a bank account object intended for bank-account based payments (the documentation explicitly references examples such as bank transfers or direct debits). The parameters include, among others:

• IBAN and BIC/SWIFT fields (commonly associated with bank-transfer rails in many geographies)

• Routing number and account type fields (commonly associated with bank-account payments in the US context)

Alternative Methods And Wallet/Netbanking Parameters

The “Bank Specific Parameters” section lists a set of method names for which additional parameters may be required, including examples such as Skrill, Neteller, PaySafeCard, Trustly, and others. Separately, the REST API specifications include parameters such as:

• A paymentProvider field (described for a bank list used for netbanking/wallets)

• A vpa_address field described as a virtual payment address for UPI

UPI Enablement

Paymentz documentation for wallet APIs states that the platform provides APIs for enabling UPI payments, and the REST API specifications include UPI-related parameterization (virtual payment address).

Recurring Billing, Stored Credentials, And 3D Secure

Tokenization And Stored Payment Data

Paymentz documents tokenization as a mechanism to store payment data and reuse it later, including for recurring transactions. The tokenization workflow describes:

• Creating a token during a payment or as a standalone operation

• Using stored payment data via an endpoint intended for “pay with token” behavior

• Deleting stored payment data when needed

Recurring Payments

Paymentz recurring documentation describes the use of a recurringType parameter to mark initial and subsequent payments:

• INITIAL for the initial recurring payment

• REPEATED for subsequent recurring payments

The recurring guide describes different repeat workflows, including repeating with a registrationId or with a paymentId, depending on the scenario.

3D Secure Support

Paymentz REST API specifications include 3D Secure data structures and fields for both:

• 3D Secure (general)

• 3D Secure Version 2 (including device/browser detail fields for 3DS v2 scenarios)

The API specifications also document an attemptThreeD concept for 3D-secure merchant accounts, with modes described as Direct, 3D, and Only3D.

Merchant Portal, Reporting, And Operational Controls

Merchant Dashboard And Reporting Views

Paymentz describes a merchant dashboard that provides a graphical overview of transactions for the last six months and includes charts such as:

• Sales chart

• Sales per currency chart

• Status chart

• Progress status

Back-Office Transaction Operations Via API

Paymentz describes operational actions available through REST API back-office operations, including:

• Capturing an authorization

• Refunding a payment

• Reversing/canceling a payment

• Inquiring about a payment

This is relevant for merchants who need programmatic post-authorization controls and lifecycle management.

Partner Back Office And Marketplace Operations

Paymentz includes partner-oriented documentation describing merchant management features (including sales/refund/chargeback reporting) and marketplace onboarding flows where vendors can be registered as sub-merchants. The marketplace flow includes partner credentials, vendor registration workflows, and master/child tracking identifiers for marketplace transaction logic.

Payouts

Paymentz describes payouts as a transfer of funds from the merchant to the customer and notes payout support as part of REST API capabilities. It also provides a separate payout API documentation area.

Settlement Timing

Paymentz states that payments are settled to the registered bank account after 2 working days (with clarifications about what constitutes working days).

Onboarding And Support Model

Paymentz describes swift onboarding and 24×7 support. Separately, the user guide for partner sign-up and login states that back-office access requires credentials provided via email after successful sign-up, and that sign-up can be initiated by contacting support by email.

Conclusion

Paymentz offers a merchant-facing payment acceptance stack centered on hosted checkout plus REST APIs, with additional modules for invoices (payment links), QR payment workflows, tokenization and recurring payments, and operational controls for refunds, capture, cancellation, and inquiry. It indicates structured back-office reporting for merchants and partners, including transaction dashboards and charge summaries.