- Brand
- Allpay
- Category
- Finance
- Primary Subcategory
- Payment Processing & Gateways
Integration details
Description
View payments and payouts, create payment requests and reusable payment links, and get reports from your Allpay account directly in ChatGPT. Analyze payments by date, currency, customer, payment link, payment method or card origin. Compare periods, identify top customers, and inspect payment details and transaction history. View company information, connected services and fees, billing, payout schedules, past payouts, payment links and existing customer subscriptions. Create an individual payment request for a specific customer or order, with a unique checkout link intended for one payment. Alternatively, create a reusable payment link that multiple customers can use. Both individual requests and reusable links support standard payments, installments and monthly subscription checkout, subject to account permissions. Monthly subscriptions use a single line item and cannot be combined with installments. Deferred subscriptions collect the customer’s card at checkout and charge it when billing starts; an invalid card may only be detected at that first charge. Subscription billing begins only after the customer completes the applicable checkout flow. Choose supported currencies, checkout languages, line items and expiry settings. Test mode is available for demonstrations. Payment requests and reusable links are created within the authenticated merchant's Allpay account. Customers complete checkout on an Allpay-hosted payment page; creating a request or link does not itself charge a card. The integration does not issue refunds, initiate payouts or activate paid Allpay services. Any required Israeli identity or company number is entered by the payer directly on the Allpay-hosted payment page, outside ChatGPT and MCP. These values are stored on Allpay's servers and are never transmitted through MCP, accepted as MCP tool arguments, or included in MCP responses. Do not ask users to provide these numbers in chat. The optional hide_tehudat boolean controls only the visibility of that field on the hosted payment page; it never contains an identity number. Account authorization is required. You can retrieve Allpay API documentation and request deletion of account-level MCP interaction logs after explicit confirmation. Log deletion does not delete payments, business records or copies held by an AI provider. Allpay's Privacy Policy explains Team access, logging, retention and deletion.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Payment Processing & Gateways
- Secondary Subcategories
- None listed
- Brand
- Allpay
- Access
- Account required
- First tracked
- 2026-11-22
- Tool count
- 21
- Market
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Not discoverable in ChatGPT yet
ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Allpay suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.
What discovery looks like

