Skip to main content

Using Security and Collateral

Updated over a week ago

At Cloudfloat, protecting both our customers and our platform is a priority. In some cases, we may require security or collateral to support a transaction or facility. This helps us manage risk responsibly while continuing to offer fast, flexible access to funds.

This article explains what security and collateral mean, when they may be required, and how they are used at Cloudfloat.

What is Security or Collateral?

Security (or collateral) is an asset, guarantee, or financial commitment provided to support a payment advance or facility. It helps ensure obligations are met and reduces risk for all parties involved.

Requiring security does not reflect negatively on a customer. It is a common and prudent measure used across financial services.

At Cloudfloat, security arrangements are always:

  • Proportionate to the level of risk

  • Clearly explained

  • Agreed to before funding is released

When Might Cloudfloat Require Security?

Security may be required where there is limited historical data or increased exposure. Common scenarios include:

  • New customers with limited transaction or settlement history

  • Larger funding amounts relative to past activity

  • Increased funding frequency or changes in usage patterns

  • Irregular or delayed settlement cycles

  • Manual payout requests or account linking limitations

  • Compliance or verification requirements

Each request is assessed individually, using a combination of automated checks and manual review.

Types of Security Cloudfloat May Use

Depending on the situation, security may include:

Guarantees

In some cases, a personal or business guarantee may be required to support higher limits or ongoing facilities.

Verification Documentation

This may include confirmation of bank account details, identity verification, or supporting financial documentation.

Other Agreed Safeguards

For certain facilities, additional safeguards may be agreed to based on the specific risk profile.

Cloudfloat does not take ownership of customer assets, and we do not impose security conditions beyond what is explicitly agreed.

Transparency and Customer Communication

Cloudfloat is committed to clear, open communication. We will always:

  • Explain why security is required

  • Clearly define what is being secured

  • Confirm how long the security applies

  • Provide access to support throughout the process

There are no hidden terms, surprise conditions, or retroactive changes.

How Security Benefits Customers

While security helps manage risk, it also enables Cloudfloat to:

  • Offer faster access to funds

  • Support higher funding limits

  • Reduce fraud and misuse

  • Maintain platform stability and availability

  • Deliver consistent service across customers

This ensures Cloudfloat remains reliable and sustainable for all users.

Did this answer your question?