I kept staring at a transfer screen last week and wondering how something as ordinary as moving coins to another account had turned into a form. Not a tax form. Not a bank wire. A short questionnaire that decides whether the coins leave at all. If you hold crypto in Brazil and you ever send it abroad, or receive it from someone who does not live there, November 1 is the date that form stops being optional. Miss a field and the withdrawal simply does not submit. An incoming deposit can sit in limbo, or in some cases bounce back to the sender. That is a different kind of friction from a fee. It is a gate.
The change is narrow on paper and wide in daily life. Domestic moves between two people who both live in Brazil stay as they are. Cross the residency line, even if both wallets belong to you, and the transfer is treated as international. That single distinction is the whole story. Everything else, the purpose codes, the counterparty type, the dollar thresholds, hangs off it.
What Actually Changes for Brazil Crypto Transfers on November 1
From that date, users of a large global exchange operating in Brazil will have to explain why crypto is moving across the border and who sits on the other side before some deposits and withdrawals can clear. The exchange has tied the new checks to a central-bank resolution that pulled international virtual-asset transfers into the country’s foreign-exchange framework and gave service providers fresh reporting duties.
I have found that people hear “new crypto rule” and picture a ban. This is not a ban. Ordinary trading is not being switched off. Transfers between Brazilian residents are untouched. What tightens is the paperwork around money, or rather assets, that cross a residency border. In my experience, paperwork is where calm users get surprised, because the asset still looks free on the screen until the button refuses to work.
The resolution treats a crypto movement as international in three situations. Ownership changes between a resident and a non-resident. Ownership changes between two non-residents. Or the same person sends or receives their own assets across Brazil’s border. That last case catches a lot of honest users. Sending coins to an account you own on an overseas platform counts. It is not a loophole. It is the rule.
Who Has to Fill the Form, and Who Does Not
Individuals and companies using the platform in Brazil are in scope when crypto moves between a Brazilian resident and someone who is not. The exchange has said users may need up to three pieces of information. First, the purpose of the transfer. Second, the type of counterparty: an individual, a company, a bank, an exchange, an investment fund, a nonprofit, or another category. Third, for corporate accounts, whether the other company sits in the same economic group.
Self-hosted wallets get a softer version of the same idea, and it is easy to mix the two up. If you move assets to or from a self-custody wallet you own, you do not have to state a purpose. You do have to confirm that the wallet is yours. The exchange will still report the movement to the central bank, under a separate category. That is not a free pass. It is a different box on the same reporting shelf.
A separate self-custody reporting rule, aimed at anti-money-laundering, already took effect on October 1 for qualifying transfers around the $10,000 mark. Do not fold that into the November purpose-code exercise. They share a calendar and a country. They do not share a job. One is about knowing the owner of a wallet. The other is about classifying an international transfer inside the foreign-exchange regime.
- Resident to resident inside Brazil: no new purpose questionnaire under this change.
- Resident to non-resident, or the reverse: purpose and counterparty details required.
- Same person, account on a foreign platform: treated as international, purpose auto-filled as an own-account move, then confirmed by the user.
- Same person, own self-custody wallet: ownership confirmation, no purpose field, still reported.
- API, institutional, and VIP flows: covered, with extra technical instructions for larger clients.
Why the Purpose Has to Match Real Life
Purpose codes come from classifications set by Brazil’s central bank. The everyday examples are familiar if you have ever filled a wire form: a transfer between your own accounts, payment for goods, IT services, business services, a donation, international travel. The category you pick is not a vibe. It is reported. Pick a label that does not match the real reason and you have created a record that can be checked later.
Perhaps the most interesting design choice is how the menu shrinks or expands with size. Transfers worth $50,000 or less, or the equivalent in another currency, use a simplified list of ten purposes. Cross that line and the menu opens into the full set of 96 classifications. The threshold is per transfer, not per month and not per year. Above $50,000 there is no generic “other.” You have to choose the classification that actually fits.
A purpose code is only useful if it describes the transfer you really made. A tidy wrong answer is still a wrong answer once it lands in a monthly report.
That missing “other” bucket is where I expect the complaints. Plenty of crypto flows do not map cleanly onto a goods invoice or a travel expense. A founder reimbursing a contractor. A family loan. A treasury shift between related companies. The long list exists so those cases have a home. It also means a rushed click on the nearest label is a bad habit to start on day one.
What the Regulator Actually Wants Reported
The resolution asks for a fairly specific packet. Transaction date. Purpose. Whether crypto entered or left the country. Customer identification. Asset type and quantity. Value in Brazilian reais. The foreign payer or recipient. Country. Relationship with the customer. The exchange has said the answers collected in the new questionnaire will go into monthly regulatory reports. It has not said the November change will halt ordinary trading or domestic transfers between residents.
Read that list slowly. It is not a travel-rule payload, even if it rhymes with one. It is a foreign-exchange record. The exchange has been explicit that the November questionnaire is not the country’s crypto travel rule. Domestic travel-rule duties are scheduled for 2027, international ones for 2028, with separate notices when those phases arrive. Mixing the two calendars will make November feel scarier than it is, and 2027 feel like a surprise when it is not.
Withdrawals Stop. Deposits Can Wait.
The operational split is the part worth taping above a desk. An international withdrawal cannot be submitted until the questionnaire is complete. There is no “send now, explain later” path on the way out. On the way in, funds arriving from abroad can remain pending while the platform waits for the requested details. In certain cases, if those details never arrive, the transaction may be returned to the sender.
Pending is an underrated word. A trader watching a balance that has not landed will assume a chain delay. Sometimes it will be a chain delay. After November 1 it might be a missing counterparty type. The difference matters if you are timing a payment, a payroll, or a simple move before a weekend. I would rather know the form is the bottleneck than refresh a block explorer for an hour.
API users are not exempt. Endpoints need the extra regulatory fields. Institutional and VIP customers are due separate technical notes. If your stack still posts a bare withdrawal, expect it to fail closed rather than fail open. That is the sensible default for a rule like this, and it is also the default that breaks unattended scripts at 2 a.m.
The $100,000 Cap Is Not a Blanket Ceiling
Here is the line people will quote wrong. Brazilian rules place a condition on transfers involving foreign counterparties that are not authorized to operate in the country’s foreign-exchange market. An older resolution, as amended by the 2025 measure, limits an international virtual-asset payment or transfer to the equivalent of $100,000 per transaction when the counterparty is not an institution authorized in that FX framework.
It is not a blanket $100,000 ceiling on every international crypto transfer. Application depends on the status of the institution or entity on the other side. A foreign exchange that has been assessed under central-bank requirements can appear in a drop-down. A platform that does not appear can be submitted to customer support for review. Inclusion is still subject to internal analysis. That is a polite way of saying the menu is not a wish list.
Central-bank rules also require a Brazilian virtual-asset provider dealing with a foreign crypto service company to check whether the overseas firm is under effective prudential and conduct supervision. If the foreign jurisdiction does not apply those requirements, the Brazilian provider has to document its own risk assessment before doing business with that firm. The drop-down is the visible edge of that work. The assessment file is the part you never see.
| Situation | What you provide | Size twist |
| International transfer at or under $50,000 | Purpose from a short list of 10, plus counterparty type | Simpler menu, still mandatory |
| International transfer above $50,000 | Purpose from the full list of 96, plus counterparty type | No generic “other” category |
| Counterparty not authorized in the FX framework | Same questionnaire, subject to the cap | $100,000 equivalent per transfer |
| Own account on a foreign platform | You are the counterparty; purpose auto-set, then confirmed | Still an international transfer |
| Own self-custody wallet | Ownership confirmation, no purpose | Reported under a separate category |
Use the table as a map, not a legal opinion. Thresholds are in dollars or the equivalent in another currency, and the real value reported is in reais. A transfer that looks comfortably under $50,000 at breakfast can sit over the line by the time you confirm it, if the asset or the exchange rate moves. Per transfer means splitting is a behavior the form will see, one ticket at a time. I am not suggesting anyone structure around a threshold. I am saying the form will not average your week for you.
A Walk Through Four Ordinary Transfers
Concrete cases help more than another recital of the resolution number. Take a designer in Recife who invoices a client in Lisbon and receives USDT. That incoming transfer is international. The designer should expect a request for purpose and counterparty type. Payment for services is the honest label. If the details are slow, the deposit can wait. If they never arrive, return-to-sender is on the table.
Second case: the same designer sends a slice of savings to an account she opened on a platform abroad, same name, same person. Still international. She identifies herself as the counterparty. The purpose field should fill itself as a transfer between accounts of the same person. Her job is to confirm that declaration, not to invent a more interesting story.
Third case: she moves coins from the exchange to a hardware wallet in her desk drawer. No purpose code. She confirms the wallet is hers. The movement is still reported, just not through the international purpose menu. If the amount also trips the October self-custody reporting threshold, that is a second conversation with a different rule, not a second copy of the November form.
Fourth case: a São Paulo company pays a supplier that is also in São Paulo, both resident, both on the same platform. This change does not add the questionnaire. Domestic is domestic. The moment that supplier’s receiving account is held by a non-resident entity, the picture flips. Residency of the party, not the vibe of the invoice, is what the framework looks at.
How This Sits Inside a Wider Rulebook
The new transfer procedure lives inside a broader push to supervise crypto firms more like financial intermediaries. Capital and licensing expectations for providers have been moving toward governance, risk management, and prudential standards closer to the world of brokers. November 1 is one operational slice of that shift, not the whole loaf. Users feel it as a form. Firms feel it as a reporting build and a counterparty-screening duty.
There is a related limit that people also blur into this story. Virtual assets cannot settle transactions inside the country’s supervised electronic foreign-exchange payment system. That measure does not prohibit ordinary crypto transfers through exchanges or wallets. It draws a line around a regulated payment channel. You can still move coins. You cannot treat those coins as the settlement asset inside that particular eFX rail. Different door, different lock.
The exchange has also said further details about a “transfer of operations to Brazil” will come in the following days. An early-October notice did not expand on that process. I would not build a theory on a phrase that has not been filled in. Watch for the follow-up. Do not treat silence as a hidden deadline.
What I Would Do Before the First of the Month
If I had regular cross-border flows, I would inventory them this week rather than on the morning the form goes live. Which counterparties are foreign. Which are my own accounts abroad. Which wallets are genuinely self-custody and in my name. Which transfers routinely clear $50,000 and will need the long code list. Which foreign platforms I use, and whether I have any idea if they would appear on an assessed drop-down.
- List every recurring international deposit and withdrawal, with a typical size and a real purpose.
- Match each purpose to the short list first. Flag anything that will need one of the 96 codes.
- Note counterparties that are not authorized FX institutions, and treat $100,000 per transfer as a hard planning number for those routes.
- Update API payloads so unattended withdrawals carry the new fields before they are rejected.
- Separate October self-custody reporting from the November purpose form so your ops notes do not merge two regimes.
- Tell anyone who sends you crypto from abroad that a missing reply can leave funds pending or returned.
None of that is dramatic. It is the unglamorous work that keeps a Friday payment from becoming a Monday ticket. I have watched teams treat compliance fields as a frontend nuisance and then spend a week explaining a stuck treasury move. The form is cheaper.
Purpose Codes, in Plain Language
You will not get the full 96-item catalog reprinted on a blog, and you should not trust a reprint anyway. Codes live with the central bank and with the platform’s implementation. What you can do is think in families. Own-account transfers. Goods. Services, including IT and broader business services. Donations. Travel. Investment-related movements where the classification exists. Intra-group company transfers, which is why the economic-group question shows up for corporate accounts.
The short list of ten is a courtesy for smaller tickets. It is not a suggestion that small transfers are invisible. They are still reported. They simply do not force you to browse a taxonomy built for trade finance. Cross $50,000 and the courtesy ends. That design tells you something about where the regulator expects ambiguity to hide: in larger tickets, where a vague label would do the most damage to the quality of the data.
A practical filter before you submit: Is the other party resident in Brazil? If yes, this form is not your problem. Is the other party you, on a foreign platform? Confirm the own-account purpose. Is the other party you, in self-custody? Confirm ownership, skip purpose. Is the ticket over $50,000? Open the long code list and pick the real reason. Is the foreign counterparty outside the FX authorization frame? Respect the $100,000 per-transfer cap.
I like filters like that because they fail in the right direction. If you cannot answer the first question, you are not ready to send. Residency is not a mood. It is a fact about the account holder. When in doubt, ask the counterparty before you need the answer under a pending deposit.
Companies, Groups, and the Extra Question
Corporate users get one more fork. They must say whether the other company belongs to the same economic group. That question exists because intra-group funding and third-party payments are not the same economic event, even when both look like a stablecoin transfer on a block explorer. Treasury teams that sweep balances between affiliates should expect to answer it every time the sweep crosses the residency line.
Same economic group does not mean “we work together.” It means a real group relationship. A supplier is not your group because you like their invoice terms. A sister company is. Getting that wrong is the corporate version of picking “travel” for a payroll. It will sit in a monthly report with your name on the customer field.
Funds, banks, nonprofits, and exchanges as counterparty types are there so the record can tell a payment processor from a cousin. Use them. A nonprofit donation and a payment to an exchange are both “sending crypto.” They are not the same purpose, and they may not face the same authorization question under the $100,000 condition.
Foreign Platforms and the Drop-Down Problem
The drop-down of foreign exchanges is going to be the emotional center of the first month. If your usual platform appears, the path is boring, which is what you want. If it does not appear, you can ask support to review it. Review is not a promise of inclusion. The Brazilian provider has to be comfortable that the overseas firm is supervised, or it has to have written down its own risk view where supervision is thin.
That is a reasonable burden and an awkward user experience. You cannot see the assessment. You can only see whether a name is on a menu. Plan for the awkward version. If a route you rely on is missing, the $100,000 cap for non-authorized counterparties may be the binding constraint while a review sits in a queue. Splitting a large move into compliant tickets is a conversation for your own counsel, not a trick to scribble in a chat. The cap is per transaction. It is also a signal, not a puzzle to solve.
A platform missing from the list is not a verdict on its quality. It is a statement about what the Brazilian provider has finished checking.
A compliance lead I would want on the desk in week one
Users who hop between several offshore venues will feel this more than users who keep one assessed route. Concentration has a cost in counterparty risk. Fragmentation now has a cost in paperwork and caps. Neither is free. The honest choice is to know which cost you are paying.
Self-Custody, Without the Myth
There is a myth that a hardware wallet makes a transfer domestic, private, or unreported. Under this framework, a move to your own self-custody wallet skips the purpose field and still gets reported under another category. The October rule on qualifying self-custody transfers is an AML reporting track. Neither rule turns a border crossing into a local errand.
Confirming ownership is also a fact you should be able to support. “I control the keys” is the start of the sentence, not the whole file. If a wallet is shared, multisig with a co-founder abroad, or held for a client, the clean “this is mine” box may be the wrong box. Those structures need a human look before November, not a hopeful click.
I am sympathetic to people who self-custody because they do not want a platform in the middle of every decision. Sympathy does not rewrite the reporting category. The category exists precisely because regulators know that path is popular. Treat the confirmation as a declaration. Declarations have a memory.
Travel Rule Later, FX Record Now
It is worth sitting with the calendar so the next two years do not blur. November 2026: purpose and counterparty data for international virtual-asset transfers, feeding monthly FX-style reports. October 2026, already in force: a separate self-custody reporting threshold for qualifying transfers. 2027: domestic travel-rule implementation on the timetable the exchange has described. 2028: international travel-rule implementation, again with separate notices.
Why the gap? A travel rule is about originator and beneficiary information traveling with the transfer, in the tradition of wire messaging. The November work is about classifying the transfer inside a foreign-exchange and international-capital frame: date, purpose, direction, customer, asset, quantity, reais value, foreign party, country, relationship. Overlap in spirit, different forms, different years. If a vendor tries to sell you one project that “covers all of it,” ask which notice they are building against.
Perhaps that staggered timetable is the most practical mercy in the package. Firms get a reporting build now and a messaging build later. Users get a questionnaire now and a fuller identity payload later. Annoying in sequence beats impossible all at once. It still rewards the teams who write the fields down before the endpoint rejects them.
What This Does Not Do
A short list of negatives, because rumor fills gaps. The change does not, on the exchange’s own account, stop ordinary trading. It does not add the questionnaire to transfers between Brazilian residents. It does not set a universal $100,000 cap on every cross-border coin movement. It does not replace the travel rule, and it does not start the travel rule early. It does not ban self-custody. It does not let virtual assets settle inside the supervised eFX channel, and it does not need to, because that channel was already off limits for this use.
It also does not care about your narrative. A transfer you describe as “just moving my own money” is still international if the other account is abroad. A transfer you describe as “small” is still reportable. A transfer you describe as “temporary” can still be returned if the details never show up. Language on social feeds will be looser than the form. The form wins.
Friction, Trust, and the User Who Just Wanted to Send
I keep coming back to the person who is not a compliance officer. They bought a little bitcoin, they have family abroad, they want to send a gift or pay a freelance invoice. The new screen will feel like a bank, because it is borrowing a bank’s logic. Purpose. Counterparty. Relationship. Value in local currency. That logic is how foreign-exchange systems have worked for decades. Crypto grew up pretending the border was a latency problem. Brazil is saying the border is a reporting problem.
Is that heavy for a $200 gift? The short list of ten purposes suggests someone thought about scale. Is it heavy for a $70,000 treasury move with no clean code? Yes, and that heaviness is intentional. Data quality on large tickets is the point of killing the “other” bucket. You can dislike the paperwork and still see why a regulator does not want a dump of unlabeled flows.
There is a trust question aimed the other way, too. Users are handing purpose and counterparty data to a platform that will pass it into monthly reports. That is the deal for using a supervised on-ramp in a country that has decided virtual-asset transfers belong in the FX frame. If that deal is unacceptable, the alternative is not a secret toggle. It is a different set of constraints, including the ownership confirmation and the separate reporting category on self-custody. Leaving the frame entirely is a life choice with its own costs, not a settings change.
Operational Edges Worth Rehearsing
Rehearse the ugly paths, not the happy one. A deposit lands pending on a Thursday night and the sender is asleep in another time zone. A withdrawal button stays disabled because a corporate user skipped the economic-group question. An API job retries the old payload and piles up errors. A foreign venue is absent from the drop-down on the day you needed a six-figure shift. A rate move pushes a ticket across $50,000 between quote and confirm, and the short list no longer applies.
Each of those has a boring fix if you have seen it once. Pending means chase the counterparty details, not the chain. A disabled withdrawal means finish the form, not open a second account. An API error means ship the fields, not raise the timeout. A missing venue means use an assessed route or accept the cap while review happens. A threshold cross means stop and pick from the long list. Write those fixes where the person on call will actually look.
For families and small businesses, the rehearsal is a conversation. Tell the relative abroad that a transfer might ask who they are. Tell the client that “payment for services” is the label you will use, and that it should match the invoice. Tell yourself that confirming an own-account move is not an accusation. It is the system recognizing the most common honest case and filling the purpose for you.
Numbers, Without the Fog
Three figures will get repeated until they lose their conditions. Pin the conditions back on.
- $10,000: the neighborhood of the separate self-custody reporting rule that started on October 1. Not the November purpose form.
- $50,000: the per-transfer line between a 10-code menu and a 96-code menu. Equivalent in other currencies counts. No generic “other” above the line.
- $100,000: the per-transfer cap when the foreign counterparty is not authorized in Brazil’s FX market framework. Not a universal ceiling.
Value in the regulatory report is in Brazilian reais. Dollar thresholds are how the rule speaks to users who price coins in dollars. Keep both in your head. A reais swing and a coin swing can each move you across a line. If a transfer is close, treat it as the stricter case and choose the code you can defend.
A Note on Tone, and on What “Tightens” Means
Headlines like “tightens” are fair and easy to overread. The exchange is adding checks it says follow the resolution. Withdrawals will not submit without the data. Some deposits may wait or return. Foreign venues get screened. Large tickets lose the vague category. That is tightening. It is not a shutdown, and describing it as one helps nobody plan.
I also would not describe it as a minor UX tweak. A gate on the submit button changes behavior. People batch transfers. People delay gifts. People move activity toward routes that feel simpler, including self-custody, without noticing that simpler is not the same as unreported. The second-order effect is the one I would watch through November: not a volume collapse, a change in how cross-border tickets are labeled and sized.
Questions Worth Answering Before You Click
Is the recipient a Brazilian resident? If you are sure, and you are one too, this questionnaire is not the hurdle. If you are not sure, find out before you send. Residency is the hinge.
Are you sending to yourself? On a foreign platform, say so, and confirm the own-account purpose the form offers you. In your own wallet, confirm ownership and do not go hunting for a purpose field that is not supposed to be there. If the wallet is not solely yours, pause.
Does the purpose exist on the list you are shown? Under $50,000 you have ten chances to be accurate. Over it you have 96 and no junk drawer. If nothing fits, the transfer may not fit the product path you chose. That is a signal to slow down, not to improvise a label.
Is the other side an authorized FX-market institution? If the venue is on the assessed menu, you are in the clearer lane. If it is not, the $100,000 per-transfer condition may apply, and a support review is a request, not a reservation. Size the ticket accordingly while you wait.
Who else needs to know? A sender abroad, a finance colleague, a script, a family member. The failure mode is asymmetric. You can be ready and still stall because the other human has not answered. Pending is a two-person state.
How I Would Explain It to a Skeptical Friend
I would say this. Brazil has decided that when crypto crosses the resident line, it belongs in the same mental drawer as foreign exchange. The big platforms that serve Brazilian users have to collect purpose and counterparty data and put it in monthly reports. Starting November 1, one major platform will not let you submit an international withdrawal without that data, and it may hold or return an international deposit that arrives without it. Moves between residents stay quieter. Moves to your own wallet skip the purpose and still get noted. A $50,000 ticket changes the length of the menu. A non-authorized foreign counterparty can cap the ticket at $100,000. The travel rule is a later project. Trading is not what this switch turns off.
If my friend asked whether I think the form will be annoying, I would say yes. Annoyance is not the same as surprise, and surprise is the expensive part. The resolution has been public. The platform notice is public. The only secret is which of your own transfers you have not labeled yet.
The Reporting Packet, Field by Field
It helps to picture the monthly file as a row you would not be embarrassed to read back. Date: when the transfer happened, not when you remembered to reply. Purpose: the real reason, from the list you were shown. Direction: in or out of the country. Customer: you, identified. Asset and quantity: what actually moved, not a rounded story. Value in reais: the local-currency figure the framework cares about. Foreign party: who paid or received. Country: theirs. Relationship: own account, group company, client, relative, platform, something you can say out loud.
Nothing in that row is exotic. Banks have collected cousins of these fields for years. The exotic part is that the asset is a token and the interface used to be a single confirm button. November replaces that button with a short interview. Answer it like a person who expects the row to exist later.
Corporate rows grow a branch. Same economic group, or not. That branch changes how a reader of the report understands the flow. Intra-group funding can be routine. A payment to an outside firm can be a trade settlement. The blockchain will not tell those apart. You will, in a field, on the way out.
Where Good-Faith Users Still Get Stuck
Good faith is not a field. The stuck cases I expect are boring. A nickname on an account that does not match a legal name, so the counterparty type feels fuzzy. A joint wallet. A transfer that is half gift and half loan. A stablecoin payment for software that could be “IT services” or “business services,” and the user freezes rather than pick. Freezing is safer than guessing if you can ask. Guessing is how tidy wrong rows get born.
Another stuck case: the user who withdraws to a foreign platform, gets asked to confirm an own-account purpose, and hesitates because the coins will later be spent by someone else. The purpose is about this transfer, the one leaving Brazil for an account in your name. What you do after that, on the other side, is a later fact. Do not relabel this hop to predict the next one. If the receiving account is not yours, do not use the own-account path. The form is offering a shortcut for a specific fact. Use it only when the fact is true.
API users get stuck in a more mechanical way. A field added to a payload is a contract change. Old clients will not invent the field. They will omit it, and the omission is the rejection. Ship the change before the date, in staging, with a ticket above and below $50,000 so both menus are exercised. I would rather break a test job in October than a payroll job in November.
Market Context, Held Lightly
Brazil is a large crypto market with a retail base and a growing institutional one. A rule that touches cross-border transfers will be felt in remittances, in freelancer invoices, in treasury pilots, and in the habit of parking coins on an offshore venue “just in case.” It will be felt less in a spot trade that never leaves the local residency box. Volume headlines that ignore that split will misread the first month.
I do not expect a single price reaction to a questionnaire. I do expect support queues, a few returned deposits, and a wave of posts confusing this with the travel rule. The useful response is the map above: who is in scope, which number applies, which calendar belongs to which rule. Panic is a poor checksum.
Providers, meanwhile, are being pulled toward governance and prudential expectations that look more like the broker world. Screening a foreign firm before you offer it in a drop-down is of a piece with that. Users experience screening as a missing name. The work behind the name is a risk file. Both are part of the same maturation, whether you welcome it or not.
A Clean Way to Keep Notes
If you move crypto across this border more than once a quarter, keep a one-page note. Counterparty legal name. Resident or not. Type. Purpose family. Whether they sit in your group. Whether their platform has shown up as assessed. Typical size versus the two dollar lines. Wallet or hosted account. Who in your house answers if a deposit goes pending. That page will outperform a reread of any article, including this one, at the moment the button stalls.
Before submit: resident? purpose real? counterparty typed? size vs $50k menu? size vs $100k cap if unassessed? ownership true if self-custody?Tape the checksum somewhere unromantic. The rule is not trying to be poetic. It is trying to make an international token transfer legible in a foreign-exchange report. Legible is a low bar and a high one. Low, because the questions are ordinary. High, because ordinary questions stop the send button when they are blank.
After the First Week
The first week will produce edge cases the notice did not narrate. A country field someone disputes. A nonprofit that looks like a company. A fund that is also an exchange. A user who confirms ownership of a wallet they share. Those cases belong with the platform’s support and, where the sums matter, with your own adviser. They do not belong in a guessed code chosen because the menu was long and the clock was short.
Watch also for the promised detail on moving operations locally. A phrase in a notice is not a timetable. When the follow-up arrives, read it against the transfer rules rather than instead of them. An operational relocation and a purpose questionnaire can coexist. One does not cancel the other.
By the end of November, the interesting question will not be whether the form exists. It will be whether people tell the truth on it, whether foreign venues get assessed at a pace that matches real routes, and whether pending deposits become a known delay or a folklore horror story. Folklore grows where instructions are vague. The instructions, this time, are fairly concrete. Use them.
The Part I Would Not Skip
If you remember one distinction, remember residency. Two Brazilian residents can still move crypto between themselves without this questionnaire. The moment one party is not resident, or the moment you send your own coins to an account abroad, the transfer is international and the form wakes up. Self-custody you own is the exception on purpose and not the exception on reporting. Size picks the menu at $50,000 and, for unassessed foreign counterparties, the cap at $100,000. Withdrawals wait for you. Deposits may wait for you, or go home.
That is the whole gate. It is narrower than a ban and wider than a tooltip. Fill it as if the row will be read, because the design of a monthly report says that it might. And if a transfer of yours is still unlabeled on the last day of October, unlabeled is the risk. Not the coin. Not the chain. The blank field beside the button.
I will be curious, in a month, which purpose families dominate the real tickets. Own-account moves, I suspect, then services, then a long tail the 96 codes were built to catch. If the long tail gets shoved into the nearest popular label, the reports will look cleaner than the economy. Cleaner than the economy is not the same as true. True is the only version of this form that is worth the extra click.
