Introducing two new payment methods: EPS and Giropay

Introducing two new payment methods: EPS and Giropay

Today we are announcing the addition of two new payment methods to the Mollie product portfolio: EPS and Giropay. These payment methods will empower our merchants to grow in the German and Austrian market by enabling their customers to pay in a payment method they are familiar with.

EPS and Giropay are available through our clever yet simple API, built for both easy integration and handling high transaction volumes.

Grow your business in Austria

The Electronic Payment Standard (EPS) is a payment method developed by various Austrian banks. This makes EPS the main bank transfer payment method in Austria and highly popular with Austrian shoppers. With Mollie you can integrate EPS quickly and start processing payments right away. You only pay for successful transactions and there are no hidden fees involved.

Offer Giropay payments to your German clients

Giropay is a popular bank transfer payment method in Germany. It uses more than 1,500 German banks, which makes it a payment method your German customers can trust. Implementing Giropay through Mollie is easy, there’s no lengthy signup process and we have free, open-source packages and plugins available for most coding languages and e-commerce platforms to let your customers pay in the payment method of their preference.

Localize the payment experience to advance your international growth

During the last couple of months Mollie has been focusing on making the payment experience familiar and convenient for all of our merchants and their customers abroad. To fit our merchant’s needs we've introduced a Multicurrency feature that enables a flawless experience for customers with international cards. Advancing your business opportunities across borders became even easier with Mollie localized checkout, which allows your customers to shop in their native language. Ready to advance your business on the German and Austrian market? Check our support articles and see if your plugin supports EPS and Giropay.

Improve your international experience by localizing your checkout

Improve your international experience by localizing your checkout

As businesses grow internationally and acquire more foreign customers, it’s important to adjust accordingly. After all, international customers have different needs and expectations. To advance international opportunities we are now offering the option to localize your checkout.

Mollie adds Multicurrency, to advance international growth

Mollie adds Multicurrency, to advance international growth

Over the years we have been happy to continuously welcome new customers and be a part of their growing businesses. Seeing our merchants grow made us realize that, at some point, growing means internationalizing. To catalyze this internationalization we are introducing Multicurrency. A new feature, providing our customers the opportunity to grow wherever they want.

National Holiday Belgium

Because of the Belgium National Holiday all banks will be closed on Wednesday November 1st. Settlements can be created and send, but they won't be transferred to your bank account. The transfers will be done on Thursday.

Mollie launches gift cards

Today, we’re announcing the addition of a new payment method to Mollie’s products: gift cards. Starting today, all merchants who have an agreement with one or more of the supported gift card brands, can accept online gift card payments through Mollie.

Mollie currently supports the most used Dutch gift card brands: Nationale EntertainmentCard, Webshop Giftcard, Podium Cadeaukaart, VVV Giftcard and YourGift. If you are a licensed retailer for any of these issuers, integrating them into your checkout is as easy as turning on the payment method in your Dashboard Settings.

If you’re a retailer for multiple supported gift cards brands, using Mollie allows you to accept them all through a single integration.

Consumers who choose to pay for their purchases using gift cards, enter the card number and, if required, the PIN which is found on the card and might be hidden behind a scratch-off layer. Using gift cards, consumers can pay partial or full amounts. If there’s a remaining amount, another gift card of the same brand can be redeemed or any other activated payment method can be used.

As always, we only charge you for successful transactions. The cost of a successful gift card transaction is 0,25 EUR.

Not a licensed retailer yet? There’s a lot of advantages to it. The Dutch gift card industry saw a turnover of more than 2 billion EUR in 2014 And a 2015 report by the Dutch tourist office found that 41% of consumers spend more than the gift card’s worth when they redeemed it. Adding gift cards as a payment method also amplifies your reach in your specific market through exposure from the gift card issuer.

To use the gift card payment method, you’ll first need to enter into an agreement with one or more issuers. Payouts are handled by the issuers as well.

Click here for more information about the payment method.

Improvements to SEPA Bank Transfer for German consumers

Improvements to SEPA Bank Transfer for German consumers

