diff --git a/source/docs/casper/resources/advanced/transfer-token-to-contract.md b/source/docs/casper/resources/advanced/transfer-token-to-contract.md
index b6ab7b897c..95b15831b3 100644
--- a/source/docs/casper/resources/advanced/transfer-token-to-contract.md
+++ b/source/docs/casper/resources/advanced/transfer-token-to-contract.md
@@ -7,6 +7,8 @@ slug: /resources/tutorials/advanced/transfer-token-to-contract
 
 This tutorial covers two methods to handle tokens via a contract. This is not a native process to a Casper network and will require the use of custom code. The following two scenarios provide a framework for developers and the pros and cons of each example. Developers should choose the option that best suits their individual needs.
 
+For increased security, token transfers from a main purse must be handled via session code (WASM), as shown [here](../../developers/writing-onchain-code/writing-session-code.md#example-3-transfers-using-session-code-transfers-using-session-code). Therefore, `transfer-*` methods are unavailable in stored WASM for tokens originating from an account's main purse, even when the stored WASM runs in the account context.
+
 ## Scenario 1 - Creating a Throw-Away Purse {#scenario1}
 
 The first scenario involves the use of a single-use, throw-away purse. The caller creates and funds a purse independent of their main purse, before passing the URef to the callee.