Maly Maly Payments v1 Changelog Partners
Base URL Applied to every example. Stored only in this browser.
Core concepts

Key lifecycle

Issuing, replacing and protecting your credentials.

Your API key is issued once at account activation and shown to you once. We do not store a retrievable copy, so it cannot be re-sent to you later.

Replacing a key#

There is one API key per account, issued once at activation. There is no self-service rotation at launch. If a key is lost or exposed, contact your account manager to have it replaced; the old key is revoked and a new one issued. Plan for a brief cutover in which you switch systems to the new key and the old key stops working.

Protecting a key#

  • Store the key in a secret manager or environment variable, never in source control.
  • Limit which of your systems and staff can read it.
  • Log the calls you make with a request identifier, so unusual traffic is visible.
  • Use a separate key per environment.
i

Source IP restriction Restricting production traffic to an agreed set of source IPs is available on request. Raise it during onboarding if your platform egresses from fixed addresses.

Maly Payments API v1 · Documentation 1.1 · July 2026
Maly Tech Ltd. This guide is provided for information. Where it differs from your signed agreement, the agreement applies.