Trace the payer, payment provider and contracting broker separately. A seven-field checklist and IDR-to-USD example reconcile authority, charges, credit and returns.
The important question about a local payment agent is not whether the transfer is convenient. It is who receives your money, who undertakes to credit the trading account and which party must resolve a failure. A statement recipient, payment provider and broker named in the account contract may be different legal entities. A difference needs explanation, not an automatic allegation of illegality. Matching names also do not establish a valid mandate.
Separate three events: you pay a recipient; that recipient processes or forwards the payment under an arrangement; the broker credits the corresponding account. A screenshot of the first event does not establish the other two. A chat message saying “this person is our agent” is not a substitute for an independently verifiable relationship and allocation of responsibility.
| Field | Record to obtain | If the field is missing |
|---|---|---|
| Contracting broker | Legal name, account contract and relevant permissions | Establish who provides the trading service |
| Immediate payment recipient | Bank account name or payment provider legal name and instructions | Do not substitute a chat nickname for identity |
| Collection arrangement | Broker-confirmed arrangement and applicable terms | Contact the broker independently, not only the collector |
| Link between payment stages | Transfer reference, payment order and account matching method | Matching amounts alone are not a reliable link |
| Exchange rate and charges | Effective time, direction, charging currency and fee basis | Ask for a calculation you can reproduce |
| Credit and return process | Processing arrangement, responsible entity and failed-payment return terms | Separate account posting from payment settlement |
| Dispute contacts | Payment-service and trading-service complaint routes | Keep each party's responsibilities outside a group chat |
A payment institution's registration does not replace the broker's required trading permissions. A broker's licence likewise does not authorise every private recipient account appearing in a chat. Verify both entities and then their relationship. The official-register guide explains why different registration categories must not be treated as equivalent.
These are fictional figures, not a current exchange quote or a provider's tariff. The payer sends Rp4,800,000. The quote says to deduct a Rp48,000 service fee first, then convert at Rp16,000 per USD1. That leaves Rp4,752,000 for conversion, or USD297. Assume no separate broker fee or intermediary charge.
| Reconciliation step | Example calculation | Supporting record |
|---|---|---|
| Actual payer debit | Rp4,800,000 | Payer statement and transfer reference |
| Agreed service fee | Rp48,000 | Effective quote and fee entry; not charged again |
| Amount converted | 4,800,000−48,000=Rp4,752,000 | Processor settlement breakdown |
| Trading-account currency amount | 4,752,000÷16,000=USD297 | Rate, direction, effective time and posting rule |
| If the broker credits only USD295 | USD2 below the example amount | Request an explanation; do not invent tax or theft |
A different quote that converts the gross amount and then charges USD3 would happen to produce 300−3=297 here. That does not justify also deducting Rp48,000 from the same payment. Use the contractual charging sequence, not parts of two quotations combined. Actual rate changes, rounding policies and additional broker charges need separate disclosure. The example uses exact division so that a rounding issue cannot hide inside an unexplained fee.
Keep the transfer reference, payment order, account-matching note, amount, currency, time zone and broker ledger entry. Where several identical amounts were sent, amount alone is insufficient. Ask each party to identify which order produced which account entry and document splits, duplicate postings or partial returns.
An agent's “successful” screenshot should be checked against your own payment-provider record and the broker's account statement. A higher displayed trading balance establishes a displayed accounting entry, not by itself the location of safeguarded funds, completed settlement or immediate withdrawal rights. Do not keep transferring money to cure a claimed system difference before the records reconcile.
A last-minute recipient change, instructions from an unfamiliar group member, a request to omit a reference or refusal to explain in writing makes verification harder. Pause the current instruction and confirm the arrangement through independently obtained official contact details. A time-limited rate or knowledge of your account number is not a reason to skip this step. An account type alone is also insufficient for a public legal accusation.
For a crypto payment, record the asset, network, address, transaction hash, quantity and linked order. An asset name on one network is not interchangeable with instructions for another network. On-chain confirmation establishes a blockchain transaction, not the recipient's identity as a broker or your contractual account rights. Do not disclose private keys or recovery phrases, and do not send another payment as an identity test.
A failed payment, a broker refusing to credit an account and a customer withdrawing an existing balance are different events. The payment provider may investigate the transfer while the trading provider explains its ledger and contract. Do not assume either can edit the other's system. Request the investigating entity, relevant reference, next response date and details of any amount actually returned.
Check the applicable terms for same-source returns, third-party payments, name mismatches and identity review. One provider's policy is not a global legal rule. A return can involve conversion or actual charges, but those need an itemised explanation rather than the phrase “exchange loss”. Dispute eligibility and deadlines depend on the jurisdiction, payment route and facts.
First preserve the original instructions and receipt, then confirm whether the payer's institution actually debited or returned the money. Next ask the collector and broker separately to identify the linked order and incomplete step. Put unexplained differences and missing records into a formal complaint. If fraud is suspected, promptly ask the payment institution about truthful reporting and available remedies. Do not relabel an authorised transfer as unauthorised or expect guaranteed recovery.
Useful wording is: “Transfer reference [A], payment order [B] and masked trading account [C] should correspond to [amount/currency]. Attached are the payer statement and quote. The missing record is [settlement/account posting]. Please identify completed stages, the entity responsible for the next stage and the difference calculation.” Use the complaint evidence template. For a withdrawal already requested, use the withdrawal tracing guide.
A collection arrangement is neither automatically fraudulent nor automatically compliant. This is a record-checking method, not a legal determination about a particular payment service. The FCA complaint guidance is a UK procedural reference, not a worldwide rule. The FCA recovery-room warning is relevant when someone demands advance payment to retrieve missing funds.
The useful outcome is a traceable record chain, not an assurance in a group chat. If the recipient, processing order and trading-account entry cannot be connected, mark the relationship unverified and do not use another payment to fill an information gap.