Integrate from any server stack

Moneybag's reviewed public contract is HTTP and JSON. Generate types or a client from the API Reference, or call the documented operations with the maintained HTTP client in your trusted backend.

Evaluate a client or plugin

Before adopting any Moneybag-labelled package, confirm all of the following from an owner-approved release artifact:

the package registry and source repository are controlled by Moneybag;
the released version targets the current public OpenAPI contract;
checkout fields and response parsing match the generated schema;
the merchant key remains server-side and sandbox/production configuration is explicit;
retries are bounded and never replay non-idempotent money movement blindly;
webhook signatures use the current signing contract and raw request body; and
supported runtime versions, maintenance status, license, and vulnerability-reporting path are published.

Direct HTTP is the baseline

If those facts are unavailable, use a standard HTTP client and the exact schema from Scalar. Keep Moneybag-specific code behind a small server-side adapter so a future verified SDK can replace it without changing order or fulfillment logic.