## TL;DR

For "cURL error 28: Resolving timed out": the same advice resolved the issue for other users with webshops on slow networks. Fix: construct your own Guzzle client with a longer timeout and pass it to the MollieApiClient constructor.

```text
cURL error 28: Resolving timed out
```

## Steps

1. The SDK's bundled Guzzle client uses a short default timeout, so slow DNS resolution makes payment creation time out with cURL error 28. Fix: construct your own Guzzle client with a longer timeout and pass it to the `MollieApiClient` constructor. Something like `new Client(['timeout' => 60])` injected at construction works. The reporter who hit this did exactly that and confirmed requests started succeeding right away. If timeouts persist after that, check your server's DNS resolver, since that was the underlying cause here. Source: https://github.com/mollie/mollie-api-php/issues/492

## When to use

You are seeing this: Users of mollie-api-php v2 hit cURL error 28: Resolving timed out on payment creation, even though Mollie reported no availability issues. Use this skill when you run into "Mollie API calls time out with cURL error 28 in the PHP client".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/mollie/mollie-api-php/issues/492