Protecting your A-PFI order, data and transfers

Depending on the journey, data can include identity and contact details, residential address, bank and wallet information, order and transaction records, support messages, identity documents, source-of-funds material, device and security data, and records of policy acceptance.

Sensitive fields and private files are encrypted and access is logged. Secure customer functions use verified, purpose-bound sessions, and Support attachments are checked before download. No system can guarantee absolute security, so send sensitive documents only through the requested secure portal.

Depending on applicable law, you may have rights to access, correct, delete, restrict, object to, or receive certain information. Submit the request through secure Support; identity verification may be required, and some financial, legal, security, or audit records cannot be deleted while retention duties apply.

Essential first-party cookies or equivalent session storage keep secure forms, language, and verified sessions working; they are not described as advertising profiles. The interactive Demo keeps progress only in component memory and clears it when the page is refreshed or closed.

The order form shows only countries currently enabled for the selected Buy or Sell direction and EUR or USD currency. A country can exist in the directory while service remains disabled or under legal review. Availability also does not by itself confirm that every person or activity is eligible.

Hong Kong is a recognized country entry, but a customer route remains unavailable until the applicable direction and currency are enabled after the required review. If it does not appear for your selected route, that route is not currently available.

Real orders can be created only in Live mode with executable pricing and the required route configuration. Sandbox shows illustrative quotes, while Maintenance pauses new orders. A placeholder, stale or unavailable rate, disabled direction, or unavailable network can also leave only a preview.

The amount may be outside the displayed minimum and effective maximum, monthly Buy capacity may be exhausted, fees may leave no valid settlement amount, the quote may have expired, or pricing may be unavailable. Return to the amount step, use the shown limits, and request a fresh quote.

The file may use an unsupported type, exceed the per-file or total limit, belong to the wrong request, fail its security check, or no longer match an active upload session. Choose a clear permitted file from the current secure step; do not rename an unsafe format merely to bypass validation.

Resume or cancel the unfinished order from this connection before creating another. If the site instead says too many Sell orders were started recently, wait before retrying or contact Support. Do not change order details merely to work around a displayed limit.

Do not send money or USDC using an old order example, demo screen, or saved bank details. Wait until the live interface provides a new quote and creates an order successfully. If you already funded a valid open order, use its tracking page or Support instead of creating a replacement payment.

Keep the order reference and any payment evidence, then use the status page when service returns. Do not repeat a bank or blockchain transfer merely because the page was temporarily unavailable.

No. Wait until the service can present a fresh reviewable quote. A manually calculated rate or old screenshot is not a substitute for the amount and terms attached to an order.

A temporary data-provider problem can delay what the status page displays. Verify the hash independently on the correct network, keep it, and avoid broadcasting a duplicate while the first transfer remains valid.

Yes, the page may wait for verifiable bank information even when your own bank shows progress. Keep the receipt and let the order update; do not send again unless the first transfer is clearly returned.

First check for an order confirmation, reference, email, or tracking record. Retry only if the form clearly remains unsubmitted; repeated clicks can create confusion about whether the first request succeeded.

An old tab or restored page can display stale content. Open the secure current order from its trusted tracking path and compare its reference and status before using any payment details.

Interactive validation, secure steps, and live status can require JavaScript. Enable it for the genuine site in a current browser, then reload; do not use a third-party copy of the form.

Some session continuity or security state may not persist between steps. Allow the genuine site’s necessary storage for the journey or use a normal browser profile, then restart the affected step carefully.

Private windows may discard session data when closed. Keep the order reference and verified email, and use the secure tracking flow rather than relying on the private tab to preserve progress.

Use a trusted network that permits the genuine site’s required secure connections, or ask the network administrator about the blocked domain. Do not bypass company policy with unknown proxy tools.

Abrupt network or location changes can trigger a new session or additional security checks. Keep a stable trusted connection during sensitive steps and never misstate your actual residence or identity information.

Yes. If a trusted page is incomplete, temporarily allow its essential scripts and reload, while keeping protection against unrelated domains. Confirm the site address before changing any blocker setting.

One window may contain older session state. Continue in the window showing the current secure status, close the stale copy, and do not submit payment information from both.

Recheck every visible field rather than assuming the draft survived rotation. If the order had already been created, return through secure tracking instead of recreating it from memory.

