Added
Internal account configuration
November 5th, 2026
Define payment rules on an internal account to automatically deny payment orders and incoming payments that do not match your eligibility criteria.
What's new
- Internal accounts of type
ownnow support aconfigurationobject with two independent sections,payment_orderandincoming_payment. - Each section is either
null(no restrictions) or a rule set with amode(allowlistordenylist) and one rule. - Each rule can match on
payment_type,direction, andexternal_accounts. A field set tonullmatches any value. internal_account_configurationis now a supported value ofpayment_validation.type. When a payment fails the rule,payment_validation.statusisfailedandpayment_validation.status_detailsispayment type denied.- The dashboard now shows payment rules on the internal account detail page and lets you edit them in the internal account form.
Mambu Payments enforces the rules only when Customer Success configures the internal_account_configuration validation for your organization. The action configured on the validation sets the payment's next status.
What changed
POST /internal_accountsnow accepts an optionalconfigurationin the request body. Both sections default tonull.POST /internal_accounts/<internal_account_id>now accepts an optionalconfigurationin the request body. Theconfigurationyou send replaces the whole existing configuration. Mambu Payments clears any section that you omit or set tonull.GET /internal_accounts/<internal_account_id>now returnsconfigurationwith both sections. A section isnullwhen not set.
No changes are required on your end. Existing internal accounts return null for both sections.
Example
The following request denies all SWIFT payment orders from an internal account.
{
"configuration": {
"payment_order": {
"mode": "denylist",
"rules": [
{
"payment_type": "swift",
"direction": null,
"external_accounts": null
}
]
},
"incoming_payment": null
}
}Read the internal account configuration guide to learn how rules are evaluated.
