2.28.0

Added

Knowing when a dispute was closed is now possible thanks to the new ClosedDate parameter for the Dispute object.

The following endpoints have been updated accordingly:

Vew a Dispute
List Disputes for a User
List Disputes for a Wallet
List all Disputes
List Disputes that need settling

Please note that the new ClosedDate field will only display values for the Disputes closed after this release. Otherwise, a null value will be returned.

2.27.2

Fixed

• #290 Missing Kosovo in CountryISO enum

2.27.1

Fixed

• Fix bug preventing access to authentication endpoint

2.27.0

Added

Verifying some specific legal structures is now more efficient thanks to a new legal entity type: PARTNERSHIP.

The Legal User LegalPersonType parameter now includes the PARTNERSHIP value. The following endpoints have been updated accordingly:

Create a Legal User (Payer)
Create a Legal User (Owner)
Update a Legal User

Please note that changing the LegalPersonType to PARTNERSHIP for an existing user will automatically result in:

• A KYC downgrade to Light (default) verification
• The REGISTRATION_PROOF document being flagged as OUT_OF_DATE.

With this new LegalPersonType, the MANGOPAY team can better handle specific legal structures and speed up the validation process.

2.26.0

Added

New 30-day preauthorization feature

Preauthorizations can now hold funds for up to 30 days, therefore ensuring the solvency of a registered card for the same amount of time.

• The DepositApi service has been added with methods for creating, fetching and canceling a deposit
• The Deposit entity has been created
• The createCardPreAuthorizedDepositPayIn method has been added to the PayIn service

Thanks to 30-day preauthorizations, MANGOPAY can provide a simpler and more flexible payment experience for a wide range of use cases, especially for rentals.

New behavior when MANGOPAY API is down

• Instead of NPE when the API is down, a custom Exception has been added

2.25.2

Fixed

Tests have been fixed due to API evolution.

2.25.1

Fixed

User TermsAndConditionsAccepted is now nullable

2.25.0

Added

New country authorizations endpoints

Country authorizations can now be viewed by using one of the following endpoints:

View a country's authorizations
View all countries' authorizations

With these calls, it is possible to check which countries have:

• Blocked user creation
• Blocked bank account creation
• Blocked payout creation

Please refer to the Restrictions by country article for more information.

2.24.0

Added

Recurring: €0 deadlines for CIT

Setting free recurring payment deadlines is now possible for CIT (customer-initiated transactions) with the FreeCycles parameter.

The FreeCycles parameter allows platforms to define the number of consecutive deadlines that will be free. The following endpoints have been updated to take into account this new parameter:

Create a Recurring PayIn Registration
View a Recurring PayIn Registration
This feature provides new automation capabilities for platforms with offers such as “Get the first month free” or “free trial” subscriptions.

Please refer to the Recurring payments overview documentation for more information.

2.23.0

Added

UserCategory management

Users can now be differentiated depending on their MANGOPAY usage.

This is possible with the new UserCategory parameter, whose value can be set to:

• Payer – For users who are only using MANGOPAY to give money to other users (i.e., only pay).
• Owner – For users who are using MANGOPAY to receive funds (and who are therefore required to accept MANGOPAY’s terms and conditions).

Please note that the following parameters become required as soon as the UserCategory is set to “Owner”:

• HeadquartersAddress
• CompanyNumber (if the LegalPersonType is “Business”)
• TermsAndConditionsAccepted.

The documentation of user-related endpoints has been updated and reorganised to take into account the new parameter:

Create a Natural User (Payer)
Create a Natural User (Owner)
Update a Natural User
Create a Legal User (Payer)
Create a Legal User (Owner)
Update a Legal User
View a User
List all Users

Differentiating the platform users results in a smoother user experience for “Payers” as they will have less declarative data to provide.