Scroll within the page, try the device’s standard orientation, or reduce zoom enough to reach the control without making text unreadable. Keyboard focus can also help locate interactive elements.

Navigate by headings and form labels, listen to the full field value, and review the order summary before submission. If a control has no understandable label, stop and report that accessibility issue to Support.

Use Tab and Shift+Tab to move, Enter or Space to activate controls, and arrow keys where a list or slider supports them. If focus becomes trapped or invisible, report the page and control to Support.

Reconnect, then check for the confirmation, email, or secure tracking record before submitting again. Preserve any visible reference or screenshot from the first attempt.

A session can expire to protect order details. Restart the purpose-specific verification from the genuine page and do not use an old code or a link copied from an untrusted source.

Do not bypass the warning or enter order, banking, identity, email-code, or wallet information. Check the domain, date, and network, then return only when the browser establishes a valid secure connection.

Do not send. Clipboard malware or a browser extension may have replaced the address. Compare it with the secure order, secure the device, and contact Support if the mismatch continues; a blockchain transfer to the wrong address may be irreversible.

A trusted private connection is safer for sensitive order, identity, wallet, and bank steps. If the network or certificate warning looks unusual, stop and reconnect securely rather than submitting data or approving a transfer.

It can let the approved contract spend up to the allowance from your wallet later. A direct Sell transfer should not be confused with an unlimited approval. Reject unexpected requests and never approve a contract solely because a message claims it is required.

Reviewing unnecessary allowances is good wallet hygiene, but use a trusted method and do not mistake revocation transactions for Sell payments. Revoking an allowance costs gas and does not fund the order.

No. A public address and transaction hash are enough to inspect public blockchain activity. Never share a private key, seed phrase, recovery phrase, keystore file, or remote-control access with anyone.

Never upload or photograph a seed phrase for an order or support case. It grants control of the wallet and is not valid ownership evidence. Use only the safe verification method presented in the secure portal.

Do not expose secret phrases, private keys, codes, balances, or unrelated transactions through screen sharing. Support can request limited public evidence through the secure ticket; no one should control your device or wallet for you.

A counterfeit app can steal recovery material, replace destinations, or fabricate transaction status. Install wallets only from verified publisher channels and independently compare the on-chain hash and destination before trusting the interface.

Treat notifications as prompts to inspect the trusted wallet and blockchain hash, not final evidence. Phishing notifications can contain malicious links. Open the wallet independently instead of following an unexpected message.

Anyone can monitor public blockchain activity and send fake support messages or tokens. Ignore unsolicited recovery offers, links, and wallet requests. Continue only through the official site and your existing secure order.

Do not interact with, approve, swap, or follow links attached to an unsolicited token. Hide it in the wallet if desired. Its presence does not change the status of your legitimate order.

Public addresses can receive unsolicited spam NFTs containing malicious links. Ignore and hide them; do not connect your wallet to claim, burn, or redeem anything. They are unrelated to the Sell order.

An attacker sends a small transaction from a look-alike address so it appears in wallet history. Never copy a deposit destination from recent activity; copy the full address from the current secure order and compare it completely.

Keep the device updated, avoid untrusted software, copy only from the secure order, and compare the full pasted address on the wallet and signing device. Stop if any character changes unexpectedly.

Do not use it for the order. Cancel the unfunded order if permitted, secure assets using independent trusted guidance, and create a new order only with an eligible safe wallet. Never announce recovery details in a public ticket.

Check the exact transaction and order, then contact Support without sharing secrets. Secure any remaining assets using trusted independent steps. The confirmed transfer cannot normally be pulled back from the blockchain by changing your wallet credentials.

Use a known explorer reached independently or through a trusted order link, check the domain carefully, and never connect a wallet just to view a public hash. Viewing transaction data should not require a seed phrase or token approval.

They may be trying to enter your secure order or Support session. A one-time code is for you to type into the official page only. Do not read, forward, screenshot, or paste it into chat.

Type or use your trusted bookmark for a-pfi.com, inspect the complete hostname and HTTPS certificate warning state, and avoid look-alike links from ads, messages, or search results. Stop if the browser reports a certificate problem.

Yes. Advertising placement does not prove authenticity. Verify the exact domain before entering an email, code, identity data, bank details, or wallet information, and never install remote-support software from an advertisement.

