setup-revenue-monster
Revenue Monster Payment Gateway
Use this skill for Revenue Monster (RM) Open API payment integration work.
Source
Read references/revenue-monster-api.md before giving factual API guidance or writing integration code. It contains environments, OAuth token flow, the RSA signature algorithm with exact string-to-sign, hosted checkout fields, redirect and notify payloads, query, refund, reverse, reconciliation, methods, statuses, and error codes.
It also holds the Endpoint Catalogue (every documented operation) and points to the detail files:
references/revenue-monster-objects.md: Transaction Object, nested objects, type/status enums, method and region matrix, FPX B2C/B2B bank codes.references/revenue-monster-tokenization.md: recurring, tokenized customer, charge bound card, card-on-file tokens.references/revenue-monster-instore.md: Quick Pay, terminal events, POS, Android deeplink.references/revenue-monster-invoice.md: invoice / payment link API (/api/v3/...).references/revenue-monster-errors.md: every documented error code.
Read references/account-setup.md when the user asks how to register, where Client ID / Client Secret / Store ID / RSA keys live, sandbox activation, payment method activation, env var names, pricing, or plugins.
Read references/source-map.md when choosing which official RM docs page or SDK file applies.