GuidesAPI ReferenceChangelog
Log In
Changelog

13 February 2026

⚠️ Deprecations

  1. The GET /organizations/{id}/kyc-link (v1) endpoint has been removed

🔜 Coming Soon

  1. LATAM onramp support — We're adding onramp support for MXN (Mexican Peso), BRL (Brazilian Real), and ARS (Argentine Peso). Stay tuned!

🚀 New APIs

  1. Archive endpoints for https://developers.muralpay.com/docs/counterparties-and-payout-methods and Payout Methods — soft-delete resources you no longer need:
  • POST /api/counterparties/counterparty/{id}/archive
  • POST /api/counterparties/{id}/payout-methods/{payoutMethodId}/archive
  1. Bre-B COP external pay-ins (COP virtual accounts using Bre-B keys). The keys can be fetched using the account details endpoint.

⭐ Enhancements

  1. Expanded KYC coverage — Added 20+ new government ID types across 50+ countries, including Residence Permits, Voter IDs, PAN Cards (India), My Number Cards (Japan), and more
  2. MaxLength validation on payout request memo field — The memo field now enforces a maximum length, returning a clear validation error if exceeded
  3. Bank account owner name validation — Added upfront validation requiring both first and last name for LATAM and regional currencies, preventing downstream payout failures
  4. Panama NATIONAL_ID validation relaxed — Updated from exactly 8 digits to 5-12 digits, supporting Colombian nationals with Bancolombia Panama accounts
  5. PayoutDestinationError — New structured error (HTTP 412) when a payout method is unavailable. Returns payoutMethodId and payoutIndex so you can programmatically identify which payout failed — https://developers.muralpay.com/docs/errors#payoutmethoderror
  6. Improved payout error messages — Validation errors on payout creation (e.g., unsupported routing number for wire) now surface the specific error message instead of a generic error

🐛 Bug Fixes

  1. Fixed a 500 error on payout creation when physicalAddress was missing — now correctly returns 400 validation error
  2. Fixed contact creation error propagation — validation errors (e.g., invalid bank account numbers) now return their specific message instead of a generic "Unable to create contact"
  3. Fixed floating-point precision issue in developer fee percent calculations
  4. Added global string sanitization to prevent encoding errors from special characters in request inputs
  5. Improved UUID validation across blockchain transaction endpoints — invalid formats now return 400 instead of 500