Payments

API reference for accepting payments with PayMe — sales via hosted payment page, hosted fields or direct API, tokens, subscriptions, refunds and captures, 3D Secure, invoices and point-of-sale. Start with Getting Started for credentials, environments and a first sale.

API reference

Getting Started

• Start Here: Reading order for developers and AI coding agents integrating the PayMe Payments API: 1) PayMe at a glance, 2) Authentication (seller_payme_id/MPL, payme_client_key, public key), 3) Environments (sandbox.payme.io vs live.payme.io), 4) Quickstart (generate-sale, pay, callback, refund-sale), 5) Callbacks (form-encoded POST, notify_type, payme_signature). Then Errors and Idempotency & Retries.
• PayMe at a Glance: PayMe is a payments provider whose Payments API lets platforms and merchants accept payments through a hosted payment page, hosted fields (JSAPI) or a direct API, with tokenization, subscriptions, refunds, authorization and capture, 3D Secure, invoices and point-of-sale. Other APIs: B2B Payments, Keep (accounting) and Products & Customers. Payment methods include cards, Bit, Apple Pay, Google Pay, PayPal, bank transfer, SEPA, BACS and Israeli direct debit. Sandbox: sandbox.payme.io/api; production: live.payme.io/api.
• Authentication: Payments API requests carry credentials in the JSON body, not an Authorization header. seller_payme_id (the MPL) identifies and authenticates the seller on its own, so keep it server-side. payme_client_key is the partner (platform) key held only by partners; merchants can call refund-sale without it. The per-seller public key (PayMe-Public-Key) is for browser code. Sandbox and production keys are separate. Keep uses OAuth2 client credentials; Products & Customers uses a JWT from POST /auth/token.
• Environments: PayMe has two environments: Sandbox at https://sandbox.payme.io/api/ and Production at https://live.payme.io/api/; each issues its own keys. The B2B Payments API uses the same hosts and /api prefix. sale_url is the environment's base URL plus /sale/generate/<id>; use it exactly as returned. Test only in the sandbox with the documented test cards; decline cards return HTTP 200 with status_code 1 and codes such as 20004 or 21001-21008. Browser scripts load from cdn.paymeservice.com; Hosted Fields uses testMode: true.
• Quickstart: End-to-end sandbox walkthrough. 1) POST https://sandbox.payme.io/api/generate-sale with seller_payme_id, sale_price (minor units, min 500), currency, product_name, transaction_id, sale_callback_url, sale_return_url, language en; response has sale_url and payme_sale_id. 2) Open sale_url and pay with test card 5326105300985846 12/30 CVV 658. 3) PayMe POSTs a form-encoded callback with notify_type sale-complete; reply 200 within 5 s. 4) POST /refund-sale with seller_payme_id, payme_sale_id and optional sale_refund_amount.
• Callbacks: PayMe callbacks are form-encoded POSTs to sale_callback_url (or the default callback URL). Any HTTP status below 400 counts as delivered; each attempt times out after 5 s; up to 3 attempts over about 2 minutes, then dropped. Duplicates happen and ordering is not guaranteed: de-duplicate on notify_type + payme_sale_id + payme_transaction_id. payme_signature = lowercase hex MD5 of payme_client_key + client password + payme_transaction_id + payme_sale_id. Before fulfilling an order, confirm the sale's status and amount with POST /get-sales.
• Errors: Payments API errors return status_code 1 with status_error_code, status_error_details (Hebrew unless language is en; he, en, es, ru, ar accepted) and status_additional_info (often the field name). Branch on status_code and status_error_code, never on HTTP status: card declines return HTTP 200, many request errors HTTP 500, some 400/403/422/429/503. Common codes: 1 missing parameter, 200 unknown client key, 251 seller not found, 252 currency not allowed, 305 wrong sale status, 352 invalid price, 998 too many or duplicate requests, 20xxx/21xxx card declines.
• Idempotency and Retries: PayMe has no idempotency key and does not de-duplicate transaction_id: two generate-sale calls create two sales. A second pay-sale, refund-sale or capture-sale for the same sale while the first is running gets HTTP 429 code 998; once it finished, a retry runs again (a repeated partial refund is a second refund; a paid sale paid again gets 305). After a timeout, check sale_status via POST /get-sales (filter by sale_payme_id or transaction_id) before retrying. generate-sale, pay-sale and capture-sale share a per-seller rate limit, 100 requests per 10 s by default.

Introduction

• Payments overview: Our API is designed to allow platforms to offer a full payment solution as part of their product.
• Sandbox and Production URLs: In order to work with the API, you should use the service URLs according to the required environments, Sandbox or Production.When interacting with the API, make sure you point to the correct environment, with the correct credentials. Both URLs will be stated next to each function.
• Test Cards and Payment Methods: Please use the following credit card when integrating only in the Sandbox environment.
• Value Added Services: At PayMe, We go beyond traditional financial solutions to offer a comprehensive suite of value-added services. These services are designed to enhance our clients' financial experiences and empower them with the tools they need for success. From the creation of invoices and security services to seamless integration with third-party platforms, our value-added services cater to the diverse needs of your business.
• Payment Options: We have three integration options: - Hosted Payment Page - Hosted Fields - JSAPI - Direct API

