Crypto Travel Rule Singapore: sender and beneficiary details on transfers

Crypto Travel Rule Singapore: why an exchange may ask about a transfer

The crypto Travel Rule Singapore users encounter is part of the Monetary Authority of Singapore’s anti-money laundering requirements for licensed digital payment token service providers. It concerns information about the person sending and the person receiving a value transfer, which must accompany or be traceable to the digital token transfer. That is why an exchange may ask for an originator name, recipient details or information about a wallet before it processes a withdrawal or credits an incoming deposit. The request relates to transfer records; it is not a request for a seed phrase or private key.

What MAS Notice PSN02 covers

MAS Notice PSN02 applies to holders of payment services licences that provide a digital payment token service. The notice requires those providers to collect, record and transmit specified information for value transfers. “Originator” is the party that allows or orders the transfer, while “beneficiary” is the party identified to receive the tokens. The regulated provider has duties around this information. The exact form or additional fields an exchange asks its customer to supply can depend on the transfer route and the provider’s own compliance process.

The current notice was revised on 30 June 2025. Read the MAS Notice PSN02 document for the official wording. MAS also explains that PSN02 covers customer due diligence, record keeping, wire transfers and other AML/CFT controls on its notice information page. A provider’s in-app checklist is an operational instruction for that service, not a replacement for the notice itself.

Sender and recipient details may travel with the transfer

For a value transfer of S$1,500 or less, paragraph 13.4 of PSN02 says an ordering institution must include the originator’s name and account number or unique transaction reference, and the beneficiary’s name and account number or unique transaction reference. The notice provides a separate rule for transfers above S$1,500: additional identifying information about the originator is required, such as an address, an identification number, or date and place of birth or registration. There are detailed provisions for how information can be sent through intermediaries, so use the full notice when a transfer has an unusual route.

The threshold is part of the provider’s obligations for value transfers. It does not mean a customer should ignore a smaller transfer request or invent details. A platform may need you to confirm the source wallet, who owns it, or who is receiving a transfer so it can fulfil its duties. Requirements can also differ across platforms and routes. Follow the verified request shown in the official app and ask the provider what field is missing if a transfer is held.

Exchange to exchange and personal-wallet transfers

A transfer between two exchanges may involve an originating service and a beneficiary service exchanging information in the background. The receiving platform may still ask you to identify the sender or confirm the destination account. A transfer between an exchange and a self-custody wallet can be handled differently because there may not be another regulated institution on the other side to provide the same information. The exact checks depend on the provider’s compliance procedures and the transaction details.

For example, one exchange may ask a Singapore customer to identify the sender when a deposit arrives from an external wallet. Another may request information before allowing an outgoing transfer. These are service-specific workflows, not universal steps that every exchange presents in the same order. Crypto.com’s Singapore Travel Rule FAQ is one example of a provider describing its own incoming and outgoing transfer process. Check your own platform’s current instructions before transferring.

Prepare a transfer record before you send

Before moving tokens, confirm the asset and blockchain network match on both sides. Copy the destination address from the receiving wallet or exchange, verify it on the final confirmation screen, and check whether a memo or tag is required. Keep the transaction hash, date, token amount, network, sending service, receiving service and any associated fee. If the destination is your own wallet, keep a note showing that you control both addresses. These details can help answer a provider’s question without guessing after the transaction has already left.

If an exchange asks for sender or beneficiary information, provide only what is relevant through its verified app or website. Do not share a password, one-time passcode, seed phrase or private key to satisfy a Travel Rule request. Those secrets give control of an account or wallet and are not ordinary transfer metadata. If a request arrives in a social message or from a lookalike domain, open the exchange independently and check its support centre before responding.

Why a deposit or withdrawal can be delayed

The MAS notice requires a provider to include the required information and says a transfer should not be executed or arranged if the provider cannot comply with the applicable transfer requirements. A receiving service also has procedures for handling value transfers that lack information. As a result, a platform can pause a deposit, request clarification, reject a transfer or take another action under its documented policies. A pending transaction does not necessarily mean a blockchain is congested; it can also be waiting on a compliance check.

Keep your transfer confirmation and support reference number if a transaction is under review. Avoid sending a second transfer to “test” the route until you understand what happened to the first one. If the blockchain transaction is confirmed but the exchange has not credited the deposit, provide the transaction hash through official support and ask which information is still needed. Never pay an unofficial “unlock fee” to an individual who contacts you outside the platform.

A practical Singapore transfer checklist

• Confirm the token, network, address and any required memo or tag.
• Record who controls the sending and receiving wallet or exchange account.
• Save the transaction hash, date, amount, fee and platform reference.
• Use only an exchange’s official app or support page to submit information.
• Provide the requested originator or beneficiary details accurately; do not guess.
• Never share a seed phrase, private key, password or one-time passcode.
• Read the current provider terms if a transfer is delayed, rejected or returned.

The MAS PSN02 notice is the primary source for the Singapore requirements; provider support pages can explain how a specific exchange applies them. The Travel Rule is separate from exchange fees, tax reporting and the security of a blockchain network. A request for transfer details does not itself show that a transaction is taxable or suspicious.

Keep the distinction clear

For Singapore users, the useful habit is to keep enough information to explain where a transfer came from and who should receive it. The provider handles its reporting and screening responsibilities, while the user can preserve accurate wallet, exchange and transaction records. The requested fields can change as platforms update their procedures, so check the official notice and your service’s latest help page before acting on a transfer question.

For more Singapore exchange information, visit CryptoSigy’s exchange guides and browse the Singapore crypto article collection. This guide explains the transfer-information framework and does not replace advice about a specific compliance issue.