> ## Documentation Index
> Fetch the complete documentation index at: https://developer.me-cash.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API

> Latest production changes for the meCash API Platform.

Stay on top of API changes that could impact your integration. Each entry notes the rollout status plus any required follow-up.

<Note>
  Looking for something earlier? Reach out to <a href="mailto:support@me-cash.com">[support@me-cash.com](mailto:support@me-cash.com)</a> and we can share archived notes.
</Note>

## How to read these notes

* **Status** clarifies whether the update is fully live or rolling out.
* **Action needed** highlights anything developers must do (schema updates, new scopes, SDK upgrades, etc.).
* **Heads-up** calls out upcoming deprecations so you can plan ahead.

## API Platform

<Accordion title="June 2026 — Version v1.x (Status: Live)">
  **New Features**

  * **EUR recipient enhancements**: Added support for specifying destination countries when creating EUR recipients, improving coverage across supported European payout corridors.
  * **Recipient management APIs**: Introduced support for creating, retrieving, and managing saved recipients for repeat transfers.
  * **Sender information support**: Added sender address book capabilities to simplify recurring international payment requests.
  * **USD wallet funding details**: Enhanced wallet APIs to return funding instructions for USD wallets.

  **Enhancements**

  * **Transaction details enrichment**: Expanded transaction responses to include additional source account information and payment metadata.
  * **Validation improvements**: Standardized validation rules and error responses across recipient, sender, and transaction endpoints.
  * **Phone number validation**: Improved backend validation to reject invalid phone number formats before processing requests.
  * **EUR transfer support**: Extended validation and processing for supported EUR destinations.
  * **Performance improvements**: Optimized transaction processing and API response times across several payment flows.

  **Bug Fixes**

  * Fixed an issue that caused errors when processing EUR recipient requests.
  * Fixed delayed retrieval of USD transaction details.
  * Fixed missing funding account information in USD and EUR wallet responses.
  * Fixed source account information returning empty values in transaction responses.
  * Fixed a USD to CNY exchange rate issue that could result in server errors.
  * Fixed refund processing issues affecting USD transactions.
  * Fixed OTP validation failures during transaction confirmation.
  * Resolved several API stability and performance issues across transaction and payout endpoints.

  **Action needed:** No integration changes are required. These updates are backward compatible with existing API integrations.
</Accordion>

