3.6.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.

New country authorization hook

Country authorization updates can now be received by setting up a hook for the following EventType: COUNTRY_AUTHORIZATION_UPDATED

With this hook, it is possible to be notified when a country’s restrictions are updated.

3.5.0

Added

• It's now possible to fetch a Payconiq payin by ID

3.4.2

Fixed

• Bug with idempotency parameters with some GET requests (Disputes, Repudiations...)

3.4.1

Fixed

Missing EventType have been added (RECURRING_REGISTRATION).

3.4.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.

3.3.1

Fixed

The SDK handles existingUser without an UserCategory

3.3.0

Added

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.

3.2.0

Added

Terms and conditions acceptance parameter

The acceptance of the MANGOPAY terms and conditions by the end user can now be registered via the SDK.

This information can be managed by using the new TermsAndConditionsAccepted parameter added to the User object.

The following API endpoints have been updated to take into account the new TermsAndConditionsAccepted parameter:

Create a Natural User
Update a Natural User
Create a Legal User
Update a Legal User
View a User

Please note that:

• Existing users have to be updated to include the terms and conditions acceptance information.
• Once accepted, the terms and conditions cannot be revoked.

3.1.0

Changed

Updated libraries

The SDK relies on .Net 6.0. You should update your project and librairies accordingly.
If you use a lower/older version, we will not be able to provide any support.

3.0.0

The .Net SDK has been revamped in order to increase performances and improve the developer experience.

Changed

Updated libraries

The SDK relies on .Net 5.0. You should update your project and librairies accordingly.
If you use a lower/older version, we will not be able to provide any support.

Functions include idempotency management

Previously, if you wish to use idempotency, you had to use a dedicated function for idempotency. These functions have been removed.
Now, each regular function can use idempotency, thanks to a new parameter.

For example :

await this.Api.PayIns.CreateRefundAsync(payIn.Id, refund, idempotentKey: idempotencyKey);

Requests efficiency

We have improved our request management. This version uses a singleton RestClient and changes only the RestRequest at each request. Therefore, requests are faster and have less impact on your server.