Different response when hitting curl command with & without single quotes
Without quotes, the & will cause everything before it to run in the background. Effectively making your command be:
curl -L -H 'Authorization: Bearer MY_TOKEN' -X GET https://api.admitad.com/payments/?limit=2
Followed by executing has_statement=0 as a separate (but valid) command.
With the quotes the & is escaped and the intended command is sent. Which apparently fails when it has the &has_statement=0 part. This is supported by the fact it fails with postman also.