<AccordionGroup>
  <Accordion title="May 2026 — Version v1.x (Status: Live)">
    **New Features**

    * **SWIFT Payment Channel Split**: The generic `SWIFT` payment channel has been replaced with three explicit charge-bearer variants to give integrators finer control over who absorbs wire-transfer fees:

    | **Channel**         | **Charge Bearer** | **Description**                                             |
    | :------------------ | :---------------- | :---------------------------------------------------------- |
    | `SWIFT_CUSTOMER`    | Sender            | The sending customer bears all transfer charges.            |
    | `SWIFT_SHARED`      | Both parties      | Transfer charges are shared between sender and beneficiary. |
    | `SWIFT_BENEFICIARY` | Beneficiary       | The beneficiary bears all transfer charges.                 |

    **Backward Compatibility**

    * Integrations still sending `paymentChannel: "SWIFT"` should migrate to `SWIFT_CUSTOMER`, `SWIFT_SHARED`, or `SWIFT_BENEFICIARY` at the earliest opportunity.
    * Choose `SWIFT_CUSTOMER` if your platform absorbs the full cost of the transfer.
    * Choose `SWIFT_SHARED` if transfer charges should be deducted from the beneficiary's received amount.
    * Choose `SWIFT_BENEFICIARY` if the beneficiary should bear all transfer charges.

    **Action needed:** Update your payout request payloads to use `SWIFT_CUSTOMER`, `SWIFT_SHARED`, or `SWIFT_BENEFICIARY` in place of the deprecated `SWIFT` value for USD Transactions. No other fields change — recipient account details, sender details, and quote request format remain identical.
  </Accordion>

  <Accordion title="March 2026 — Version v1.x (Status: Live)">
    **New Features**

    * **Mobile Money Collections API**: Introduced API endpoints for collecting payments via mobile money across multiple African currencies.
    * **Bulk Payout for Businesses**: Enabled businesses to process multiple payouts in a single request, improving operational efficiency.
    * **Pay with Mobile Money**: Added support for mobile money as a payment method within API integrations.
    * **Pay by Bank App Integration**: Introduced support for bank-based payment flows through API integrations.

    **Enhancements**

    * **Nickname validation (API level)**: Added backend validation to ensure nickname consistency across platforms.
    * **Removed account validation constraints**: Improved compatibility with diverse account formats globally.
    * **Standardized backend error responses**: Unified error structures for easier debugging and integration.
    * **API response codes implementation**: Introduced consistent response codes for a better developer experience.
    * **Multi-user access (roles & permissions)**: Enabled role-based access control and scalable user management.
    * **IP allowlisting enforcement**: Added an extra layer of security by restricting access to approved IPs.
    * **Webhook enhancements (`settledAmount` field)**: Expanded webhook payloads to include settlement information.
    * **Transaction activity logging**: Improved auditability by logging all transaction-related actions.
    * **CloudWatch monitoring integration**: Enhanced system observability and performance monitoring.
    * **Sandbox & testing improvements**: Improved API testing reliability and sandbox environment setup.

    **Bug Fixes**

    * **Static quote currency issue**: Fixed incorrect handling of quote currencies during transaction creation.
    * **Missing account number in response**: Ensured account numbers are returned correctly in API responses.
    * **Phone number validation gaps**: Strengthened validation to prevent malformed inputs.
    * **Incorrect transaction status (refunded vs completed)**: Fixed status inconsistencies for refunded transactions.
    * **Sandbox account response issue**: Corrected invalid account object responses in sandbox.
    * **Admin transaction server error**: Resolved backend errors affecting admin transaction views.
    * **Stamp duty inconsistencies**: Fixed incorrect stamp duty deductions in API transactions.
  </Accordion>

  <Accordion title="February 2026 — Version v1.x (Status: Live)">
    **New Features & Enhancements**

    * **Mobile Money Collections API**: Exposed a new API to discover supported providers and request mobile money payments in RWF, KES, TZS, and MWK.
    * **Webhook Enhancements**: Updated collections webhooks to explicitly provide fund sender details.
    * **Virtual Cards & Rates APIs**: Implemented APIs to fetch exchange rates for virtual cards and manage rates independently of payment channels.
    * **Static Accounts**: Backend update to natively accept `accountName` based on customer type (retail or business).
    * **Response Updates**: Updated recipient and payout creation responses to return source of funds and echo back all payload details.

    **Documentation Updates**

    * Restricted USD payouts to SWIFT only (removed "Bank Transfer" option).
    * Cleaned out legacy payout references from developer docs.
    * Removed restrictions tying country bank lists to specific route IDs.
  </Accordion>

  <Accordion title="January 2026 — Version v1.x (Status: Live)">
    **New Features & Enhancements**

    * **Standardized Error Responses**: Unified the structure of error responses across all backend services to provide consistent and predictable feedback for frontend and mobile integrations.
    * **Partner Integration Comms**: Established standardized communication protocols for managing USD virtual account data with Modena.

    **Infrastructure & Performance**

    * **Optimized Account Retrieval**: Updated the virtual account flow to fetch existing account numbers from the database rather than repeatedly calling partner APIs, reducing latency and avoiding downtime.
    * **Deployment Versioning**: Upgraded the infrastructure (Terraform) to ensure services only deploy specific image versions rather than defaulting to "latest," preventing accidental overrides.
  </Accordion>

  <Accordion title="November 2025 — Version v1.x (Status: Live)">
    **New Features**

    * **Crypto On-Ramp Endpoints**: We have exposed new endpoints to support fiat-to-crypto transactions. You can now fetch real-time exchange rates, view fee breakdowns (network vs. transaction fees), and initiate crypto purchases (BTC, ETH, USDT) using NGN.
    * **Credit Transaction Retrieval**: A dedicated endpoint has been added for retrieving and posting credit transactions, ensuring reliable querying for transaction history integrations.
    * **Dynamic Pricing Configuration**: We introduced endpoints to fetch pricing configurations directly from our backend (integrated with Sanity). This allows for dynamic pricing updates without requiring client-side code changes.

    **Improvements**

    * **Payout Validation Enforcement**: To reduce failed transactions, we now enforce mandatory field validation at the API level for **USD**, **EUR**, and **GBP** payout instructions. Incomplete payloads will now return specific validation errors before processing.
    * **Virtual Account Naming**: The `accountName` parameter for Dynamic Virtual Accounts is now optional. If omitted during creation, the system will automatically default to using the registered business name.
    * **Optimized Payout Payloads**: We have removed the need to send redundant `country` and `currency` fields in the Payout API payload, as these are now inherited directly from the associated Quote object.

    **Fixes**

    * **Login Error Messages**: Standardized error responses for failed login attempts. The API now returns a specific "Invalid login credentials" message instead of a generic server error.
  </Accordion>

  <Accordion title="October 2025 — Platform Release (Status: Live)">
    * Added new outbound payment routes so you can reach more corridors without custom onboarding—check the API Reference for the latest supported `destinationCountry` values.
    * `accountName` is now supported on dynamic virtual account creation, letting you assign customer-friendly names; when omitted, we automatically fall back to your registered business name.

    **Action needed:** Pass `accountName` anywhere you need campaign- or store-specific labeling, and refresh your routing matrix to take advantage of the new payout corridors.
  </Accordion>
</AccordionGroup>
