FAQ

BinaxPay may support digital accounts, payments, cards, onboarding, and related customer services for eligible private users and businesses where available. The exact scope depends on product, jurisdiction, and provider partners, and on your approved agreement. Nothing on the public website promises that every service is available to you. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay is not a licensed bank in every jurisdiction. Services may be delivered through BinaxPay and regulated financial or payment partners depending on product and location. Public copy describes a bank-grade approach to security and compliance; it does not mean BinaxPay holds a banking licence everywhere.

BinaxPay publishes information for an international audience, but services are not offered everywhere. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Eligible individuals and businesses may apply where BinaxPay and its partners support the relevant product and jurisdiction. BinaxPay may refuse or limit access when required by law, risk policy, or provider rules. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay is designed for both private users and companies where those products are offered. Not every product is available to every customer type in every market. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay operates a public website and may offer live customer services in supported markets. Which features are live for you depends on onboarding outcome, product, provider availability, and agreement. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Depending on jurisdiction and approval, supported services may include accounts, payments, cards, statements, documents, and support channels described on the website and in your agreement. The public site does not promise the same availability for every user. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Service availability varies by country, product, provider, compliance outcome, and agreement. A feature shown on the website may not be offered in your location. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. BinaxPay works with external regulated and specialist providers for banking, payments, cards, identity verification, and other operational services where required. Partner participation may affect which products you can use. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. BinaxPay may decline applications, suspend access, or limit features for legal, compliance, risk, sanctions, provider, or contractual reasons. Such decisions are subject to applicable law and your agreement.

Use this FAQ, the Company page (Página de la empresa), Contact page, legal documents, and machine-readable public files such as /faq-ai.txt and /public-data.json. For contractual terms, refer to your agreement and published policies.

BinaxPay public services are operated in connection with BinaxPay Holding Ltd and related BinaxPay entities listed on the Company page (Página de la empresa).

BinaxPay Holding Ltd is the UK parent company shown in public company information. Official registry and contact details are published on Página de la empresa, including company number 16830503 and registered office at 167–169 Great Portland Street, 5th Floor, London, W1W 5PF.

The registered company number for BinaxPay Holding Ltd is 16830503, as shown on Página de la empresa and in public company information.

The registered office address of BinaxPay Holding Ltd is 167–169 Great Portland Street, 5th Floor, London, W1W 5PF, as published on Página de la empresa.

Yes. BinaxPay may operate through or display related international entities on the public Company page (Página de la empresa). Status and roles vary by entity and may change as published there.

The Company page (Página de la empresa) shows BinaxPay Holding Ltd and other BinaxPay entities with their public registration or formation status, as published there. Refer to Página de la empresa for the current list.

Local entities may support regional operations, compliance, partnerships, or future services according to what is published on Página de la empresa. They do not by themselves mean all services are offered in every region.

No. Some entities may be listed as in formation or not fully operational. Rely on the current public Company page (Página de la empresa) rather than assumptions about operational status.

"In formation" means an entity is not yet fully registered or operational for the purpose shown on the Company page. It does not mean all services are available through that entity. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Official public company details are on Página de la empresa. This FAQ summarizes common questions; the Company page remains the source for entity listings and registry information.

You may contact BinaxPay using the channels on the Contact page and support@binaxpay.com for general support enquiries. WhatsApp and Signal may be available at +49 163 333 2543 where published.

For official contact, use support@binaxpay.com unless a different address is shown on Página de la empresa or in your agreement for a specific matter.

