Payment Route and Source-of-Funds Checklist

Start by mapping the proposed transaction from beginning to end. Check which organisation would receive the initial instruction, whether an intermediary could be involved, and where the money would ultimately arrive. The name shown on a banking record may be worth checking against the details presented during the payment process.

Readers reviewing the payment route and source-of-funds checklist should confirm the displayed information themselves before proceeding. Do not infer that an option shown in one part of a site will necessarily be available for a particular account, location or transaction.

“Source of funds” generally concerns where money used for a transaction comes from. Before initiating a payment, consider whether the origin of the money can be explained clearly and consistently. Relevant questions include:

• Is the payment account held in the same name as the gaming account?
• Can the origin of the money be described accurately if a query arises?
• Are account details current and entered without errors?
• Does the proposed transaction create any inconsistency with previously supplied information?

Do not upload sensitive material merely because an unexpected message requests it. First verify where the request appears, why the information is being sought, how it would be handled, and whether there is a secure channel for responding.

Read the information displayed at the final confirmation stage rather than relying on an earlier summary. Look for the transaction amount, currency, any displayed charges, applicable limits and the destination details. If currency conversion may be relevant, check which party sets the rate and whether an estimate or final amount is being shown.

Also examine whether cancellation, reversal or correction options are described. Avoid assuming that a submitted instruction can be changed later. If any material term is missing or unclear, pause and seek clarification through a verified support channel.

Small inconsistencies can create uncertainty. Compare names, contact details, account identifiers and selected currency across the information shown. Check whether the proposed route involves an account belonging to another person or organisation, and consider whether that arrangement is expressly addressed by the applicable terms.

Never enter credentials, security codes or complete card details into an unverified message or page. Navigate through a known site entry point and inspect the destination carefully before submitting sensitive information.

Before confirmation, save the non-sensitive details needed to identify the instruction, such as the amount, currency, date and any reference displayed. After submission, compare the confirmation with the original instruction. Records can help readers describe an issue precisely, but they should be stored securely and shared only when necessary.

Pause if the destination changes unexpectedly, the requested information appears unrelated, the amount differs from what was entered, or the route cannot be explained clearly. Pressure to act immediately is another reason to slow down and verify the request independently.

A careful review cannot guarantee acceptance, processing or a particular result. Its purpose is to help readers understand what they are authorising, identify unanswered questions and avoid proceeding on assumptions. If the route remains unclear, do not confirm the transaction until the relevant details have been checked.