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.

2.11.0

Added

Instant payment eligibility check

The destination bank reachability can now be verified prior to making an instant payout. This results in a better user experience, as this preliminary check will allow the platform to propose the instant payout option only to end users whose bank is eligible.

Instant payment mode only

Instant Payment requests can now be automatically cancelled when an issue is encountered (rather than falling back to the standard payout mode).

This is possible by using the new INSTANT_PAYMENT_ONLY option that has been added to the PayoutModeRequested parameter.

Fixed

• RefundReasonType is now a string

2.10.0

Added

We are now providing new hooks for our new feature Instant payouts :

• INSTANT_PAYOUT_SUCCEEDED
• INSTANT_PAYOUT_FALLBACKED

It will allow you to trigger an action depends on the Instant Payout treatment.

2.9.0

Added

You can now change the status to "ENDED" for a recurring payment.

Fixed

• "Status" is now available in the response when you request a recurring payment registration.

2.8.0

Added

Payconiq

As requested by numerous clients, we are now providing Payconiq as a new mean-of-payment. To request access, please contact MANGOPAY.

Flags for KYC documents

We provide more information regarding refused KYC documents. Therefore it will be easier for you to adapt your app behavior and help your end user.

You are now able to see the exact explanation thanks to a new parameter called “Flags”.

It has been added to

this.Api.Kyc.GetAsync(kycDocument.Id);

It will display one or several error codes that provide the reason(s) why your document validation has failed. These error codes description are available here.