Private users may apply for a BinaxPay account where private banking products are supported. Approval is subject to verification, eligibility, and provider availability—not instant or assured. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Eligibility typically includes meeting identity and compliance requirements, residing in or connecting from supported jurisdictions, and passing KYC and risk checks. Criteria may change by product and country. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Where approved, private users may use features such as balances, payments, recipients, cards, statements, receipts, and documents as enabled in their product and jurisdiction. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Multi-currency support may be available where the product and provider support it. Currency availability is not assured in every country. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Private users may send or receive payments where supported after verification and subject to limits, compliance review, and provider rules. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Creating and managing recipients may be available where the payments product supports it. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Cards may be offered to eligible private users where supported. Card type, delivery, and limits depend on provider approval and jurisdiction. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Account statements may be available in the platform where the account product includes them. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Payment and transaction receipts may be downloadable where the feature is enabled for your account. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Document upload and management may be available for onboarding and ongoing compliance where required. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Verified customers may reach support through approved in-platform channels where available, in addition to public contact options such as support@binaxpay.com.

No. Private account services are not assured or promised. BinaxPay and partners may decline, restrict, or discontinue services as permitted by law and agreement. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Accounts may be restricted or closed for compliance, sanctions, fraud prevention, inactivity, provider decisions, or breach of terms, subject to applicable law and notice where required.

BinaxPay may support payment and account structures for private and business customers where products are offered, including multi-currency balances where available. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Account details such as account numbers or IBANs may be provided after approval where the product and provider support them. Details are not promised upfront. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Incoming payments may be accepted where account details are issued and the payment rail, sender, and compliance checks allow receipt. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Sub-accounts or additional balances may be available on some products where supported by provider and agreement. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Holding multiple currencies may be supported where the product allows it; not all currencies or corridors are supported in every market. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

IBANs may be available for some products and jurisdictions. Availability depends on provider allocation and compliance approval; a dedicated IBAN is not assured for every customer. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Account detail formats and availability vary by country, product, and provider. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Access may be limited for security, compliance, maintenance, or risk reasons, subject to applicable law and your agreement.

Yes. Account setup and ongoing use may require approval from BinaxPay and underlying banking or payment providers. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Export options may be available where the platform supports statements or data export for your product. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Statements may be viewed and downloaded where the account product includes them. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

If account setup is not approved, you will be informed where possible and may not receive account details or transactional services. You may contact support@binaxpay.com for general guidance without assurance of reversal. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay may support outbound and inbound payments, internal transfers, and related payment features where products and providers allow. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Sending payments may be available after verification, within limits, and subject to compliance and provider acceptance. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Receiving payments depends on issued account details, supported rails, sender compliance, and provider rules. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Internal transfers between your balances or sub-accounts may be supported where the product allows. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

International payments may be supported on some corridors via rails such as SEPA or SWIFT where available; not all corridors are supported. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Supported rails depend on product, currency, and provider. Common examples include domestic transfers, SEPA for EUR, and SWIFT for cross-border where enabled. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Rail availability varies by country, currency, provider, and compliance outcome. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Payments may be delayed, rejected, returned, or held for compliance, sanctions, insufficient information, provider, or legal reasons.

Payments may require review for AML, sanctions, fraud, unusual activity, corridor limits, or incomplete beneficiary details. Review timing is not fixed in advance.

Payment status may be visible in the platform where tracking is supported for your payment type. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Receipts may be available for download where the product provides them. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Cancellation may be possible only before processing completes and where the rail allows; many payments cannot be cancelled once sent.

No. Payment execution is not assured. Outcomes depend on providers, recipients, compliance, and legal requirements. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Pricing, fees, plans, and limits are not final and may change. Any pricing information is subject to eligibility, provider availability, compliance review, applicable law, and final agreement.

BinaxPay may offer card programmes where supported by provider partners and jurisdiction. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Virtual and physical cards on major card networks may be available for eligible customers where approved. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Virtual cards may be offered where the card programme supports them. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Physical cards may be offered where supported; delivery times and availability vary. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Freeze and unfreeze controls may be available in the platform where the card product supports them. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Card labelling or rename options may be available where implemented for your product. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Sensitive card data may be shown through secure, controlled views rather than plain display, where supported.

Replacement cards may be requested where the programme allows; fees and delivery may apply per your agreement. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Transactions may be declined by the network, issuer, merchant, limits, or security rules.

Failures may result from insufficient funds, limits, merchant category blocks, incorrect details, fraud checks, or provider downtime.

