Antom
2C2P Pte. Ltd v1.1.2
Integrate and manage payments
From the developer
Declared limitations
- Query a payment from another provider. A Stripe payment is outside the connected Antom account.
- Translate payment-related text. Translation requires no merchant account access or payment operation.
- Draft a refund request email. Writing a message is not a request to retrieve or execute a refund.
Not specified in the available declarations: capabilities, pricing & account requirements.
Onboarding example
Help me check the status of a payment in my Antom account and investigate any reported errors.
Sources & dates
Developer declarations; not independently tested. Listing last checked Nov 16, 2026. Package observed Nov 16, 2026.
Description
From the marketplace listing
Antom helps merchants, developers, and finance teams integrate payments, investigate transaction issues, and reconcile settlements. It combines payment integration guidance, connected merchant account tools, and settlement report analysis in one plugin. Build your payment integration with guidance on product selection, integration methods, SDKs, and API usage. Generate and review integration code, troubleshoot payment notifications and API errors, and prepare for sandbox testing and go-live. Supported integration scenarios include One-time Payments, Tokenized Payment, Subscription Payment, and the Billing Product Family through Payment Element, Checkout Page, or API-only integration. Connect an eligible Antom merchant account through OAuth to retrieve merchant information, check payment and refund status, inspect transaction details, review integration logs, and diagnose failed requests. You can also retrieve settlement report download links and create or list subscription products and prices within your authorized merchant account. Analyze Antom Settlement Detail CSV or XLSX reports to validate settlement calculations, summarize net settlement and fees, compare fees by payment method, and identify discrepancies with supporting figures. You can provide report files directly; online report retrieval and transaction lookups through the reconciliation skill additionally require an installed and independently authenticated Antom CLI. Account-connected features depend on your merchant eligibility and granted permissions. Skills load supporting knowledge from Antom-hosted online documentation. Report analysis requires a supported Python environment and dependencies; CLI-based online retrieval is unavailable in environments that cannot install or authenticate the Antom CLI. The connected tools support inquiries, diagnostics, and subscription catalog configuration; they do not initiate payments, issue refunds, or release settlement funds. For institution-side developers, the Antom Channel Integration skill provides AIS SDK contract guidance, adapter project generation, field mapping, security implementation, testing and delivery guidance. CLI source, templates and AIS SDK 1.5.2 are included. Building and running the channel generator requires a compatible local macOS/Linux environment with Java 8 and Maven 3.6.3 or later; installing the skill alone does not build the CLI or deploy a channel adapter.
Language: English · Automatically detected from descriptions.
Changes
No changes recorded yet. Follow this plugin to keep track of future changes.
First seen Nov 16, 2026. Last seen Nov 16, 2026.
Similar plugins
Find competitors to follow as you develop your plugin.
-
Antom payment integration guidance for ChatGPT and Codex.
Shared terms: integrate, payment, antom, api
-
Connect your airpay merchant account to check transactions, refunds, UPI QR payments, and settlements through conversation.
Shared terms: payment, merchant, refund, retrieve
-
Assess Whop for business payments and plan merchant onboarding, checkout, websites, ecommerce, ads, and eligible embedded-finance workflo...
Shared terms: payment, billing, checkout, eligible
-
Connect your GoCardless account to look up payments, customers, mandates, payouts, and refunds, and to take actions such as creating paym...
Shared terms: payment, api, guidance, integration
-
Connect your Razorpay account to access your payment data through conversation. Ask ChatGPT about your payments, orders, refunds, settlem...
Shared terms: payment, merchant, method, refund
Files & skills
File archives
Skill instructions
antom-channel-integration11 KB
--- name: antom-channel-integration description: Help external developers use Antom Channel Integration (ACI) to implement and test channel adapters against the AIS platform standard and SDK contracts. Use for integration questions, capability selection, protocol adaptation and troubleshooting; do not deploy the platform or change production configuration. license: Apache-2.0 --- # antom-channel-integration (ACI) Antom Channel Integration (ACI) is Antom's channel integration tool for external developers implementing adapters against the AIS platform standard. Answer knowledge-only questions without changing files. For implementation requests, edit the user's designated adapter project, not the Skill installation directory. ## Choose the task before acting | User intent | Workflow | | --- | --- | | Explain contracts or troubleshoot | Read the selected topic and answer with evidence. Do not create or edit a project. | | Create an adapter | Follow the authoritative [generation intake](references/project-generation.md#confirm-the-generation-inputs). Obtain a user-supplied institution code first; only then collect other missing choices. Wait for required answers before configuration, dry run or generation. | | Implement or change an adapter | Inspect the designated project and follow the [implementation workflow](references/implementation-workflow.md). Preserve unrelated work; do not run init over an existing project. | | Validate or prepare delivery | Follow [testing](references/TESTING.md) and [delivery](references/delivery.md). Report what actually ran and what remains unverified. | Generation intake starts with a mandatory user-supplied institution code, followed by payment/3DS scope, transaction and notification choices, and only two security yes/no choices. Derive identifiers directly without a naming-approval round. The complete questions, dependency rules and naming conventions live in project generation; do not duplicate or replace them with example defaults. Keep generated source and documentation in English. ## Ask for missing information For new-project creation, a valid institution code explicitly supplied by the user is a prerequisite to every other intake question. If it is missing or unusable, ask only for **Institution code** and wait for the user's reply. Do not ask other questions in the same call or while this answer is pending. A display name, project identifiers, directory name, user identity or example configuration cannot substitute for a user-supplied code. Retain other answers already supplied, but ask about missing ones only after this prerequisite is met. Do not ask again when the user has already explicitly supplied a valid code for this task. Ask in the user's language with only a short field label or question and the necessary choices. Retain supplied answers; omit known fields. Keep SDK details, SPI dependencies, generated identifiers, implementation advice and progress summaries out of the questionnaire. For an actual conflict, add only the one sentence needed to resolve it. Use the available question/input tool instead of a chat-only question. The institution code requires a standalone free-text input box with no options, examples, placeholder or default. In Codex, use `request_user_input_async` with exactly one question `title` and omit `options`; use an equivalent free-text question tool in other clients. Fall back to one short chat question only when the client has no suitable input tool. See the [generation intake](references/project-generation.md#confirm-the-generation-inputs) for the remaining fields. ## Establish the sources of truth - **API facts:** the target project's actual AIS SDK types, fields, methods and default implementations take precedence over this package's snapshot. Use `jar tf` and `javap` when only a JAR is available; developers do not need access to platform source code. - **Business rules:** the institution protocol and user-confirmed mappings, signing input and
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 189 — file references are metadata, not package contents.
antom-integration8.67 KB
--- name: antom-integration description: >- Antom payment integration skill for product and integration-mode selection, integration Q&A, code implementation, troubleshooting, sandbox testing, and go-live guidance. Use for One-time Payments, Tokenized Payment (recurring auto-debit), Billing, Payment Element, Checkout Page, and API-only integration. --- # Scope Use this skill to: - locate relevant Antom product, integration, SDK, notification, checklist, and troubleshooting knowledge - write or modify Antom payment integration code for the selected product, integration mode, and tech stack - diagnose integration issues from result codes, API names, request IDs, logs, asynchronous notifications, and sandbox or go-live symptoms # Document Access Guidelines Fetch Antom online docs with curl: ```bash curl -sL "https://****/****.md" ``` # Get Integration Documentation Use this section as the shared knowledge lookup for product advice, Q&A, code implementation, and troubleshooting. ## SDK Selection When the user has not chosen a backend tech stack, prioritize languages with official Antom SDKs listed in SDK Description; otherwise, respect the user's chosen or existing stack. Read [SDK Description](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/select-sdk.md) when a server-side SDK is involved and you need to select a language, confirm the public version or installation, configure the API domain, or prepare backend code. Product-specific sample-code is selected from the matched product document. ## Product Selection Read [Product Decision](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/product-decision.md) for product or integration-mode advice. Use its clarification template only when needed. Choose the product through Product Decision before opening any product overview or selecting an integration mode. After product selection, prefer Checkout Page (CKP) when the user wants rapid integration and broad payment-method coverage, if it fits the selected product and scenario. ## Integration Documentation Select Based on the user's selected product or capability and any applicable integration mode, locate the corresponding integration documentation: - [One-time Payments](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/one-time-payments.md) - [Tokenized Payment](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/tokenized-payment.md) - [Billing subscription integration](https://cdn.marmot-cloud.com/page/antom-integration-doc/billing/subscription-integration-core.md) Read the most specific sections available in the matched product doc. - After selecting a product, do not load other product docs unless comparison or migration is requested. For Billing, follow its Router and load only the selected scenario, capability, path, and operations. - For Q&A or product advice: infer what you can, read the closest relevant docs, and state assumptions when useful. - For troubleshooting: route by resultCode/resultMessage, API name, requestId, debug log, or error text first. # Writing Code Before writing or modifying code, first confirm the user's selected product and tech stack. Confirm an integration mode only when the selected flow has a payment-path or UI choice. Blocking list before coding: Do not write or modify integration code until all applicable items below are complete. - [ ] Read [Product Decision](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/product-decision.md) to confirm the product category and integration mode, even when the user's request appears specific. Skip only if the user explicitly asks to skip product selection. - [ ] Read [SDK Description](https://cdn.marmot-cloud.com/page/antom-integration-doc/references/select-sdk.md) when a backend language or SDK is involved. - [ ] Read the matched product overview from `Integration Documentation Select`: - One-time Payments - Tokenized Payment - Billing - [ ] Fr
Preview of the first 4,000 characters. Read full instructions →
antom-reconciliation-expert14.6 KB
--- name: antom-reconciliation-expert description: "Reconciliation Expert - Handles retrieval, download, parsing, validation, and financial analysis of Antom settlement reports. Supports Settlement Detail reports only (CSV/XLSX). Triggers: settlement, reconciliation, payout, fee verification, empty batch, gross profit, financial overview, report download." --- **Version**: 2.0.0 # Reconciliation Expert Given a date range and merchant report, complete the full workflow of report retrieval, download, parsing, validation, attribution, and reporting — producing a mathematically self-consistent settlement analysis report. ## 0. Knowledge Base Domain knowledge is served via CDN and is not embedded in this file. **Knowledge base entry point**: ``` https://cdn.marmot-cloud.com/page/antom_bill_reconciliation_doc/wiki/index.md ``` ## 0.0 First-Use Environment Setup (Mandatory) On the **very first interaction** of each session, run this command to verify Python and install dependencies: ```bash python3 --version && pip3 install "openpyxl>=3.0" "requests>=2.20" "jsonschema>=4.0" ``` - If this command **succeeds**: proceed to Section 0.2 (Version Check) - If `python3` or `python` is not found: guide the user to install Python 3.8+ — `brew install python` (macOS), `apt install python3` (Linux), or download from https://python.org (Windows). On Windows, use `python` instead of `python3` and `pip` instead of `pip3`. - If `pip3 install` fails: show the error and guide the user through manual setup For **online bill retrieval**, additionally verify antom CLI: ```bash antom version && antom whoami ``` - If `antom: command not found`: run `export PATH="$HOME/.local/bin:$PATH"` and retry. If still not found, guide the user through Section 0.1 items 3–4 - If `antom whoami` shows no active profile: guide the user to run `antom login` **Rules**: - Only run once per session — skip on subsequent interactions - If all checks pass, never re-run them in the same session ## 0.1 Environment Prerequisites Detailed reference for manual setup when the automated check above fails: 1. **Python 3.8+ is installed**: run `python3 --version` (or `python --version` on Windows) to verify. Install via `brew install python` (macOS), `apt install python3` (Linux), or https://python.org (Windows). 2. **Python packages are installed**: run `pip3 install "openpyxl>=3.0" "requests>=2.20" "jsonschema>=4.0"`. 3. **antom CLI is installed and on PATH** (only needed for online bill retrieval; supports macOS / Linux / Windows): install via one command: - **macOS / Linux (including WSL)**: `curl -fsSL https://mdn.alipayobjects.com/portal_4vwbay/uri/file/as/release/install.sh | bash` - **Windows PowerShell**: `irm https://mdn.alipayobjects.com/portal_4vwbay/uri/file/as/release/install.ps1 | iex` If `antom: command not found`, run `export PATH="$HOME/.local/bin:$PATH"` (macOS/Linux). Verify with `antom version`. 4. **Authentication is configured** (only needed for online bill retrieval): run `antom login` (browser) or `antom login --interactive` (manual credentials) to authenticate. For Agent/CI scenarios, use `antom login --non-interactive` then `antom login --complete`. Verify with `antom whoami`. Local-only operations (parsing, validation, CDN knowledge loading) require only items 1–2. Online bill retrieval additionally requires items 3–4. ## 0.2 Version Check Call `cdn_loader.check_version()` to load the version manifest from CDN. This function checks every session (in-memory 300s cache prevents duplicate network calls within the same process). - If it returns a **manifest JSON** → compare local version (this file's `**Version**` field) against the manifest. If a newer version is available, **you MUST inform the user** by appending a brief notice at the end of your response (e.g., "ℹ️ New version available: 2.0.0 (current: 1.0.0). Run the update command to upgrade."). Then execute update if needed per the manifest's `comparison_rules` and `update_meth
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 14 — file references are metadata, not package contents.
Release notes
Updated the Antom Integration skill with current Billing subscription guidance, SDK selection guidance, and settlement-currency clarification.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- 2C2P Pte. Ltd
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Package observed Nov 16, 2026.
Technical details
- First seen
- Nov 16, 2026 · 06:00 UTC
- Last seen
- Nov 16, 2026 · 12:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ad9d66d88e08191b2c0939949ce5743
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.