Skip to content

Latest commit

 

History

History
520 lines (335 loc) · 22.6 KB

CHANGELOG.md

File metadata and controls

520 lines (335 loc) · 22.6 KB
Raw

[2.37.2] - 2024-05-24

Added

[2.37.1] - 2024-04-30

Fixed

[2.37.0] - 2024-04-02

Added

  • New endpoint Add tracking to Paypal payin
  • New parameter SecureMode for Create card validation
  • New parameters for PayPal mean of payment : CancelURL & Category (sub-parameter of LineItems). And management of PaypalPayerID, BuyerCountry, BuyerFirstname, BuyerLastname, BuyerPhone, PaypalOrderID in the response.

[2.36.0] - 2024-03-08

Fixed

  • Fixed incorrect spelling of the Subtype key in the BinData parameter.
  • Conversions endpoint spelling

Added

  • The optional Fees parameter is now available on instant conversions, allowing platforms to charge users for FX services. More information here.
  • Platforms can now use a quote to secure the rate for a conversion between two currencies for a set amount of time. More information here.
  • Introduced the isUkHeaderFlag boolean configuration key. Platforms partnered with Mangopay's UK entity should set this key to true for proper configuration.

[2.35.1] - 2024-02-16

Fixed

  • Naming of Get card validation endpoint switch to : getCardValidation()

[2.35.0] - 2024-02-06

Added

Fixed

  • setCardApi is now public in com.mangopay.MangoPayApi #316

[2.34.0] - 2023-12-22

Added

New CardInfo parameter returned on card transactions. More information here.

[2.33.0] - 2023-12-07

Added

The IDEAL legacy implementation has been enhanced. You can now pass the Bic., and if provided, the API response will include the BankName parameter. More information here.

[2.32.1] - 2023-11-09

Added

It's now possible to specify an amount for DebitedFunds and Fees when you create a refund with getPayInApi().createRefund().

[2.32.0] - 2023-11-02

Updated

  • Giropay and Ideal integrations with Mangopay have been improved.
  • Klarna param "MerchantOrderId" has been renamed to "Reference"

Added

  • New Reference parameter for the new Paypal implementation.

[2.31.0] - 2023-09-29

Added

  • Multibanco, Satispay, Blik, Klarna are now available as a payment method with Mangopay. This payment method is in private beta. Please contact support if you have any questions.
  • Card validation endpoint is now available (Private beta)
  • A new parameter for Paypal : ShippingPreference
  • Instantly convert funds between 2 wallets of different currencies owned by the same user with the new SPOT FX endpoints

Updated

  • Google Pay integration with Mangopay has been improved. This payment method is in private beta. Please contact support if you have any questions.

Fixed

  • MBWay & PayPal are now using Web Execution Type.

[2.30.0] - 2023-07-28

Added

Paypal integration with Mangopay has been improved. This payment method is in private beta. Please contact support if you have any questions.

[2.29.1] - 2023-07-07

Fixed

  • Phone parameter instead of PhoneNumber for MBWay

[2.29.0] - 2023-06-21

Added

  • MB WAY is now available as a payment method with Mangopay. This payment method is in private beta. Please contact support if you have any questions.

[2.28.0] - 2023-03-17

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] - 2023-03-03

Fixed

  • #290 Missing Kosovo in CountryISO enum

[2.27.1] - 2023-01-26

Fixed

  • Fix bug preventing access to authentication endpoint

[2.27.0] - 2023-01-12

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] - 2022-12-20

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] - 2022-10-14

Fixed

Tests have been fixed due to API evolution.

[2.25.1] - 2022-09-16

Fixed

User TermsAndConditionsAccepted is now nullable

[2.25.0] - 2022-08-17

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] - 2022-06-29

##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] - 2022.05.24

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.

[2.22.0] - 2022.05.12

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.

[2.21.0] - 2022.03.31

Added

Instant payment eligibility check

With the function PayOutEligibilityResult checkInstantPayoutEligibility(String idempotencyKey, PayOutEligibility payOutEligibility); 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.

Tag on KYC Document creation

You can now add a tag while creating a KYC Document

Fixed

  • Issues with the BankAccount deserializer and IBAN and US account number
  • missing debitedFunds and fees on class RecurringPayInMIT

[2.20.0] - 2021-11-17

Added

Instant payouts hooks

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.

GET a RecurringPayIn ID

You can now request the RecurringPayIn ID to check if the status is valid using this.api.getPayInApi().get(createdCit.getId())