No. Card programmes are not offered in every country. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Card issuance is subject to approval, product rules, and provider availability. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Spending, ATM, and velocity limits may apply by product, provider, and compliance settings.

Cards may be suspended or closed for security, compliance, loss, abuse, or provider decisions, subject to applicable law and programme rules.

Onboarding typically includes creating an application, providing personal or business information, verifying identity and address, and completing compliance checks before any service is activated. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

You may need to provide legal name, date of birth or company details, address, contact information, and other data required by KYC, KYB, AML, and product rules. Requirements may differ by country.

Documents may include government ID, proof of address, company registry extracts, ownership information, and additional items requested for risk or regulatory reasons.

Identity documents help verify who is opening or controlling an account and are required for AML and KYC obligations.

Proof of address helps confirm residency or operating location for compliance and product eligibility. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Timing varies by completeness of information, document quality, jurisdiction, and review workload. There is no fixed public promise of same-day approval. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Enhanced due diligence, provider queues, or missing information can extend onboarding.

BinaxPay may pause review and request additional information before continuing. Services remain inactive until requirements are met and approval is granted where applicable.

You may be asked to provide a clearer or alternate document; repeated failures can lead to decline. Approval is not assured after resubmission.

Yes, where allowed you may resubmit corrected documents; resubmission does not assure approval.

No. Submitting documents does not assure approval or account opening. Outcomes depend on compliance review and provider decisions. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay compliance teams and appointed reviewers assess applications according to policy and law. Human review applies; public website content is not a substitute for your application outcome.

Checks may be performed by BinaxPay and external providers such as identity verification partners (for example Sumsub, where used on the site) and banking or payment partners.

Yes. Required fields, documents, and steps may differ by country, product, and risk profile. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay applies technical and organisational measures appropriate to a financial platform, including access controls and encryption in transit and at rest where applicable.

Secure authentication mechanisms are used for customer access where the product supports them.

Multi-factor authentication may be offered or required for certain actions or products.

Sessions use industry-standard protections; you should keep credentials confidential and log out on shared devices.

Card data is handled through controlled, PCI-aligned processes with partners where card services are provided.

Uploaded documents are stored with restricted access for verification and compliance purposes.

Yes. Data may be shared with providers that deliver payments, accounts, cards, verification, hosting, or support on BinaxPay's behalf, as described in the Privacy Policy.

Compliance providers help perform KYC, AML, sanctions screening, and fraud prevention required by law and policy.

The Privacy Policy is available at Política de privacidad.

The Cookie Policy is available at Política de cookies.

Yes. Contact support@binaxpay.com with data-protection questions; serious requests may require identity verification.

BinaxPay does not sell customer personal data. Processing is described in the Privacy Policy at Política de privacidad.

Email support@binaxpay.com, use WhatsApp or Signal at +49 163 333 2543 where published, or in-platform support where available for verified customers.

The official support email is support@binaxpay.com.

WhatsApp and Signal may be available at +49 163 333 2543 where published; Signal uses the same number as WhatsApp.

Verified users may access support from the platform where that channel is enabled for their product.

Include your registered email, a clear description, relevant dates and amounts, and references that help investigate without sharing unnecessary sensitive data.

Response times vary by channel, volume, and complexity. BinaxPay does not publish a fixed response-time promise in this FAQ.

Urgent payment or security issues should be flagged clearly; escalation is handled according to internal procedures without assured outcomes.

Yes. Report suspected fraud or unauthorized activity promptly via support@binaxpay.com and available urgent channels including +49 163 333 2543 where listed.

Support can help with general account questions within operational limits; some actions require verification.

Support can guide document resubmission processes where applicable.

Support can assist with payment status questions where information is available from providers.

Support can help with card blocks, replacements, or declines according to programme rules.

No. Public information is not a promise of service. Availability and performance depend on law, providers, compliance, and your agreement. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Countries and corridors differ; some products are not offered in certain locations. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Applications, payments, and ongoing activity may be reviewed for AML, sanctions, and risk.