Over the past couple of weeks, we optimised the SEPA Bank Transfer payment method for German consumers. We integrated a German IBAN, which provides improvements for both our German customers and German consumers that use this payment method. Instead of being asked to transfer funds to a foreign, in this case Dutch, bank account, they can now transfer funds to a German IBAN, which will increase trust and transaction speeds.

What do you have to do to use this German IBAN? That depends on whether you use the Mollie Checkout or use the Mollie API to generate payment details like bank account numbers and references. When using the Mollie Checkout you don’t have to do anything, our processes automatically localise the experience for your customers and use the German IBAN when relevant. If you use the Mollie API you can ensure that the German IBAN is displayed by giving the locale parameter the value de_DE when generating payments for German customers.

In 2015, we added a Belgian IBAN for Belgian consumers and noticed great improvements. We expect our customers operating in Germany will see the same.

Migrating to a new datacenter (completed)

Update: we have completed the migration to our new data center. Follow our status page to stay updated.

This change will not affect the payment services.

Somewhere in the near future, there will be a change in our network structure.

This change will mean that the webhook requests you receive, will come from new IP addresses. If you use a firewall or security plugin on your website or server, and you have whitelisted our IP addresses,  you may experience some problems . We recommend to NOT whitelist our IP addresses. The way how our API works makes this unnecessary. Whitelisting adds complexity, but no additional security.

If you still wish to whitelist our IP addresses, please add these two IP addresses to the whitelist: 87.233.229.26 and 87.233.229.27. Do not remove the existing IP addresses!
In case this information is too technical, or when you do not have access to the whitelist, please send this e-mail to your technical advisor.

Join Mollie at the PHPBenelux Conference 2017

Join Mollie at the PHPBenelux Conference 2017

Mollie has been the sponsor of the Dutch PHP Conference for two years now. We have since become active in the Belgian market as well and would like to bring ourselves to the attention of local developers. We regularly sponsor meet-ups, user groups and conferences. This allows us to do something for all those developers who have chosen Mollie or implemented our API.

We are therefore pleased to announce that we will be the sponsor of the PHPBenelux Conference 2017. The annual PHPBenelux Conference is a two-day event for PHP developers from Belgium, the Netherlands and Luxembourg. The event is held in the Antwerp Hotel Ter Elst, the 27th and 28th of January. Tickets are almost sold out, so be quick! 

Schermafbeelding-2016-12-20-om-10.50.42 (1)

Several of the members of our Development Team will attend both days of the conference. If you’re going to be there and would like to meet our developers, please come talk to us! You will recognize us from our Mollie shirts.

Vacancies at Mollie

We’re always looking for new colleagues. If you’d like to know more or meet up, get in touch for a cup of coffee at our offices. Interested in how we work? Check out our development blog!

From the development department: Migrating to PSR-2 at Mollie

From the development department: Migrating to PSR-2 at Mollie