Hosted Payment Page

• Generate Payment: POST /generate-sale
• Generate Multi Checkout Payment: How to call POST /generate-sale for Hosted Payment Page.

Hosted Fields - JSAPI

• Generate Payment with Token: How to call POST /generate-sale for Hosted Fields - JSAPI.

Direct API

• Available Payment Methods: As PayMe offers different payment methods, you can use the sale_payment_method parameter in generate-sale to set your desired payment method.
• Pay Sale: POST /pay-sale

Point of Sale (POS)

• Order New POS Device: POST /vas-enable
• Pair New Device: POST /vas/pos/pair
• Authenticate New Device: POST /vas/pos/authenticate
• New POS Payment: POST /sales
• Refund POS Sale: PUT /sales

Post Sale Actions

• Refund Sale: POST /refund-sale
• Void Sale: How to call POST /refund-sale for Post Sale Actions.
• Capture Sale: POST /capture-sale
• Cancel Multi Payment Page: POST /cancel-template

Apple Pay

• Activate Service (Apple Pay): How to call POST /vas-enable for Apple Pay.
• Generate Sale with Apple Pay: How to call POST /generate-sale for Apple Pay.

Google Pay

• Activate Service (Google Pay): How to call POST /vas-enable for Google Pay.
• Generate Sale with Google Pay: How to call POST /generate-sale for Google Pay.

IL Direct Debit

• Generate New Authorization: How to call POST /generate-sale for IL Direct Debit.
• Generate New Payment: How to call POST /generate-sale for IL Direct Debit.

Subscriptions

• Generate: POST /generate-subscription
• Recurring Payments: Recurring payments help you to oversee regular payments for subscriptions, providing convenience to customers and predictable revenue streams for your business.
• Pay: POST /pay-subscription
• Cancel: POST /cancel-subscription
• Pause: POST /pause-subscription
• Resume: PATCH /subscriptions/{sub_payme_id}/resume
• Update Price: PATCH /subscriptions/{sub_id}/set-price

Tokenization

• Capture Buyer Token: POST /capture-buyer-token
• Generate Sale with Token: How to call POST /generate-sale for Tokenization.
• Get Buyer Key: POST /get-buyer-key
• Get card details by token: POST /buyer-token-to-card-number

Merchants Management

• Create Seller: POST /create-seller
• Update Seller: POST /update-seller
• Upload Seller Files: POST /upload-seller-files
• Retrieve Seller's Additional Services Data: POST /get-vas-seller
• Withdraw Balance: POST /withdraw-balance
• Get Seller Public Key: GET /sellers/{seller_payme_id}/public-keys
• Delayed Market Fee: PATCH /sales/{guid}/external-market-fee
• Create Individual: POST /sellers/{mpl_key}/individuals
• Update Individual: POST /sellers/{mpl_key}/individuals/{individual_key}
• Get-Individuals by Company ID: GET /sellers/{mpl_key}/individuals
• Get Partner Data: GET /partners
• GET Mids: GET /sellers/{mpl_key}/mids
• Business Fields: GET /business-fields

Buyers Management

• Get Customer Details: GET /buyers/{buyer_guid}

Generate a Sale with 3D Secure

• Generate Sale with 3D Secure: How to call POST /generate-sale for Generate a Sale with 3D Secure.

Standalone 3D Secure service

• Initialize 3DSecure Request: POST /sales/payme_sale_id/3ds
• Resolve Secured Hash: GET /sales/payme_sale_id/3ds/hash

Invoices

• Create Document: POST /documents
• Get Generated Document By ID: GET /documents/document_id
• Show Generated Document By ID: GET /show-documents/document_id
• Query Existing Documents: GET /documents

Query APIs

• List Sales: POST /get-sales
• Reporting & Data: Access preconfigured reports to gain insight into essential activities, such as sales, transactions, subscriptions, and balance adjustments.
• List Transactions: POST /get-transactions
• List Subscriptions: POST /get-subscriptions
• List Sellers: POST /get-sellers
• List Past Withdrawals: POST /get-withdrawals
• List Future Withdrawals: POST /get-future-withdrawals
• Aggregated Wallets Data: GET /funds-transfer/aggregated
• List of available banks: GET /banks/{country_iso_code}
• Wallet to Wallet transfers: GET /funds-transfer
• Withdrawal Correlation: POST /credit-match

Get Transaction Statistics

• Get Transaction Statistics: POST /get-transaction-statistics

Get Transaction Data

• Get Transaction Data: POST /get-transaction-data

iOS SDK

• iOS SDK: You can use the PayMe (Isracard Global) iOS SDK to implement payments on iOS devices. The guide covers building and importing the PMLib.framework, initializing the SDK, and integrating the Isracard Global API to pay a sale, pay a subscription, and capture a buyer.