Trust, evidenced

BINK is built for regulation and monitored continuously in-app. It is not yet licensed or certified, and is preparing for UK e-money registration. Every claim on this page is read from a policy you can open in full.

Compliance policy v2.0 · effective 1 September 2026

Why enterprises trust BINK

Five reasons, each with a document behind it

The claim and the document are the same object

100%

Of facts on this page read from a policy you can open

Every control, cycle and entity on this page is read directly out of the approved policy at build time. There is no second copy to fall out of date, and no marketing edit that can quietly widen a scope. If the policy changes, this page changes with it; if it does not, this page cannot.

Not yet licensed, and saying so

BINK holds no licence, authorisation or registration in any market and is preparing for UK e-money registration. Regulated services will be provided through licensed partners.

Oversight that does not report to sales

A dedicated compliance function operates independently of commercial teams and reports to the board. Policies are reviewed annually, and each control has a named owner and a testing schedule.

Not yet independently audited

BINK holds no PCI DSS, ISO 27001 or SOC 2 certification, and no external or independent audit has taken place yet. Every privileged action is recorded in BINK’s own internal audit log.

Partners are assessed, not assumed

Every partner and processor will be assessed before onboarding and reviewed annually, covering regulatory standing, security posture, resilience and data protection.

The protection journey

What happens around a single payment

Controls are easier to trust when you can see where each one sits. This is the same payment, from the moment an account is opened to the moment an incident is closed.

Before the account opens

Identity verified

We verify identity before an account is opened, understand the expected purpose and volume of activity, and refresh due diligence on a risk-based schedule. Enhanced diligence applies to higher-risk relationships.

Before you sign in

Phishing-resistant authentication

Passkeys and hardware security keys are supported on every account, with one-time codes for step-up verification and new devices confirmed before first use.

As the payment is made

Screened in real time

Customers, counterparties and payments are screened against applicable sanctions lists in real time. Matches are held for review, and confirmed matches are reported and blocked.

In flight

Encrypted end to end

Traffic is encrypted with TLS 1.3. Stored data is encrypted with AES-256 and keys are managed in hardware security modules with split control. Card data will be tokenised and handled by licensed card partners.

Continuously

Monitored for the unusual

Sessions, devices and payments are scored continuously. Unusual patterns trigger step-up verification, a temporary hold, or review by our fraud team, and alerts are investigated by trained analysts.

If something is wrong

Contained, then disclosed

Detection and triage on call at all times, affected sessions or accounts isolated, and notification to affected customers and any relevant authorities as required.

Afterwards

Reported and reviewed

Suspicious activity is reported to the relevant financial intelligence unit, and a post-incident review is published in summary where material.

Jurisdictions

Where the group has companies

BINK is a group of companies. The entity named in your account agreement is the one you contract with. None of them is licensed yet.

EgyptUnited Arab EmiratesUnited Kingdom
EgyptGroup company

BINK PAY

United Arab EmiratesGroup company

BINKPAY FINANCING BROKER L.L.C

United KingdomGroup company

BINK PAY LTD

Group entities and BINK’s licensing status are stated in Regulatory status — version 3.0. BINK is not yet licensed in any of these markets.

Operational security

How production is actually run

BINK holds no certifications yet. These are the day-to-day controls its software and team run, quoted from the Security policy.

Isolated productionLeast-privilege access, mandatory review on every change, immutable deployments.
Time-bound accessAccess to production data requires approval and expires.
Trained annuallyAll staff complete financial crime, security and data protection training at onboarding and annually.
Protected escalationEscalation routes are confidential and protected.
Change managementStandard

Peer review and automated checks

AccessStandard

Least privilege, time-bound, logged

BackupsStandard

Encrypted, tested quarterly

RecoveryStandard

RPO 15 minutes · RTO 4 hours

TLS 1.3

Traffic encrypted in transit

AES-256

Data at rest, keys split across hardware modules

In-app

Sessions, devices and payments scored by BINK’s own software

1 business day

Vulnerability reports acknowledged

Questions

What diligence teams ask first

Can I see your attestation reports?

There are none yet. BINK holds no PCI DSS, ISO 27001 or SOC 2 certification and has not been externally audited. The compliance team can answer diligence questionnaires.

Which entity am I actually contracting with?

The entity named in your account agreement. BINK is a group of companies and is not yet licensed in any market; regulated services will be provided through licensed partners.

What happens to my money if BINK fails?

No partner rails are live yet, and no customer funds are held or safeguarded by anyone. When live, customer funds will be held in segregated accounts at licensed partners, separate from BINK’s own funds. They will not be bank deposits, so deposit guarantee schemes will not cover them.

How often is the platform tested?

No external penetration test or audit has taken place yet, and BINK holds no PCI DSS, SOC 2 or ISO 27001 certification. Controls run inside BINK’s own software, as described on this page.

Will you ask me for my password or one-time code?

Never. BINK will never ask for your password, one-time code or passkey over the phone, by email or in chat. If someone does, it is not us.

What do you do when a regulator asks for data?

We respond to lawful requests from regulators and law enforcement, disclosing only what is required and notifying affected customers where legally permitted.

How do I report a vulnerability?

Through the security channel in the application, or to security@binkpay.net. We acknowledge within one business day and will not pursue action against good-faith research, provided testing does not access other customers’ data, degrade service, or use social engineering.

Boundaries

What BINK is not

Knowing what a financial platform does not do is part of deciding whether to trust it. Each line below is stated in the licensing or privacy policy.

We do not take deposits. BINK is not a bank and is not yet licensed to issue electronic money.

Not covered by deposit guarantee schemes. When live, customer funds will be held in segregated accounts at licensed partners instead.

We do not provide investment advice. Nothing in the product is a recommendation to buy or sell.

We never sell customer data. Data is shared only where there is a lawful basis to do so.

Related

Everything this page is read from

Reviewing BINK for your business?

Our compliance team answers diligence questionnaires. There are no attestation reports yet: BINK is not certified and has not been externally audited.