3.15.0

Added

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

Fixed

• BillingField & ShippingField are now optionals for RecurringPayIn
• We have fixed DateTimeField (previously was generating an error due to format)

3.14.1

Fixed

• Change FallbackReason parameter's type to object in BankWirePayOut

3.14.0

Added

• 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

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

3.11.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 Python SDK. You can now verify the mode applied to an instant payment.

get_bank_wire = BankWirePayOut.get_bankwire(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.

Fixed

Duplicate BIC in resources

3.10.1

Fixed

Fixed

IBAN for testing purposes

⚠️ 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.

Others

• httplib2 has been updated to the last version
• RemainingFunds was flag wrongly as mandatory for PreAuthorization. It has been fixed.
• ProcessedDate had the type IntegerField instead of DateTimeField. It has been fixed.

Added

New events for PreAuthorization

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.

Logging

We have merged @rbarrois pull request. The logging module expects user to provide the string as a first argument, and all interpolation parameters in separate positional or keyword arguments: logger.debug("trying x=%s", x).

This brings two benefits:

• The interpolation is only performed if the logging message is actually
  used (debug messages won't even be interpolated if logging is set to
  WARNING)

• Monitoring libraries like Sentry can group messages based on their
  non-interpolated message, which helps detecting similar issues.

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

3.9.0

Added

• 3DS2 integration with Shipping and Billing objects, including FirstName and LastName fields
  The objects Billing and Shipping may be included on all calls to the following endpoints:
  • /preauthorizations/card/direct
  • /payins/card/direct
  • /payins/card/web
• Enable Instant Payment for payouts by adding a new parameter PayoutModeRequested on the following endpoint /payouts/bankwire
  • The new parameter PayoutModeRequested can take two differents values : "INSTANT_PAYMENT" or "STANDARD" (STANDARD = the way we procede normaly a payout request)
  • This new parameter is not mandatory and if empty or not present, the payout will be "STANDARD" by default
  • Instant Payment is in beta all over Europe - SEPA region

Changed

• Changed date to dateTime and fixed tests
• Changed User-Agent

3DS2 changes - Added IpAddress and BrowserInfo parameters, 'NO_CHOICE' value for the SecureMode

Update of Python SDK 3.8.5 ⬆️

Added IpAddress and BrowserInfo parameters to the following endpoints and corresponding objects 💳
• /payins/card/direct
• /preauthorizations/card/direct
Added 'NO_CHOICE' value for the SecureMode parameter 🧷

Regulatory endpoint and hook

Update of Python SDK 3.8.4 ⬆️

Added 'Regulatory' endpoint to allow checks of User Block Status 🚫
Added support for Regulatory -> Blocked Status Hooks 📞