[2.19.0] - 2021-10-20

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.18.0] - 2021-10-14

Fixed

  • Card deactivation
  • UBO Declaration creation
  • User-Agent in headers

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.getKycDocumentApi().getKycDocument(kycDocument.getId());

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.17.0] - 2021-08-10

Fixed

  • Better error parsing (issue #244)
  • Change FallbackReason parameter's type to object in PayOutPaymentDetailsBankWire

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

[2.16.0] - 2021-06-10

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.

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

Fixed

  • Missing "Culture" parameter in PreAuthorization

[2.15.0] - 2021-05-27

Added

Instant payment

Mangopay introduces 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.

You can now use this new type of payout with the Java SDK.

Example :

PayOut getPayOut = this.api.getPayOutApi().getBankwire(payOut.getId());
// where payOut.getId() is the id of an existing payout

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

List transactions for a mandate

The endpoint to list all transactions linked to mandate has been added to the SDK.

[2.14.0] - 2021-05-11

Fixed

IBAN for testing purposes

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

More information about how to test payments, click here.

Others

  • LegalRepresentativeBirthday primitive Long fixed. Thanks @LeComptoirDesPharmacies

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.13.0] - 2021-03-25

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

[2.12.0] - 2021-02-19

  • 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

[2.11.6] - 2020-12-09

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

[2.11.5] - 2020-09-25

  • added test to cover issue
  • added new method for PreAuthorization Transactions
  • added methods for creating client bank accounts and client payouts

[2.11.4] - 2020-09-25

  • Missing UserID added in UboDeclaration process
  • New endpoint to support changes to Card Validation process (please listen out for product announcements)
  • Testing added for added for RemainingFunds feature
  • Improved gson support and minor fixes

[2.11.3] - 2020-08-24

  • As part of KYC improvements, we are adding OUT_OF_DATE as a enum for KYC documents
  • Due to changes to the API we are no longer accepting connections with a TLS certificate of 1.1 or lower, this concerns in particular .NET frameworks 4.5 and earlier. This update applies a fix which forced the application to use TLS 1.2. (edited)
  • Fixed port settings in setBaseUrl() for use of Mock API - #206
  • ProcessedDate is now a long #170
  • Modified function to reflect payinExecutionDetailsDirect #157
  • Added binaryData as a parameter to resolve DisputeApi defect #195
  • Enabled TLS v1.2 for Java 7

[2.11.2] - 2020-08-11

  • Fixed PayInDeserializer not setting the WireReference from the JSON response.

[2.11.1] - 2020-08-10

  • New MultiCapture and RemainingFunds Parameters in Preauthorization object
  • BankingAlias Object returned now fixed, returns complete info
  • Fixed JsonNull In PayInDeserializer, thank you https://github.com/ptroc
  • "User-agent" format in the headers changed, aligned to other assets

[2.11.0] - 2020-07-10

  • USER_KYC_REGULAR has been added as a new Event. Thanks to it, you are now able to know when all the needed KYCs for a user have been validated and its KYCLevel is updated.
  • Release adds typing for EventType values KYC_OUTDATED USER_KYC_REGULAR and USER_KYC_LIGHT
  • Bug Fix -> Serializing certain address fields, filtering bank accounts

[2.10.1] - 2020-03-23

Fixed

  • Serialization issue has been fixed. ExecutionDetails property was wrongly sent on JSON request, TemplateURLOptions was not taken in account for Payin Web.

[2.10.0] - 2020-03-19

Added

  • AccountNumber property added for Payins EXTERNAL_INSTRUCTION (BankingAliases)
  • GooglePay Payin methods are now available. More info about activation to come in the following weeks...
  • EXPIRED Mandate Status and linked MANDATE_EXPIRED Event Type has been added, as this feature will be shortly supported for DirectDebit Payins. More info on our docs

Changed

  • PAYLINEparameter for PayInTemplateURLOptions will be deprecated in the following weeks for Payin Web (especiallay for Payin Cards). PAYLINEV2 parameter has been added to be used instead.

[2.9.0]

Added

  • ApplePay Payin methods are now available. More info about activation to come in the following weeks...
  • New Dispute reason type COUNTERFEIT_PRODUCT has been added.

[2.8.1] - 2019-09-09

Added

  • GetEmoney method now supports year and month parameters. More info on our docs

Fixed

  • Fix content-length issue on UBODeclaration submission
  • Migration to GSON

[2.8.0] - 2019-08-29

Added

Fixed

Travis CI integration has ben fixed and ensure fast & secure package publishing on maven.org again.