Contract boundaries
What is publicly available
The reviewed merchant-key contract contains exactly 21 sandbox operations: checkout, verification, six subscription-plan operations, ten subscription operations, and three payment-outcome simulators. Those operations are fully documented in this site and executable through the sandbox API Lab.
Capabilities outside the public API
Some Moneybag features are operated from the merchant portal rather than the public API. They are not part of the reviewed sandbox contract, are not executable in API Lab, and have no public request or response schema.
| Capability | Where it lives today | |---|---| | EMI option and instalment discovery | Configured per merchant. EMI is selected during checkout using the fields in the EMI guide. | | Webhook endpoint management | Merchant portal: create endpoints, choose events, rotate the signing secret, and inspect deliveries. | | Hosted-checkout session inspection | Internal to the hosted checkout. Confirm payment state with the public verification operation instead. | | Transaction lists and history | Merchant portal reporting views. |
If your integration needs one of these as a public API, raise it with your Moneybag contact so it can be reviewed for the contract.
Claims in the retired documentation
The retired documentation referenced payment list and detail endpoints that have never existed in this API, so an integration copied from it will fail. Use the verification operation to confirm payment state.
Refund, payout and settlement operations, payment-link management, and other operator workflows also remain outside the reviewed public artifact.
New public capabilities must first receive a merchant-scoped contract, focused authorization tests, and OpenAPI review.