Get alerts for Allpay
Get updates when Allpay’s Discoverability Score or category rank changes.
Competing in ChatGPT Payment Processing & Gateways
View Category21 tools agents can invoke
Get the texts of API documentation sections by their id. Table of contents (id → [title, parent_id?]): {"1452":["Getting Started"],"1453":["Integration Flows"],"1454":["Payments"],"1455":["Chargeback Webhook"],"1456":["Chargeback Webhook"],"1457":["Chargeback Webhook"],"1458":["Chargeback Webhook"],"1459":["Chargeback Webhook"],"1460":["Authentication",1452],"1461":["Signature Algorithm",1452],"1462":["Errors",1452],"1463":["Create Payment",1454],"1464":["Payment Webhook",1454],"1465":["Chargeback Webhook",1454]}. Pass the ids of the sections you need in ids — several at once is fine. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_api_doc
The seller's API integrations (the "Integrations → My sites" section): login/key pairs the seller's website or service uses to create payments via the Allpay API. api_login — login for requests; the secret API key is not provided through this server — it can only be viewed in the app, in the "Integrations → My sites" section; flow: redirect — the customer pays on the Allpay page, hosted_fields — card fields are embedded in the seller's website; test_mode — payments are test by default; webhook — an additional webhook URL configured in the integration settings. Payment notifications are sent to this address in addition to the webhook_url supplied in the payment API request. An empty value means no additional webhook URL is configured; it does not disable notifications to the webhook_url supplied in the request; paid — successful payments per charge currency, last_payment — date of the last one. api_url — API URL, docs — documentation. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_integrations
Get the user's current balance and the date of the next card charge. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_balance
History of Allpay balance movements (the "Tariff → Billing" tab), newest first, in shekels. type: charge — a charge to the card or to the payout balance (receipt_url — link to the PDF receipt), subscription_fee — subscription fee for service for period, one_time_fee — a one-time payment, payment_method_added — a card was added, partner_merchant_activation / partner_merchant_renewal — a charge to the partner for merchant merchant_id, top_up — balance top-up. amount — excluding VAT, amount_with_vat — as the amount is shown in the app. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_billing_history
Data from the "Company" screen: name — company name, email, phone, website, business_type — business type (en / ru / he), vat_payer — VAT payer (false — VAT-exempt), vat_on_foreign_cards — charge VAT on payments with foreign cards, logo_url — logo. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_company
Create a permanent payment link (the "Payment links" section) — one link that many customers can pay through many times: a product/service on a website or social media, donations, a subscription. For a single invoice to one specific customer use create_payment. Amount: items (line items with prices), or amount + name (a single item), or custom_amount = true (the payer enters the amount; amount_options — up to 6 buttons with preset amounts). vat on an item (default true) — subject to VAT; vat_mode — included (the price already includes VAT) or on_top (VAT is added to the price); by default — as on the seller's last link, not applied to VAT-exempt sellers. payment_type: one_time / installments (installments — up to how many payments, 2–12) / subscription (a monthly subscription, one item; requires the "Subscriptions" module; subscription_start: now / after_days / day_of_month (subscription_start_n) / date (subscription_start_date); subscription_end: never / date (subscription_end_date) / after_charges (subscription_end_charges, up to 24)). currency — charge currency (by default as on the last link), valid_till — when the link expires, language — payment page language (auto — browser language), slug — a custom link address. test_mode = true — a test link, real cards are not charged. New item names are also added to the seller's catalog; existing catalog items are not changed. Returns link — the link URL for customers. Before calling, agree the name, amount and payment type with the user. Behavior: This tool creates a new payment link, so it changes state and retrying it creates another link. The action is additive: it adds the link and any new catalog items, and does not delete or overwrite existing links, catalog items or payments. No money moves and nothing is sent to anyone when it runs. The link is a public web page: anyone on the internet who has the URL can open it and pay, so the tool is open-world.
create_paypage
Create an individual payment request for one specific customer or order: an unpaid payment record with its own checkout link on an Allpay-hosted page. For a reusable link that many customers can pay through use create_paypage. Stages. (1) Creating the request is all this tool does: it records the request and returns payment_url. It charges nothing, reserves no funds and sends nothing to the customer; the merchant delivers the link. (2) Checkout: the customer opens the link and completes the Allpay-hosted page before the link expires. Only checkout can charge or save a card. (3) Later subscription charges exist only for a subscription and only after its checkout; Allpay runs them on the subscription schedule, not this tool. Request types. Standard one-time payment (default): one checkout, the request can be paid only once. Installments (installments = N, 2–12): also one checkout and one request; the customer may split the payment into up to N installments on the checkout page. Monthly subscription (subscription = true): the checkout starts a monthly subscription for this customer; one item, no installments, requires the active "Subscriptions" module, in test_mode too. subscription_start: now — the first charge at checkout (default) / date (subscription_start_date) / after_days (subscription_start_n); subscription_end: never (default) / date (subscription_end_date) / after_charges (subscription_end_charges). With a deferred start the customer only saves the card at checkout, no money is charged then, and an invalid card will only be detected at the first charge — tell the user about this. Charges run once a day, Israel time: a start date of today may slip to tomorrow. Repeating order_id. An order_id is unique within one API integration. Without order_id a new one is generated, so every call creates another request. If the order_id was already used in that integration, existing payments are never changed: an unpaid, unexpired request with the same details is returned as it is (existing = true, the same payment_id and payment_url); different details (items or amount, name, customer, currency, language, installments, subscription terms, expiry, test mode) return an error; an expired, paid, refunded or otherwise closed request returns an error too. Use a new order_id to create another request. Integration. The request is created by a request to the Allpay API on behalf of an API integration (the "Integrations → My sites" section): without integration_id — the "MCP" integration, created if it does not exist yet (integration.created_now = true; if the API then rejects the request, the integration stays and the error carries integration_created_now = true). Pass integration_id only if the user asks to run the payment through another integration. Details. Amount: amount + name, or items (line items, prices already include VAT; vat = false — 0% VAT). The customer can be specified in advance (client_name, client_email, client_phone) — otherwise they enter their details on the payment page. The customer always enters their ID number (Teudat Zehut) / company number themselves on the payment page; hide_tehudat = true — do not ask for it (a foreign customer, or the seller does not need it). expire_days — how many days the link is valid (default 7); lang — payment page language; currency — currency (ILS, USD, EUR; if it is not allowed for the account, the amount is converted to ILS). test_mode = true — a test payment (if omitted — as in the integration settings, the result is in the test_mode field; always tell the user about a test payment). Returns payment_url — the checkout link for the customer, payment_id (status — get_payment) and existing. Before calling, agree the amount and purpose of the payment with the user. Behavior: This tool creates an unpaid payment request with a payment URL (and the "MCP" API integration if it does not exist yet), so it changes state. It is not idempotent: without order_id every retry creates another request. It is not destructive: in every branch existing payments stay as they are. A repeated order_id either returns the identical unpaid request unchanged or fails before anything is written; validation errors create nothing. If the Allpay API rejects a request right after the "MCP" integration was created, that integration stays, which the error reports. No money moves and nothing is sent to anyone when it runs; a card can be charged or saved only if the customer completes the Allpay-hosted page before the link expires. The URL is meant for a customer outside the merchant's account and opens for anyone who has it, so the tool is open-world.
create_payment
Create a new API integration (an API login / API key pair) in the "Integrations → My sites" section — to connect the seller's website or service to the Allpay API. Payment is via redirect to the Allpay page; Hosted Fields and webhook are configured in the app. Returns api_login; the secret API key is not provided through this server — the user will find it in the app, in the "Integrations → My sites" section. No integration needs to be created in advance for a payment created in this chat — create_payment does it itself. Behavior: This tool creates a new API integration record in the authenticated merchant's Allpay account, so it changes state and retrying it creates another integration. The action is additive and does not delete or overwrite existing data. It is confined to the merchant's bounded Allpay account and does not access the public web or arbitrary external entities.
create_integration
Get descriptions of Allpay merchant dashboard screens: where a screen is in the menu, a direct link to it, what is on it and step-by-step instructions for common tasks (refunds, payment links, payouts, team, notifications, modules, integrations, registration). Use it whenever the user asks how to do something in the dashboard or where to find a setting; describe only buttons and fields that are in the result. Button labels are given in Russian as shown in the Russian interface. Table of contents (id → screen): {"payments":"Платежи","payment_refund":"Платежи → платеж → Возврат","subscriptions":"Подписки","payouts":"Выплаты","paypages":"Ссылки","paypage_form":"Ссылки → Создать ссылку \/ Изменить","payment_page":"Страница оплаты (то, что видит клиент)","affiliate":"Партнерка","settings":"Настройки","profile":"Настройки → Профиль","company":"Настройки → Компания","team":"Настройки → Команда","tariff":"Настройки → Тариф","notifications":"Настройки → Уведомления","permissions":"Настройки → Разрешения","paypages_settings":"Настройки → Платежные ссылки","payout_settings":"Настройки → Выплаты","support":"Настройки → Поддержка","modules":"Настройки → Платежные модули","module_subscriptions":"Настройки → Платежные модули → Подписки","module_currency":"Настройки → Платежные модули → USD & EUR","module_3ds":"Настройки → Платежные модули → 3DS","module_bit":"Настройки → Платежные модули → Bit","module_applepay":"Настройки → Платежные модули → Apple Pay","module_googlepay":"Настройки → Платежные модули → Google Pay","module_weekly_payouts":"Настройки → Платежные модули → Еженедельные выплаты","module_installments_advance":"Настройки → Платежные модули → Рассрочка авансом","integrations":"Настройки → Интеграции","integration_api":"Настройки → Интеграции → Мои сайты (API)","shopify":"Настройки → Интеграции → Shopify","allpay_receipts":"Настройки → Интеграции → Allpay Receipts","morning":"Настройки → Интеграции → Morning","easycount":"Настройки → Интеграции → EasyCount","gtm":"Настройки → Интеграции → GTM","mcp":"Настройки → Интеграции → MCP","login":"Вход в кабинет","registration":"Регистрация"}. Pass the ids of the screens you need in ids — several at once is fine. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_ui_guide
Permanently delete the entire stored history of this account's requests to the Allpay MCP server (what was asked and what the server answered). Account data, payments and their history are not affected, including the history and API records of payment requests made through create_payment. Call it only when the user asks to delete the request history, and only after their explicit confirmation. deleted — number of records deleted. Behavior: This tool permanently deletes stored MCP request logs for the authenticated merchant and, when it deleted something, records one audit event, so it changes state and is destructive. The successful deletion call is not written to the request log itself. Repeating it with no other MCP requests in between deletes nothing (deleted = 0) and writes no audit event, so the result is the same. MCP requests made between two calls are logged as usual, so a later call deletes those new records and writes one audit event for them. Each call also updates the access token's last-used time, IP and call counter and the IP rate-limit counter. It is confined to the merchant's bounded Allpay account and does not access the public web or arbitrary external entities.
delete_mcp_log
Get payment details by its ID. amount is in currency (a code, e.g. ILS / USD); if the card was charged in another currency, charged_amount and charged_currency are added. type: one_time — a regular payment (including installments paid in one payment), installments — installments (installments — number of payments the customer chose), subscription — a subscription payment (the first or a recurring charge), preauthorization — an amount reserved on the card (J5) to be captured later, card_token — a zero-amount payment that only saves the card (token) without charging it, its amount is not charged: for a subscription with a deferred start or for later token charges via the API. subscription_id — the subscription the payment belongs to, if any. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_payment
History of a payment by its ID — the same events the seller sees on the payment card in the app, in chronological order. For a refund/chargeback record the history of the original payment is returned (history_of_payment_id). events[]: date, event, amount and currency (if the event has an amount; refunds are negative). event: payment_created, api_payment_request (a request from the seller's server to the Allpay API), paid, future_charge (a scheduled charge), amount_reserved / captured_from_reserved / reservation_cancelled (J5), 3ds_check, token_received, token_payment, subscription_charge_failed, payment_failed, card_verification_failed, refund / partial_refund, api_refund_request, chargeback / partial_chargeback, chargeback_reversed, webhook_delivered / webhook_failed (a notification to the seller's server; attempt — attempt number, failed ones are retried for up to 24 h). request (url, method, body) and response — the request and the response: for api_* and captured_from_reserved — the seller's server request to Allpay and the Allpay response; for webhook_* — the Allpay request to the seller's server and its response (a long response is truncated). The customer's ID number (client_tehudat) in requests and responses is masked. error — reason the payment failed, payment_method — card / wallet. paylink_url — the payment link the payment was created through. flow (hosted_fields / redirect) — payment flow for API payments; integration — the integration that created the payment; test_mode — a test payment. Request parameters, responses, error codes and webhook fields are described in the API documentation: https://allpay.to/docs/allpay_api_reference_llm.md Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_payment_history
Created payment links, newest first. link — the link URL for customers; type: one_time — a one-time payment, installments — installments (up to installments payments), subscription — a monthly subscription; status: active / paused — disabled by the seller / expired — valid_till has passed. amount — total to pay including VAT in currency (null — the payer enters the amount), items — line items, if there are several; charged_currency — charge currency, if different. payments[] — number and sum of payments per charge currency, last_payment — date of the last payment. For subscriptions, active_subscriptions[] — number of active subscribers and the monthly sum. API integration links are not included. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_paypages
Number and sum of payments by filters, with grouping and ranking. Provides aggregate payment statistics, grouping and ranking. By default only paid live payments are counted (including ones refunded or charged back later), and the sum is net (minus refunds and chargebacks made in that period, plus chargeback reversals); J5 reservations not charged yet are not counted. Sums are returned separately per charge currency (totals: currency, count, amount; refunds / chargebacks — number of refunds and chargebacks) — never add up sums in different currencies. With group_by it returns groups[] (key, count, totals per currency, amount_ils_approx) and groups_total — the total number of groups. amount_ils_approx — converted to shekels at the current rate, only for comparing groups; when quoting it to the user, say it is approximate. Examples: top 5 customers by amount for a period — group_by=client, limit=5; revenue by month — group_by=month; which payment link earns most — group_by=paypage; share of foreign cards — group_by=card_type; Bit / Apple Pay / Google Pay / card — group_by=method; how many refunds — kind=refunds. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
count
Past payouts and monthly fee documents, newest first. payouts[]: date, amount, currency, bank — the bank whose account received the payout. documents[]: period (YYYY-MM) — the month the documents were issued for, currency, commission_receipt_url — PDF receipt for the fee, breakdown_url — PDF breakdown of fees by payment. A payout is credited to the account within 3 business days. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_payout_history
Payout bank account (bank_account: bank, branch — branch number and name, account — account number) and payout mode per currency (schedule[]: mode — auto_monthly once a month / auto_weekly every Monday / auto_threshold when the amount exceeds threshold / manual only on request). The account can be changed only through support, by sending a bank confirmation letter with the new details; the payout mode is changed in the app. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_payout_settings
Summary of the "Payouts" section per currency (currencies[]). ready — ready to be paid out now: amount (already net of fees), payments — number of payments, can_request — a payout can be requested manually (the amount exceeds min_request_amount), schedule — automatic payout mode. future — upcoming payouts: payments processed and a date assigned, amount — total, by_date — amounts by payout date (YYYY-MM-DD). processing — in processing: paid, but no payout date assigned yet. schedule.mode: auto_monthly — automatically once a month (next_date), auto_weekly — every Monday, auto_threshold — when the amount exceeds threshold, manual — only at the seller's request. payouts_blocked = true — payouts are blocked until KYC re-verification, the seller needs to contact support. A payout cannot be requested through this server — only in the "Payouts" section of the app. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_payouts
Search payments by filters. Returns a list of payments with id, date, amount, currency (code of the amount currency, e.g. ILS / USD), status, type; if the card was charged in another currency, also charged_amount and charged_currency. type: one_time — a regular payment (including installments paid in one payment), installments — installments (installments — number of payments the customer chose), subscription — a subscription payment (the first or a recurring charge), preauthorization — an amount reserved on the card (J5) to be captured later, card_token — a zero-amount payment that only saves the card (token) without charging it, its amount is not charged: for a subscription with a deferred start or for later token charges via the API. subscription_id — the subscription the payment belongs to, if any. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
search
Returns the current full catalog of Allpay services and their applicable prices. This endpoint is the authoritative source of current Allpay service prices. For an authorized user, it returns the prices applicable to their account, which may differ from general or default prices shown in documentation and knowledge-base articles. For an authorized user, prices are account-specific, falling back to partner or default prices where no account-specific price is set. The response includes each service's connection status (status: 1 — active; 2 — being activated; 0 — not connected; -1 — disabled, including for non-payment; -2 — being deactivated) and the flags is_trial/trial_till, is_free and paid_by_partner (the partner platform pays for the service, with no charge to the user). For an anonymous user, the response contains default prices without connection statuses. Monetary prices and fixed fees are in ILS; percentage fees are expressed as a percentage of the transaction amount. All prices and fees exclude VAT; vat_rate contains the applicable VAT rate. txn_fee_percent_local / txn_fee_percent_foreign — transaction fees for cards issued in Israel / abroad. Per service: price_monthly — monthly price; price_activation — one-time activation price; free=true — the service is free. Connecting a service does not change the transaction fee, except for Shopify. For Shopify (per_shop=true), price_monthly equals price_monthly_per_shop × shops_active. Shopify payments have separate total transaction fees: txn_fee_percent_total_local / txn_fee_percent_total_foreign. These totals already include the Shopify surcharge txn_fee_percent_extra and also exclude VAT. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_services
Subscriptions of the seller's customers (the "Subscriptions" section), newest first; charged monthly. status: active / completed — ended by its terms / error — the charge failed, it will be retried (failed_attempts — number of failed attempts) / cancelled — cancelled. amount — monthly amount in currency (charged_amount / charged_currency — in the charge currency, if different); charges_done — how many charges went through, paid_amount — for what total; next_charge_date — date of the next charge; ends — when it ends (never / date / after_charges). active_summary[] — totals for all active live subscriptions: number and monthly sum per charge currency. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_subscriptions
Allpay subscription fee (the "Tariff" section), in shekels. monthly_total — monthly charge excluding VAT, monthly_total_with_vat — including VAT (rate vat_rate); services[] — what it consists of (connected paid services, monthly — excluding VAT). paid_till — paid up to this date, next_charge_date — date of the next regular charge (null — no charges). billing_active = false — the account is not activated yet, no fee is charged. is_free — no fee is charged; is_trial — trial period until trial_till; paid_by_partner — the partner pays. payment_problem — a problem with the charge, the seller should check the card in "Tariff → Payment methods". service_ends — accepting payments is disabled and will stop working on this date. Prices and fees of individual services — in get_services. Behavior: This is a read-only lookup: it does not create, update, delete, or send merchant data, and repeating it changes nothing in the account. Technical logging: like every authenticated MCP request, the call is written to the server's MCP request log, which the merchant can erase with delete_mcp_log, and it updates the access token's last-used time, IP and call counter and the IP rate-limit counter. This bookkeeping is not merchant business data. It only accesses Allpay documentation or the authenticated merchant's bounded Allpay account, not the public web or arbitrary external entities.
get_tariff
Allpay ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Allpay's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Allpay alternatives on ChatGPT?
As of 2026-11-22, Allpay competes with Stripe, airpay, Antom, Cashfree, Checkout Page, ctrl payments, Fintoc, GoCardless and 13 more in ChatGPT Payment Processing & Gateways, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.