Clearhaus changelog
Clearhaus changelog

Phasing out the Resource Owner Password Credentials Grant

From today, the Resource Owner Password Credentials Grant is only available for legacy integrations.

Since the introduction of the Client Credentials Grant the Resource Owner Password Credentials Grant has been deprecated. This is the beginning of phasing it out.

Migrating away from the Resource Owner Password Credentials Grant is done by registering a client while being logged in with the email and password used to perform the Resource Owner Password Credentials Grant. Then, change your authentication request to use the Client Credentials Grant with the new Client ID and Client Secret (see Supported grants for an example).

Transaction API: Payment method support for Google Pay and Vipps

Multiple accounts support

The Record and Application resources have been updated to be consistent with support for multiple accounts in the context of a single Application.


Removal of deprecated properties and link relations will take effect from August 25, 2020.

Record Properties

  • merchant_id
  • mcc (replaced by mccs)
  • states.contract (replaced by states.contracts)
  • states.account (replaced by states.accounts)
  • currencies will be converted from a set of currencies (["DKK", "EUR"]) to an object of currency counts ({ "DKK": 1, "EUR": 2 })


Record and Application link relations

  • ch:account (replaced by ch:accounts)
  • ch:contract (replaced by ch:contracts)

See and

Transaction API: Payment method support for Samsung Pay

Application API: JSON Contract

Expand the JSON resource to achieve parity with the PDF resource.


Settlement API: Interchange and scheme fees

Add fees.interchange and fees.scheme to settlement resource.

This feature will gradually roll out from March 1st.

NB: The fees are only relevant for Interchange+ merchants.


Transaction API: RRN

Add Retrieval Reference Number to transaction resource.

This property is also supported by the transaction query language.

See and

Rate Limiting

Starting with the OAuth token endpoint on Wednesday January 15th 2020 the Merchant API will start enforcing rate limits.

The issued tokens are valid for 24 hours and it is best practice to make use of the expires_in property to take advantage of the lifetime of the token and avoid unnecessary calls to the OAuth2 token endpoint.

Given the growing interest in the Merchant API we will gradually extend rate limiting to other resources as the need arises.

See example access token response with expires_in at

Transaction API: Settlement information on authorizations

Add support for settlement information on authorizations.

The properties amount_gross and amount_net will not be utilized as they are only relevant for captures, refunds and credits.

This feature will gradually roll out from December 10th.


OAuth Client registration

Add support for creating OAuth Clients in the Developer portal.

Previously client registration was made by request via

With this new functionality the Resource Owner Password Credentials Grant becomes deprecated and existing clients can be transitioned to the Client Credentials Grant.

See and