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.

2.7.1

Fixed

• Change FallbackReason parameter's type to object in PayOutBankWireDTO

2.7.0

• You can now update and view a Recurring PayIn Registration object. To know more about this feature, please consult the documentation here.
• To improve recurring payments, we have added new parameters for CIT : DebitedFunds & Fees. To know more about this feature, please consult the documentation here

2.6.0

Added

We have added a new feature recurring payments dedicated to clients needing to charge a card repeatedly, such as subscriptions or payments installments.

You can start testing in sandbox, to help you define your workflow. This release provides the first elements of the full feature.

• Create a Recurring PayIn Registration object, containing all the information to define the recurring payment
• Initiate your recurring payment flow with an authenticated transaction (CIT) using the Card Recurring PayIn endpoint
• Continue your recurring payment flow with an non-authenticated transaction (MIT) using the Card Recurring PayIn endpoint

This feature is not yet available in production and you need to contact the Support team to request access.

2.5.0

Added

Mangopay has introduced few months ago the instant payment mode. It allows payouts (transfer from wallet to user bank account) to be processed within 25 seconds, rather than the 48 hours for a standard payout.

We have added a new feature in the .Net SDK. You can now verify the mode applied to an instant payment.

var getJohnBankwire = awaitApi.PayOuts.GetBankwirePayoutAsync(payOut.Id);
// where payOut.Id is the id of an existing payout

Please note that this feature must be authorized and activated by MANGOPAY. More information here.

2.4.0

Fixed

⚠️ IBAN provided for testing purpose should never be used outside of a testing environement!

• Fix BankAccount IBAN reference for tests

More information about how to test payments, click here.

Added

Some of you use a lot the PreAuthorization feature of our API. To make your life easier, we have added three new events :

• PREAUTHORIZATION_CREATED
• PREAUTHORIZATION_SUCCEEDED
• PREAUTHORIZATION_FAILED

The goal is to help you monitor a PreAuthorization with a webhook.

Example: If a PreAuthorization is desynchronized, when the status is updated, you will be able to know it.

2.3.0

Added

On demand feature for 3DSv2

This on-demand feature is for testing purposes only and will not be available in production

Request

We've added a new parameter Requested3DSVersion (not mandatory) that allows you to choose between versions of 3DS protocols (managed by the parameter SecureMode). Two values are available:

• V1
• V2_1

If nothing is sent, the flow will be 3DS V1.

The Requested3DSVersion may be included on all calls to the following endpoints:

• /preauthorizations/card/direct
• /payins/card/direct

Response

In the API response, the Requested3DSVersion will show the value you requested:

• V1
• V2_1
• null – indicates that nothing was requested

The parameter Applied3DSVersion shows you the version of the 3DS protocol used. Two values are possible:

• V1
• V2_1