New endpoint for The TWINT PayIn object:
New endpoint for The Swish PayIn object:
New endpoints for The Virtual Account object:
- Create a Virtual Account
- Deactivate a Virtual Account
- View a Virtual Account
- List Virtual Accounts for a Wallet
- View Client Availabilities
- Updated
RedirectURLfor the Payconiq PayIn
- New endpoint: Create a Bancontact PayIn
- Updated tests for Look up metadata for a payment method.
- Add trace header logging : Introduced the
log_trace_headersboolean configuration key. Set it to true to enable logging ofx_mangopay_trace-idandIdempotencyKeyin the log of the http requests.
- #249 Improve error handling when logging is enabled
- #226 MultiJson::ParseError is thrown on HTTP error 5XX
- New endpoint Add tracking to Paypal payin
- Conversions endpoint spelling
- 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
uk_header_flagboolean configuration key. Platforms partnered with Mangopay's UK entity should set this key to true for proper configuration.
- New endpoint to look up metadata from BIN or Google Pay token. More information here
- The endpoint View a card Validation is now available
Now, our SDK enables seamless integration with multiple clientIDs, offering enhanced flexibility and customization.
You can effortlessly create multiple configuration objects tailored to your specific needs:
config = MangoPay::Configuration.new
config.client_id = 'your-client-id'
config.client_apiKey = 'your-api-key'
config.preproduction = true
add them using :
MangoPay.add_config('config1', config)
and perform a call with them using :
MangoPay.get_config('config1').apply_configuration
The previous method configure() is still working.
- Giropay and Ideal integrations with Mangopay have been improved.
- Klarna param "MerchantOrderId" has been renamed to "Reference"
- Instantly convert funds between 2 wallets of different currencies owned by the same user with the new SPOT FX endpoints
- A new parameter for Paypal : ShippingPreference
- Klarna is now available as a payment method with Mangopay. This payment method is in private beta. Please contact support if you have any questions.
- #225 It's now possible to configure ssl_options. It's now possible to set to false in preproduction environment. Thanks to @mantaskujalis
- Card validation endpoint management (Private beta)
- New MOPs added : Multibanco, Blik, Satispay (Private beta)
- Execution Type of MB Way and PayPal has been changed from Direct to Web
- Google Pay is now available as a payment method with Mangopay. This payment method is in private beta. Please contact support if you have any questions.
- Paypal integration with Mangopay has been improved. This payment method is in private beta. Please contact support if you have any questions.
Phoneparameter instead ofPhoneNumberfor MBWay- Timeout should be in secondes instead of milliseconds in the configuration
- 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.
- fixed GitHub Actions CD pipeline
- typo fixed in test context name (@batistadasilva)
- Possibility to configure HTTP
max_retries (http_max_retries)(default value = 1) andopen_timeout (http_open_timeout)(default value = 60 seconds) - Increased default
read_timeoutto 30 seconds
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 Deposit service has been added with methods for creating, fetching and canceling a deposit
- The create_pre_authorized_deposit_pay_in 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.
Tests has been fixed due to API evolution.
##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.
##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.
With the function
PayOut::InstantPayoutEligibility::Reachability.create(params)
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.
You can now change the status to "ENDED" for a recurring payment.
- "Status" is now available in the response when you request a recurring payment registration.
As requested by numerous clients, we are now providing Payconiq as a new mean-of-payment. To request access, please contact MANGOPAY.
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->KycDocuments->Get($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.
Idempotency key is not required anymore for UBO declarations
- 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
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.
- Add support for refund creation
- Allow to fetch UBO Declaration without User ID
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 Ruby SDK.
Example :
bankwire = MangoPay::PayOut::BankWire.get_bankwire(payout['Id'])
# where payout['Id'] is the id of an existing payoutPlease note that this feature must be authorized and activated by MANGOPAY. More information here.
- Add support to create refunds for PayIn, Transfer and PayOut transactions.
- ResponseError object improvement
More information about how to test payments, click here.
- Adding missing json require in log requests filter spec. Thank you @Vin0uz
- Extend fetch_wallet and create_payout API. Thank you @peterb
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.
This on-demand feature is for testing purposes only and will not be available in production
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:
V1V2_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
In the API response, the Requested3DSVersion will show the value you requested:
V1V2_1null– indicates that nothing was requested
The parameter Applied3DSVersion shows you the version of the 3DS protocol used. Two values are possible:
V1V2_1
- 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
- Add test on new payout mode PayoutModeRequested
- Card Validation endpoint fully activated
- added pre authorizations transactions method
- added new methods for client bank accounts and payouts
- Send headers for different api calls
- Forces TLS version to 1.2
- Improvement to Net::ReadTimeout handling
- "User-agent" format in the headers changed, aligned to other assets 👤
- This SDK is now GooglePay-ready ! Feel free to ask our lovely support for more infos about its activation.
UBODeclarationis now directly available through its ID.- If a bankwire is done from a UK bankaccount on one of your
BankingAlias, you could find itsAccountNumberonGET /payins/response - You can now send a
Cultureparameter for Paypal PayIns. Thanks to it, payment page can be displayed in various languages.
PAYLINEV2value for Payin Web has been added onTemplateURLOptionsobject. You now should use it instead ofPAYLINEfor page customization.
- Missing filters parameters have been added
- You can now send headers in update requests
- Loggers have been enhanced
- ApplePay
Payinfunctions are now available. More info about activation to come in the following weeks...
- GET EMoney method now supports year and month parameters. More info on our docs
- New UBO Declaration system (more info here)
- Paypal buyer account email that has been used is now available for Payin Paypal
- Your
HeadquartersPhoneNumbercan now be updated for your client account directly from our API
APIKeyis now replacingpassphraseproperty for credentials. You must update it by updating to 3.0.32 SDK version and upper ones.