Do not send funds using saved instructions while you cannot confirm the current secure status. Keep your reference and payment evidence, try again later through the official domain, and contact Support if a deadline or sent payment is affected.

Some creation, tracking, verification, or payout views may be temporarily unavailable. Follow any notice displayed before maintenance, keep your reference, and never assume a deadline changed unless the secure order explicitly confirms it.

Use a current mainstream browser with JavaScript, cookies needed for the secure session, and camera access when verification requires it. Disable extensions that modify pages or block essential requests if they cause errors.

Strict private mode can clear session data when a tab closes or block storage needed for a secure journey. A created order remains tracked by its reference, but you may need a fresh email code to return.

It can mistranslate financial, bank, wallet, or status terms and visually alter form fields. Prefer the site’s supported English or French version for critical instructions and compare values before payment.

The Help Centre search and article controls are intended to support keyboard and assistive navigation. If a control is unreachable or unclear, report the page, browser, device, and exact step to Support.

Bank, blockchain, email, verification, storage, or application dependencies can degrade independently. An incident can delay observation or messages without changing what was already sent. Avoid duplicate actions and retain evidence.

No uninterrupted availability should be assumed. Maintenance, provider incidents, risk controls, legal restrictions, market conditions, or capacity can pause quotes or processing. Check the live form and secure order for current availability.

It means the public experience is not a Live funding journey. Explore only the preview features provided, and do not send money, USDC, identity documents, or real personal information. Wait until the site clearly shows that the relevant service is Live.

Avoid uploading sensitive documents to an unknown conversion website. If a permitted file must be converted, use a trusted local tool or a service whose privacy handling you understand, then open the result and review its contents before attaching it.

No. Pause and open the authenticated order from the official site. Do not send money or USDC to details supplied by an unsolicited email, call, message, or social account. Report the conflicting message through the official Support route before taking further action.

No. A disabled control can reflect an unavailable route, expired quote, missing step, or invalid state. Editing the page does not make the action valid and can display misleading values. Refresh the official page or ask Support why the control is unavailable.

Avoid unnecessary screen recordings because they can capture personal details, codes, private links, bank instructions, or identity images. If Support requests evidence of a display problem, share only the smallest relevant still image after reviewing and redacting it.

Secure the device and its email account using the provider’s recovery controls, then access the official service from a trusted device. Reverify when requested, review the order status, and contact Support if someone may have viewed or changed information. Never send passwords as evidence.

Secure the mailbox first through its provider, review forwarding rules and active sessions, and do not request new service codes until you control it again. Then contact Support through the official site with the order reference and a concise explanation, without sharing mailbox credentials.

Stop before submitting or paying. Disable the unfamiliar extension, reopen the official page in a clean trusted browser profile, and compare every value with the active order. If any value still changes unexpectedly, preserve non-sensitive evidence and report it to Support.

Do not intentionally save one-time codes, private access links, wallet secrets, or complete payment details in browser notes or autofill. On a trusted private device, review any save prompt carefully; on a shared device, decline it and close the sensitive tabs when finished.

Avoid shortened links because they conceal the destination. Open the official site by typing its known address or using a trusted bookmark, then enter the authenticated order or Support flow there. Report the shortened link without opening it or sharing private access details.

Do not post it publicly. Tracking pages can expose references, status details, personal data, private links, wallet addresses, or bank information. Use the authenticated Support channel and share only the minimum relevant, carefully reviewed portion.

Do not run unexpected software, installers, browser packages, or scripts. Leave the prompt, return to the official site through a trusted bookmark or typed address, and verify the order status. Report the page or message through official Support with non-sensitive evidence.

Prefer a supported device and current browser that still receive security fixes. An outdated operating system or browser can expose email, identity, bank, and wallet information. Move to a trusted updated device before entering sensitive data or authorizing a transfer.

Do not broadly disable security warnings, antivirus protection, certificate checks, or safe-browsing controls. Confirm that you are on the official site and try a current supported browser or trusted device. If the block remains, record the non-sensitive warning and ask Support.

Do not pay, send crypto, sign a message, or reveal secrets to that person. Recovery and refund outcomes are never established by an unsolicited demand for an advance fee. Preserve non-sensitive details of the contact and report it through the official Support channel.