Banking Basics

What "banking basics" actually means

Most people learn banking by accident. You open an account because a job needs somewhere to send your pay, a card arrives, and the rest gets picked up from whatever goes wrong first. That works eventually, but it is an expensive way to learn. The guides collected here cover the parts that usually get skipped: what a statement is actually telling you, where fees come from, and why two accounts that look identical can behave very differently.

The foundation is the bank statement. It is the one document that shows a complete picture of an account over a fixed period, and it is also the document most people never read past the closing balance. Reading one properly means being able to spot a duplicate charge, recognize a subscription you forgot about, and understand why the balance on your phone is not always the balance the bank will honor tomorrow. Nearly everything else on this page builds on that one skill.

Fees are rules, not accidents

Overdraft charges, monthly maintenance fees, out-of-network ATM withdrawals and foreign transaction costs all follow published rules. They feel arbitrary because almost nobody reads those rules until after a charge appears. Once you know which conditions trigger which fee, most of them become avoidable, and the ones that do not become a good reason to choose a different account.

Checking and savings do different jobs

A checking account is built for money that moves. A savings account is built for money that should stay put. The distinction matters less for the interest rate than for the friction: putting a goal behind one extra step is often the entire reason the money is still there three months later.

Online safety is a habit, not a setting

The security features a bank gives you only work if the habits around them hold up. Knowing how a real alert differs from a convincing fake, and what a bank will never ask you for, protects an account better than any single toggle in the settings screen.

Why practice beats reading alone

Reading about a transfer and making one are different skills, and only one of them survives contact with a real account. CustomBank exists to close that gap. It is a simulator, so nothing inside it touches a real bank, real money or a real balance, which means there is no cost to getting something wrong. You can send a transfer to the wrong place, overdraw an account deliberately, or produce a statement with an error in it and see exactly how that reads, then do it again.

That is why the app works alongside the guides below rather than replacing them. Read how a statement is structured, then build one and find the line you were told to look for. Which you do first matters far less than doing both.