Why a deposit condition cannot answer a withdrawal question
Money entering an account and money leaving it are different operations, even when the payment brand is the same.
The distinction that matters
Use separate rows for deposit and withdrawal. Each row needs its own minimum, maximum, cost, currency and conditions. A deposit page should not be used to fill missing withdrawal fields. The absence of a withdrawal option in a document is also not a statement that withdrawals are impossible.
A worked example
Suppose a method page displays C$10 under deposits and no withdrawal information. A comparison that copies C$10 into both columns creates an unsupported policy. The defensible record contains C$10 for the stated operation and an explicit unknown for the other.
Your next steps
- Read the section heading around the number.
- Keep direction attached when copying a field.
- Look for a dedicated withdrawal source.
- Ask the operator about missing information before relying on a route.
Where this answer stops
The numbers here illustrate data handling. They are not a real operator's limits. Do not make a deposit to discover whether a method can later receive a withdrawal.
Sources & reading
Original Northline explanation. Worked examples use stated assumptions; they do not establish an operator’s policy or predict personal results. Read how we handle evidence.
An editorial review date is not a new policy effective date. Always check the current source for operator-specific conditions.
Suggest a correction