Skip to main content
PATCH
Update Payment Code

Authorizations

Authorization
string
header
required

Bearer HTTP authentication specified with the header Authorization: Bearer <access_token>

Headers

Monime-Version
enum<string> | null

Specifies which version of the Monime API will handle this request.

Available options:
caph.2025-08-23,
caph.2025-06-20
Monime-Space-Id
string
required

The value is the tenancy parameter that Monime uses to determine which space the request is intended for.

Maximum string length: 64
Pattern: ^spc-.*$

Path Parameters

id
string
required

The unique ID of the payment code to update.

Pattern: ^pmc-.*$

Body

application/json

Partially updates an existing payment code with new values, rules, or account bindings.

name
string | null

Updated display name or label for the payment code.

Required string length: 3 - 64
amount
object | null

Updated amount to charge per use.

duration
string | null

New expiration duration for the code.

enable
boolean | null

Flag to activate or deactivate the payment code.

customer
object | null

Updated customer information for this payment code.

reference
string | null

New reference string for tagging the payment code.

Maximum string length: 64
authorizedProviders
enum<string>[] | null

Updated list of mobile money providers allowed to use this code.

Required array length: 1 - 10 elements

The ID of the MOMO as identified by Monime. E.g. m17 to denote Orange Money SL

Available options:
m17,
m18
authorizedPhoneNumber
string | null

New MSISDN authorized to use this payment code exclusively.

recurrentPaymentTarget
object | null

Updated target count or amount for completing a recurrent payment code.

financialAccountId
string | null

Updated destination financial account for funds settlement.

Maximum string length: 64
Pattern: ^fac-.*$
metadata
object | null

Updated metadata for storing additional context about the payment code.

Response

200 - application/json

OK

success
boolean

Represents the status of the query operation, confirming if it was successful. This field is always true

messages
any[]

Contains a list of messages providing relevant information or feedback related to the query or operation

result
Payment Code · object

A Payment Code is a programmable, short-lived token that allows users to collect payments from others.
It is especially useful in USSD-like or QR-based flows, where the payer enters or scans a code to complete a transaction.

Payment Codes provide flexibility for both one-time and recurrent collections, with configurable restrictions and targets.


Use Cases

  • USSD Payment Collection
    A merchant generates a Payment Code and displays it in USSD. Customers enter the code to make payments.
    Example: A vendor creates a one-time code for SLE 50 which a customer redeems via their mobile money wallet.

  • QR Code at Point of Sale
    The Payment Code is encoded as a QR displayed at checkout. Customers scan the QR to pay.
    Example: A shop generates a QR-based Payment Code for SLE 200, which is redeemed on the spot.

  • Recurring Subscription Collection
    A fitness center issues a recurrent Payment Code for monthly fees.
    Example: The code accepts up to 12 payments of SLE 500 each, after which it auto-completes.

  • Targeted Collection
    Restrict a Payment Code to a specific MSISDN or provider.
    Example: Only customers on Orange Money with a registered number can redeem the code.