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

# Changelog

> Stay informed about the latest service updates from FedaPay SA. Discover new features, platform enhancements, bug fixes, and tool changes.

<Update label="September 5, 2026" tags={["Improvement"]}>
  **New Balance Interface**

  The **Balance** page has been updated to provide better visibility into available funds and temporarily held amounts. The different balances are now **consolidated into a single balance**. Merchants no longer need to select a balance or payment method before making a payment request.

  The new interface also introduces two categories of held funds:

  * **Temporary Holds:** These include **payouts, pending refunds**, and **pending payment requests**. If the operation fails, the held funds are automatically returned to the available balance.
  * **Risk Reserves:** These include **disputes (chargebacks)** and the **rolling reserve**, when amounts are held according to the risk policy applied to the account.

  This update allows merchants to better understand the composition of their balance and distinguish available funds from amounts that are temporarily or permanently held.
</Update>

<Update label="July 31, 2026" tags={["New","Improvement"]}>
  **New Account**

  **Tap & Go Account :** A new account type is now available for Tap & Go merchants. The **Tap & Go Account** allows you to accept payments directly from your customers via QR Code, USSD, or NFC, without requiring an internet connection (for USSD payments) or a physical POS terminal. Thanks to the Tap & Go mobile app, merchants can now track all transactions made		by their customers in one place.

  Account creation requires submitting information and documents as part of FedaPay’s general KYC process, including the legal representative's **CIP**, the **IFU**, and optionally the **RCCM or company registration number**.

  [Learn more](tap-go/en/faq-en)
</Update>

<Update label="July 31, 2026" tags={["Improvement"]}>
  **Account Validation & Risk Management Improvements**

  **Context :** Following an increase in fraudulent transaction reports and to align with regulatory requirements under our license, the account validation process has been revised and improved.

  * **Introduction of new documents: The Sworn Statement, General Terms of Use (CGU), and Service Level Agreement (SLA)** must now be downloaded, completed, and uploaded during the validation process.
  * **Removal of fields :** The *signature* and *Capital* fields have been removed.
</Update>

<Update label="February 5, 2026" tags={["New"]}>
  * **TAP & GO Available on iOS :** The TAP & GO app is now available on iOS. Merchants can download it from the App Store and accept payments directly on their iPhone.
  * **TAP & GO V2 :** In this new version of the app, merchants can now initiate a payment directly via QR Code or USSD for their customers without needing physical support. This update makes payment collection more autonomous, fast, and flexible.
</Update>

<Update label="January 24, 2026" tags={["Improvement"]}>
  <span style={{color: "#008029"}}>Description</span> **Field Added for Payouts :** An optional <span style={{color: "#008029"}}>description</span> field is now available when creating a payout. It allows merchants to specify the context or purpose of the deposit, improve transaction tracking (Dashboard & API), and simplify regulatory compliance-particularly regarding BCEAO requirements.
</Update>

<Update label="November 7, 2025" tags={["New","Improvement"]}>
  **Introduction of** <span style={{color: "#008029"}}> momo\_test</span> **in Sandbox :** The <span style={{color: "#008029"}}> momo\_test</span> mode is now the sole Mobile Money mode available in the sandbox. It replaces the former operator test environments (MOOV, MTN, etc.), which have been retired to simplify and stabilize integration testing.

  [En savoir plus](integration-api/en/sending-requests-en#mobile-money-test-numbers)
</Update>