PayMe

PayMe: Payment Acceptance And Commerce Tools For Merchants

PayMe is a payments platform that supports multiple ways for merchants to accept and manage customer payments, including checkout pages, payment requests (links), subscriptions, refunds, and dispute handling. It also provides developer-facing APIs and integration options, plus an in-dashboard marketplace for enabling additional capabilities. PayMe states that tens of thousands of businesses use its interface and that it processes billions in volume for 80,000+ businesses.

PayMe Overview

PayMe is designed for merchants that want a single operational surface to run common payment workflows: charging customers, issuing refunds, managing recurring payments, and monitoring payouts and balances. Beyond day-to-day payment operations, PayMe also supports integration-driven use cases through its APIs, including tokenization and embedded payment collection.

PayMe positions its onboarding as a streamlined process and indicates that merchants can start receiving payments within minutes, using methods such as credit cards, Bit, and PayPal (and it references Apple Pay in its documentation and flows).

Payment Acceptance Channels

Merchants can collect payments through several channels, including:

• Online (Web): Checkout via payment pages and shareable payment links.

• In-App (mCommerce): API-driven payment flows and hosted fields for embedded experiences.

• Payment Requests: Requests by SMS or email, and shareable payment links that can be distributed through channels like email or social platforms.

• MOTO / Virtual Terminal Style Workflows: Manual payment flows for charging customers directly through the dashboard.

• POS Payments: API references and guides that cover point-of-sale scenarios and POS device ordering.

This coverage is relevant for merchants that sell through a website, use social selling with payment links, collect payments through invoices or requests, or need a mix of online and in-person acceptance.

Payment Methods And Supported Schemes

PayMe’s payment method coverage spans cards, wallets, and additional rails. In practice, what is available can depend on account configuration and approvals, including risk and KYC-related review.

Examples of supported categories and methods include:

• Cards: Support for common card brands, with pricing references that explicitly mention Visa and Mastercard and include premiums for some premium brands (for example, Amex and Diners).

• Digital Wallets And Alternative Payment Methods: PayPal and Bit are explicitly supported as alternative payment methods. Apple Pay and Google Pay are referenced in pricing and in developer documentation.

• Alipay: Developer references include Alipay flows such as QR-based and online variants.

• Bank Transfer / Funds Transfer: Developer references include bank transfer style payment methods.

• Multi-Currency: PayMe indicates accounts default to ILS and can be configured for USD and EUR, and it references “tourist cards” for cards issued outside Israel.

Merchants expanding internationally should treat currency support as a configuration topic, not an assumption, because PayMe indicates that foreign currency availability and approval can be decisioned by risk management.

Checkout, Billing, And Collection Flows

PayMe supports multiple collection patterns that map to common merchant billing needs:

Payment Pages And Hosted Payment Experiences

Merchants can route customers to a payment page that adapts to the selected payment method. For embedded scenarios, PayMe also supports hosted fields via JavaScript integration, intended to provide a secure way to collect sensitive payment data while maintaining control over the storefront UI.

Payment Links, QR, And Requests

PayMe supports creating payment links that can be shared broadly, including scenarios where many customers pay from the same link. It also supports creating single-sale requests by SMS or email. For some payment methods, PayMe references QR-based presentation as part of the customer payment experience.

Subscriptions And Recurring Payments

PayMe supports recurring billing, including subscription management through the dashboard and recurring payments through APIs. For merchants with memberships, retainers, or installment-like service plans, this is a core operational capability, alongside notifications and lifecycle actions such as cancellation and payment method updates under certain conditions.

Authorizations And Delayed Capture

PayMe supports authorization flows where an amount is reserved on a buyer’s card for a limited period, followed by capture to trigger settlement. This can be relevant for preorders, deposits, or workflows that require confirmation before finalizing a charge.

Settlement And Payout Operations

PayMe provides dashboard visibility into balances and payout timing, and it offers multiple payout plan approaches:

