Integration FAQ

Where should I start?

Create a sandbox account, save the one-time key in server-side secret storage, and follow your first sandbox payment.

Which API operations are public?

The API Reference is the current reviewed merchant-key contract. If an endpoint appears only in an old guide or package, it is not public contract. See API availability for portal-only boundaries.

Can browser or mobile code call Moneybag directly?

No merchant key should be shipped to a browser or mobile app. Call Moneybag from your trusted backend and expose only the order-specific operation your client needs.

How do I know a payment succeeded?

Do not trust a customer redirect. Verify the transaction from your backend, confirm its order and amount, and make fulfillment idempotent. Signed webhooks are a complementary reconciliation signal.

Is there an official SDK or commerce plugin?

No SDK or plugin is listed as approved in this migration. Use the SDK and library checklist and require an owner-approved release artifact before installing a Moneybag-labelled package.

What are the rates, limits, fees, settlement timing, refund policy, or support SLA?

Those policy commitments are not defined by the public OpenAPI artifact and are not published here. Use the terms and approved support channel for your merchant account; do not rely on values copied from the previous documentation site.

What should I include when asking for help?

Follow the support checklist. Include sanitized request context, never credentials, full customer payloads, or webhook secrets.