At Mollie we use PHP for our back-end code. Over the years the source code style that we used was primarily based on personal preferences of team members from days of yore. For example, tabs were used for indentation, and certain PHP constants like true, false and null were written in uppercase, and we had our own little rules about where the opening brace { should go.

It is required for every developer to use the Mollie PHP code style. This helps in understanding each other’s code (reduce cognitive load), and prevents reformatting code to match own personal preferences (and any debates about that!).

To aid in sharing a common code style, the code style settings of our IDE PHPStorm are added to VCS with each project. Additionally, we use PHP_CodeSniffer from Squiz Labs, a PHP tool to check PHP source code using a set of predefined rules. This tool can also be integrated into PHPStorm to give real-time feedback about the source code in your editor.

Unfortunately, learning our proprietary coding standard took a lot of time for new developers and wasted many hours in code reviews, hours that could have been spent discussing code design or delivering value to our customers. For this reason, we decided to switch to a more established coding standard.

Standards

In 2012 the PHP Framework Interop Group (FIG) accepted two coding standard recommendations: PSR-1 and PSR-2. The PSR-2 recommendation defines a “coding style guide”, and it extends the PSR-1 “basic coding standard”. The FIG is “a group of established PHP projects whose goal is to talk about commonalities between our projects and find ways we can work better together.” (quote from their website)

Many libraries and frameworks are already using the PSR-2 coding style guide, and new ones are adapting it as well. That means that a lot of developers are getting used to writing code using the PSR-2 style.

As a Mollie developer, if you are reading a lot of code written in the PSR-2 coding style, you also want to write code using it. New developers would also become more quickly acquainted with the Mollie codebase. So we decided to use PSR-2 for our complete code base instead of hanging on to our own proprietary coding style. But that meant that we had to convert all existing code to adhere to the recommendations of the PSR-2 spec. And of course we wanted to do that automatically.

Tooling

A couple of tools exist to format PHP source code. PHP_CodeSniffer has the PHP Code Beautifier and Fixer (phpcbf) that can format and fix some code styles changes. Another one is PHP-CS-Fixer by Fabien Potencier. This tool can use a format specification (like PSR-1/PSR-2), but you can also specify additional individual rules to be included or excluded during the formatting. After some tests we decided to use PHP-CS-Fixer on all of Mollie’s repositories, and use phpcbf to only fix the usage of tabs in places that PHP-CS-Fixer ignores.

The most important changes were the following:

After converting the code in a project all the unit and integration tests were run to check if nothing was broken. Next the changed files were committed using a different author than the person running the converter. We did this to distinguish the commit from other regular commits:

git commit --all --author="PSR-2 Mollie <codestyle@mollie.com>" -m "Convert to PSR-2"

Comparing code from previous commits (using for instance git blame) with the newly formatted PSR-2 code would of course show a lot of differences, even if you ignore whitespace. So we investigated if it was possible to convert all code from previous commits using the git filter-branch command.

With this command you can change each commit from the project history. So then you can format all code and commit it back into VCS. The downside is that each changed commit creates a new commit SHA-1 hash, which invalidates all cloned repositories. And each changed commit ideally needs to be checked with the tests. Reformatting thousands of commits would end up quite time consuming. These two arguments helped us decide not to change any code in repository's histories.

Results

The conversion created a bit of work for all team members with older local branches. They needed to merge the tooling, then run the reformatting on their branch and then finally merge the tip of the master into their branch.

But we are very happy with the end result. A standard and well-established code style between libraries and project code help developers understand code more quicker and reduce developers' cognitive load. New developers can get up-to-speed more quickly. More time is spent on discussing code design instead of the placement of braces.

BOOKEO makes configuring Mollie easy via OAuth 2.0

Recently, BOOKEO, an online scheduling software and reservation system integrated Mollie as their preferred payment service provider for Europe. Customers of BOOKEO can now easily link their account with their merchant account at Mollie.

Screen-Shot-2016-11-28-at-11.39.42-768x841 (1)

Usually such integrations of SaaS platforms with Mollie consist of an option to use Mollie for payments and a text field for pasting your API key. However, BOOKEO implemented the integration via our OAuth 2.0 API.

Integrating your platform with Mollie via OAuth 2.0 has a number of benefits over exchanging plain API keys:

  • Merchants can link their account using the Connect with Mollie-button, there is no need to exchange API keys;
  • Privileges exchanges between Mollie and the platform are clearly visible and approved by the merchant;
  • The platform can easily switch from test- to livemode payments and can retrieve activation status from Mollie automatically;
  • Mollie can be more deeply integrated into the platform. For example, settlements can be displayed, the open balance and the next settlement date can be displayed, and any invoices from Mollie can be shown to the merchant inside your own platform;
  • Finally, OAuth 2.0 allows you to charge platform fees to the merchant through Mollie. Contact us if you would like to know more.

As you can see, integrating Mollie as a platform via OAuth 2.0 offers significant advantages. Check out our getting started guide on Mollie Connect if you would like to know more.

button-small (1)

To see how easy the integration with Mollie can be set up, you can check out the BOOKEO guide for connecting with Mollie.