Mollie API client for PHP

Accepting iDEAL, Apple Pay, Bancontact, SOFORT Banking, Creditcard, SEPA Bank transfer, SEPA Direct debit, PayPal, Belfius Direct Net, KBC/CBC, paysafecard, ING Home'Pay, Giropay, EPS, Przelewy24, Postepay, In3, Klarna (Pay now, Pay later, Slice it, Pay in 3), Giftcard and Voucher online payments without fixed monthly costs or any punishing registration procedures. Just use the Mollie API to receive payments directly on your website or easily refund transactions to your customers.

Requirements

To use the Mollie API client, the following things are required:

• Get yourself a free Mollie account. No sign up costs.
• Now you're ready to use the Mollie API client in test mode.
• Follow a few steps to enable payment methods in live mode, and let us handle the rest.
• PHP >= 7.0
• Up-to-date OpenSSL (or other SSL/TLS toolkit)

For leveraging Mollie Connect (advanced use cases only), we recommend also installing our OAuth2 client.

Installation

Using Composer

The easiest way to install the Mollie API client is by using Composer. You can require it with the following command:

To work with the most recent API version, ensure that you are using a version of this API client that is equal to or greater than 2.0.0. If you prefer to continue using the v1 API, make sure your client version is below 2.0.0. For guidance on transitioning from v1 to v2, please refer to the migration notes.

Manual Installation

If you're not familiar with using composer we've added a ZIP file to the releases containing the API client and all the packages normally installed by composer. Download the mollie-api-php.zip from the releases page.

Include the vendor/autoload.php as shown in Initialize example.

Usage

Initializing the Mollie API client, and setting your API key.

With the MollieApiClient you can now access any of the following endpoints by selecting them as a property of the client:

Find our full documentation online on docs.mollie.com.

Orders

Creating Orders

Create Order reference

After creation, the order id is available in the $order->id property. You should store this id with your order.

After storing the order id you can send the customer off to complete the order payment using $order->getCheckoutUrl().

This header location should always be a GET, thus we enforce 303 http response code

For an order create example, see Example - New Order.

Updating Orders

Update Order Documentation

Refunding Orders

Complete

Partially

When executing a partial refund you have to list all order line items that should be refunded.

Cancel Orders

Cancel Order Documentation

When canceling an order it is crucial to check if the order is cancelable before executing the cancel action. For more information see the possible order statuses.

Order webhook

When the order status changes, the webhookUrl you specified during order creation will be called. You can use the id from the POST parameters to check the status and take appropriate actions. For more details, refer to Example - Webhook.

Payments

Payment Reception Process

Payment Reception Process documentation

To ensure a successful payment reception, you should follow these steps:

1. Utilize the Mollie API client to initiate a payment. Specify the desired amount, currency, description, and optionally, a payment method. It's crucial to define a unique redirect URL where the customer should be directed after completing the payment.

2. Immediately upon payment completion, our platform will initiate an asynchronous request to the configured webhook. This enables you to retrieve payment details, ensuring you know precisely when to commence processing the customer's order.

3. The customer is redirected to the URL from step (1) and should be pleased to find that the order has been paid and is now in the processing stage.

Creating Payments

Create Payment Documentation

After creation, the payment id is available in the $payment->id property. You should store this id with your order.

After storing the payment id you can send the customer to the checkout using $payment->getCheckoutUrl().

This header location should always be a GET, thus we enforce 303 http response code

For a payment create example, see Example - New Payment.

Multicurrency

Since API v2.0 it is now possible to create non-EUR payments for your customers. A full list of available currencies can be found in our documentation.

After creation, the settlementAmount will contain the EUR amount that will be settled on your account.

Create fully integrated iDEAL payments

To fully integrate iDEAL payments on your website, follow these additional steps:

1. Retrieve the list of issuers (banks) that support iDEAL.

Use the $method->issuers list to let the customer pick their preferred issuer.

$method->issuers will be a list of objects. Use the property $id of this object in the API call, and the property $name for displaying the issuer to your customer.

2. Create a payment with the selected issuer:

_The _links property of the $payment object will contain an object checkout with a href property, which is a URL that points directly to the online banking environment of the selected issuer. A short way of retrieving this URL can be achieved by using the $payment->getCheckoutUrl()._

For a more in-depth example, see Example - iDEAL payment.

Retrieving Payments

Retrieve Payment Documentation

We can use the $payment->id to retrieve a payment and check if the payment isPaid.

Or retrieve a collection of payments.

For an extensive example of listing payments with the details and status, see Example - List Payments.

Refunding payments

Refund Payment Documentation

Our API provides support for refunding payments. It's important to note that there is no confirmation step, and all refunds are immediate and final. Refunds are available for all payment methods except for paysafecard and gift cards.

Payment webhook

When the payment status changes, the webhookUrl you specified during payment creation will be called. You can use the id from the POST parameters to check the status and take appropriate actions. For more details, refer to Example - Webhook.

For a working example, see Example - Refund payment.

Enabling debug mode

When troubleshooting, it can be highly beneficial to have access to the submitted request within the ApiException. To safeguard against inadvertently exposing sensitive request data in your local application logs, the debugging feature is initially turned off.

To enable debugging and inspect the request:

If you are recording instances of ApiException, the request details will be included in the logs. It is vital to ensure that no sensitive information is retained within these logs and to perform cleanup after debugging is complete.

To disable debugging again:

Please note that debugging is only available when using the default Guzzle http adapter (Guzzle6And7MollieHttpAdapter).

API documentation

For an in-depth understanding of our API, please explore the Mollie Developer Portal. Our API documentation is available in English.

Contributing to Our API Client

Would you like to contribute to improving our API client? We welcome pull requests. But, if you're interested in contributing to a technology-focused organization, Mollie is actively recruiting developers and system engineers. Discover our current job openings or reach out.

License

BSD (Berkeley Software Distribution) License. Copyright (c) 2013-2018, Mollie B.V.

Support

Contact: www.mollie.com — [email protected] — +31 20 820 20 70