Marketplaces & Platforms
How-to guides for platforms and marketplaces on PayMe: onboarding sellers, Apple Pay, Google Pay, bank transfer, Israeli direct debit, capture, 3D Secure and reporting, plus reference lists of statuses, types and codes.
- Merchant Default URLs: Upon creating your Merchant account with us, you will be required to provide a few default URLs for various calls. More examples can be found further in the documentation.
- Apple Pay: The payment method is limited to be used in the following devices manufactured by Apple:
- Apple Pay - Full Flow Control: The payment method is limited to be used in the following devices manufactured by Apple:
- Google Pay: Google Pay™ allows your customers to pay quickly and securely using payment methods saved in their Google Account.
Google Pay is fully compatible with PayMe’s products and features: You can use it for traditional payments and multi payments page.
- Bank transfer: How to take a bank-transfer payment: create a pending bank transfer, wait for the callback, and treat
PAID as funds received.
- Israeli Direct Debit: In order to create a direct debit mandate for Israeli customers, you can use our generate-sale API endpoint to complete the two actions of: 1. Generating a mandate request. 2. Generating a new payment request.
- Point Of Sale: A POS system allows your business to accept payments from customers and keep track of sales. It sounds simple enough, but the setup can work in different ways, depending on whether you sell online, have a physical storefront, or both.
- Multi Payment Page: Also known as “Template Sale”. Enables payments on a single sale link, by multiple buyers.
For example, you will be able to generate a single sale
and share its payment link on any social network site to allow multiple customers to pay on their own.
Every payment will create a new sale with
a different ID. Creation of a template sale should be done by adding the sale_type="template" attribute to the request:
- Multi Capture: The guide will be a run-through the process of using our Multi-Capture logic for card payments.
- Multi Capture Paypal: The guide will be a run-through the process of using our Multi-Capture logic for Paypal payments.
- Capture sale: Also known as “Pre-Authorization”. The requested amount gets reserved (blocked) on the credit card of the buyer for up to 168 hours. A following Capture request will trigger the actual settlement of the funds. Please note that attempting to Capture after the allowed period of time (168 hours) will result in an error.
- Create Payment With Buyer Key (Token): Allows for token capture upon the buyer's payment (submission of payment details).
- How to create subscription: Diagram of the steps to create a recurring subscription payment with PayMe.
- 3D Secure Guide: 3-D Secure is a protocol designated to redurce fradulant transactions and protect merchants from losing the funds for those transactions. The name refers to the "three domains" which interact using the protocol: the merchant/acquirer domain, the issuer domain, and the interoperability domain. Our API is designed to allow platforms to offer a full payment solution as part of their product.Using the API you can allow sellers accept 3DSecure authorizations for credit card payments.
- 3D Secure as a Service: The standalone 3D Secure service enables you to leverage the 3D Secure capabilities of PayMe in an independent API request, without executing the usual purchase or authorization transaction that triggers 3D Secure authentication.
- Create Seller: This endpoint is relevant only to PayMe's partners.
- Kinds of reports: Using our API and system, you can export different kinds of reports.
- Queries APIs guides: > For API reference, please head over to our APIs section using the sidebar on the left.
- Sale Types: Reference list of PayMe sale types and their numbers, such as sale (J4), authorize (J5), token and template.
- Sale Statuses: Reference list of sale statuses, from
initial and completed to refunded, chargeback and voided, with what each means.
- Sale Callbacks: The callback PayMe sends to your server when a sale is paid, authorized, refunded, fails or is charged back: notification types and every payload field.
- Transaction Types: Reference list of transaction type numbers, such as Sale, Token, Authorization/Void and Balance.
- Transaction Statuses: Reference list of transaction statuses, from
pending and validated to refunds, chargebacks and voids.
- Subscription Statuses: Reference list of subscription statuses — initial, active, paused, failed, cancelled, completed, and failed pending automatic retry.
- Subscription Iteration Types: Reference list of subscription billing intervals: daily, weekly, monthly and annually.
- Bank Authorization Statuses: Reference list of Israeli direct-debit bank authorization statuses sent in callbacks, such as opened, failed, cancelled by the account owner and reactivated.
- Banks in Israel: Reference list of Israeli bank names and their bank codes, used when entering seller or buyer bank details.
- File Types: Reference list of document file-type codes for uploading seller files, such as ID, bank account ownership and incorporation certificate.
- Document Types: Reference list of document type codes you can generate, such as order, invoice, invoice receipt, refund and receipt.
- MCC List: Reference list of PayMe merchant category codes (MCC) with Hebrew and English descriptions of each business type.
- Individual Seller Types: Reference list of role codes for individuals linked to a seller: owner, signatory, director, executive and back office.
- Seller Incorporation Types (IL): Reference list of Israeli business incorporation type codes, such as sole proprietorship, company, partnership and non-profit.
- VAS Types: Reference list of value-added service (VAS) type codes, such as invoices, SMS, antifraud, marketplace and POS.