• Monthly automatic withdrawal: Transfers occur on a specified day for prior-period activity, with distinct timing referenced for foreign cards and foreign currency.

• Daily transfer: Payouts are made daily and contain payments processed a fixed number of calendar days prior.

• Manual transfer: Merchants can enable manual withdrawals, with funds becoming available based on defined timing rules, and bank transfer timing can depend on bank settlement processes.

These payout rules matter operationally for cash-flow planning, especially for merchants with cross-border volume, higher-risk categories, or tight liquidity requirements.

Risk Management, Disputes, And Security Controls

Chargebacks And Disputes

PayMe provides operational guidance for chargeback handling, including merchant response steps and timelines. It also references the use of payer authentication as a tool to reduce disputes. Chargeback-related fees are explicitly listed in PayMe’s pricing table for both domestic and foreign cards.

3D Secure

PayMe offers 3D Secure as a payer authentication approach intended to reduce certain dispute outcomes. Pricing for the 3D Secure service is referenced as a percentage fee with a minimum charge.

Account Verification And KYC

PayMe’s verification process includes submission of documents such as identification and bank account proof, and it distinguishes between the ability to process transactions and the ability to withdraw funds to a bank account prior to verification completion. PayMe also references a KYC department contact for enabling certain capabilities like foreign currency clearing.

PCI-Related Security Positioning

PayMe states that its payment page is secured with PCI Level 1 compliance, and it links to PCI Security Standards resources in its support materials. For merchants, this matters most when deciding between redirect, hosted fields, and other integration modes, and when designing internal controls around PCI scope.

Reporting And Operational Administration

For reporting, PayMe provides dashboard-based export functionality for transaction reporting, including exporting transactions to an Excel spreadsheet for a selected date range. It also provides monthly invoice delivery and supporting documentation outputs such as balance authorization reporting, which can be useful for reconciliation and accounting routines.

Developer Experience And Integrations

PayMe provides a developer documentation portal that covers guides and API references for payments and related workflows. Integration approaches include:

• Hosted payment pages and hosted fields (JS-based embedding).

• API-driven payment generation, including token-based flows and 3D Secure flows.

• Marketplace and platform scenarios: PayMe’s documentation includes seller onboarding guidance, including API and white-labeled UI approaches.

For ecommerce enablement, PayMe also references plugins and integration instructions for platforms such as Shopify and WooCommerce in its help materials.

Pricing And Fees

PayMe publishes a pricing table in its Terms & Conditions, with fee items including:

• Monthly fixed cost and setup cost.

• Processing fees expressed as percentages for cards issued in Israel and cards issued abroad.

• Fixed per-transaction fees (separately for ILS and foreign currency).

• Premium card surcharges and additional method-related fees (for example, Bit).

• Chargeback fees (distinct for domestic and foreign cards).

• Refund transaction fees and fees for optional services (for example, SMS, automatic invoicing, 3D Secure).

• Wallet and alternative method fees (for example, PayPal setup and per-transaction costs, Apple/Google Pay per-transaction cost).

• Several items are described as “according to agreement”, implying merchant-specific or program-specific pricing for certain services like platform fees and accelerated settlement-related options.

Merchants should map these line items to their expected mix of domestic versus foreign cards, currency needs, refund rates, and optional services, because the effective blended cost will depend on real transaction composition.

Conclusion

PayMe combines merchant-facing payment operations (charging, refunds, subscriptions, payment links) with configurable payment methods (including cards and alternative methods) and developer tooling for embedded and API-driven integrations. Its documentation and help materials emphasize multi-channel collection, configurable payout plans, and operational controls for disputes and verification. For merchants evaluating PayMe, the practical fit typically depends on acceptance channels (online, link-based, POS), method mix (cards, wallets, local methods), currency needs (ILS versus USD/EUR), and the payout and risk configuration required for the business model.