Yes. Underlying banking, payment, and card providers must support the service. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Local financial regulation and restrictions apply and may limit what BinaxPay or partners can offer.

BinaxPay may refuse new customers or restrict existing access when required or permitted by law, policy, or agreement.

Yes. Partners may decline accounts, payments, or card operations independently of public marketing copy. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website. Consult a qualified professional for legal matters.

No. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website. Consult a qualified tax adviser for tax matters.

No. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website. Consult a qualified adviser before making investment decisions.

Terms and Conditions are published at Términos y condiciones.

The Privacy Policy is published at Política de privacidad.

KYC and AML information is published at KYC y AML. The Imprint is at Aviso legal and the Cookie Policy is at Política de cookies.

It means services, fees, and features apply only after you accept applicable terms at Términos y condiciones and related public policies, plus any product-specific agreement, and may change as permitted by law and notice requirements. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

BinaxPay's public website supports 21 language versions: English, Deutsch, Español, Français, Italiano, Türkçe, Nederlands, Svenska, Suomi, Polski, Dansk, Norsk Bokmål, Srpski, ქართული, हिन्दी, Հայերեն, Bahasa Melayu, Eesti, Македонски, සිංහල, and Shqip. Language choice helps users read public information in their preferred language. It does not by itself determine service eligibility. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Different domains help serve localized language and regional presentation for public information.

Domains are generally aligned with language or regional presentation; exact mapping is shown in language settings.

Yes. One language may be used across multiple country-oriented domains.

Core policies and product descriptions aim to be consistent, but localized pages may differ in examples or availability notes.

Use the domain or language selector that matches your preferred language; it does not by itself determine service eligibility. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. Language and domain selection is for localization of public content, not a promise of service availability. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

No. A country-oriented domain does not mean all services are available in that country. Availability depends on the product, jurisdiction, provider availability, compliance review, eligibility, applicable law, and final agreement.

Yes. Legal, tax, and compliance obligations differ by jurisdiction and affect which services may be offered. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website.

Use the site language selector or visit the appropriate localized domain where available.

AI-readable public information is machine-friendly content published so automated systems can discover accurate, public facts about BinaxPay without accessing private customer areas. It is for public discovery only—not a customer chatbot, not in-app assistant UI, and not an automated banking service.

ai.txt is a public file that explains how AI systems may read and understand BinaxPay public website information. It helps AI crawlers and search systems identify official public content, usage limits, and important legal disclaimers.

/llms.txt is a concise map of important public pages and AI-readable endpoints on the website for discovery purposes.

llms-full.txt is a public AI-readable index of BinaxPay website information. It is designed to help AI systems understand public company details, platform information, FAQ content, country partnership information, and legal limitations without using private or internal data.

/faq-ai.txt is a machine-readable export of this public FAQ, grouped by section, for automated consumers.

/public-data.json is structured public website metadata for automated consumers, without private customer data.

Yes, for public pages only. Summaries must respect stated limitations and must not invent assurances, universal availability, or private data. Content describes a regulated fintech platform, not personal advice or automated banking services.

AI systems may use published policies, FAQ, company information on Página de la empresa, and AI-readable files that explicitly allow public use.

Do not infer assured approval, universal availability, binding pricing, licences in every country, or access to private systems. Public files describe discovery metadata only.

No. Public content is informational service description, not personal financial advice. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website.

No. Public content is not legal or tax advice. BinaxPay does not provide legal, tax, investment, or regulated financial advice through the public website.

No. AI systems must not assume that BinaxPay services are offered in all markets. Service availability depends on jurisdiction, provider availability, local law, compliance review, eligibility, regulatory requirements, and final agreement.

No. Approval is subject to verification, compliance review, and agreement—not assured from public copy alone.

No. Private customer data is not available in public AI files or on the public marketing site.

No. AI-readable files exclude customer, admin, and provider-confidential data by design.

Start with /ai.txt, /llms.txt, /llms-full.txt, /faq-ai.txt, /public-data.json, and the public website pages they reference—including Página de la empresa for entity details.