Mollie.Api .NET Client Library

The Mollie.Api.AspNet package provides built-in attributes to automatically parse and validate incoming webhooks (supporting both Classic and Next-gen beta systems). Use the [FromMollieWebhook] attribute on your controller action parameters and the [ServiceFilter(typeof(MollieSignatureFilter))] attribute to ensure the request is authentic.

[HttpPost("full/specific")]
[ServiceFilter(typeof(MollieSignatureFilter))]
public Task<ActionResult> WebhookWithSpecificType([FromMollieWebhook] FullWebhookEventResponse<PaymentLinkResponse> data) {
    return Task.FromResult<ActionResult>(Ok());
}

To use Open Iconic with Foundation, include the Foundation-specific stylesheet and use the fi- class prefix followed by the icon name.

<link href="/open-iconic/font/css/open-iconic-foundation.css" rel="stylesheet">
<span class="fi-icon-name" title="icon name" aria-hidden="true"></span>

To use Open Iconic with Bootstrap, include the Bootstrap-specific stylesheet and use the oi class prefix followed by the icon name.

<link href="/open-iconic/font/css/open-iconic-bootstrap.css" rel="stylesheet">
<span class="oi oi-icon-name" title="icon name" aria-hidden="true"></span>

To use the default Open Iconic stylesheets without Bootstrap or Foundation, include the standard stylesheet and use the oi class with the data-glyph attribute.

<link href="/open-iconic/font/css/open-iconic.css" rel="stylesheet">
<span class="oi" data-glyph="icon-name" title="icon name" aria-hidden="true"></span>

To integrate the Mollie payment provider into your .NET application, install the core library via NuGet.

Install-Package Mollie.Api

If you are not using Dependency Injection, you can manually create a client instance. It is recommended to provide your own HttpClient instance. If you do not provide one, the client will create one automatically, in which case you must ensure the client is properly disposed.

using IPaymentClient paymentClient = new PaymentClient("{yourApiKey}", new HttpClient());

The SVG sprite allows you to load all icons in a single request. To use it, reference the sprite file and the specific icon ID within a <use> tag.

Styling Tips:

• Add a general class to the <svg> tag for shared properties.
• Add a unique class to the <use> tag for icon-specific styling (like color).
• To size icons, set equal width and height on the <svg> tag.
• To color icons, use the CSS fill property on the <use> tag.

<svg class="icon">
  <use xlink:href="open-iconic.svg#account-login" class="icon-account-login"></use>
</svg>

You can display icons as standard SVG images. When using this method, ensure you include an alt attribute for accessibility.

<img src="/open-iconic/svg/icon-name.svg" alt="icon name">

You can register all API client interfaces using the built-in DI extension. This allows you to inject specific clients like IPaymentClient, ICustomerClient, or ISubscriptionClient into your services or controllers. You can also configure a RetryPolicy using MollieHttpRetryPolicies.

builder.Services.AddMollieApi(options => {
    options.ApiKey = builder.Configuration["Mollie:ApiKey"];
    options.RetryPolicy = MollieHttpRetryPolicies.TransientHttpErrorRetryPolicy();
});

To create a payment, instantiate a PaymentRequest with the required details (Amount, Description, RedirectUrl, and Method) and call CreatePaymentAsync on the IPaymentClient. The response contains the checkout URL used to redirect the user.

using IPaymentClient paymentClient = new PaymentClient("{yourApiKey}", new HttpClient());

var paymentRequest = new PaymentRequest {
    Amount = new Amount(Currency.EUR, 100.00m),
    Description = "The .NET library makes creating payments so easy!",
    RedirectUrl = "https://github.com/Viincenttt/MollieApi",
    Method = PaymentMethod.Ideal
};

PaymentResponse paymentResponse = await paymentClient.CreatePaymentAsync(paymentRequest);
// Redirect your user to the checkout URL
string checkoutUrl = paymentResponse.Links.Checkout.Href;

The library provides coverage for a wide range of Mollie APIs. Note that some APIs are currently marked as 'documentation coming soon'.

- Payment API
- PaymentMethod API
- PaymentLink API
- Customer API
- Mandate API
- Subscription API
- Refund API
- Connect API
- Chargeback API (documentation coming soon)
- Invoice API (documentation coming soon)
- Permissions API (documentation coming soon)
- Profile API
- Organizations API
- Order API
- Capture API
- Onboarding API
- ClientLink API (documentation coming soon)
- Wallet API (documentation coming soon)
- Client API (documentation coming soon)
- Capability API (documentation coming soon)
- Terminal API (documentation coming soon)
- Webhooks API
- WebhooksEvents API
- Balance transfer API
- Payout API
- Balances API
- Order API