Practice banking API vocabulary: account balance inquiry, transaction history, insufficient funds rejections, ACH transfers, and SWIFT BIC codes.
0 / 14 completed
1 / 14
The app calls the bank API to perform an account ___ inquiry before initiating a large transfer.
An account balance inquiry is an API call that retrieves the current available balance (funds usable now) and ledger balance (all posted transactions) for an account. It is commonly used before initiating payments.
2 / 14
The finance dashboard calls the API to retrieve ___ history for the last 90 days.
Transaction history is a list of all credits and debits posted to an account within a date range. Banking APIs return this as structured records with fields like date, amount, description, and running balance.
3 / 14
The API response reads: 'The bank rejects the request due to ___ funds.' What caused the rejection?
An 'insufficient funds' rejection means the account does not have enough available balance to complete the transaction. The API returns a specific error code (e.g., NSF — Non-Sufficient Funds) so the caller can handle it appropriately.
4 / 14
The payroll system sends wages via ___ transfer — a US bank-to-bank electronic payment network.
ACH (Automated Clearing House) is the US electronic network for bank-to-bank transfers. It processes transactions in batches and is widely used for payroll direct deposit, recurring bill payments, and B2B transfers.
5 / 14
To route an international wire the system needs the recipient bank's SWIFT ___ code.
A SWIFT BIC (Bank Identifier Code) is an 8-11 character alphanumeric code that identifies a specific bank in the SWIFT international messaging network. It is required for all international wire transfers alongside the IBAN or account number.
6 / 14
Review Comment
During code review, Sarah commented on the `transferFunds` function:
"I'm seeing you're directly calling `getAccountBalance(accountId)` within the loop. Shouldn't we use a transactionRequest object and leverage the API's built-in error handling for insufficient funds? It seems less robust than repeatedly hitting the balance endpoint."
Sarah's comment highlights a critical best practice: minimizing redundant API calls. Repeatedly calling `getAccountBalance` for each transfer request introduces potential performance bottlenecks and doesn't utilize the bank API's designed error handling mechanisms, such as transactionRequest objects which often provide more detailed rejection reasons (like insufficient funds) than a simple balance check. The correct approach is to consolidate the balance validation within the API call itself, improving efficiency and robustness.
7 / 14
Review Comment
During code review, Sarah commented on the `transferFunds` function:
"I'm seeing you're directly calling `getAccountBalance(accountId)` within the loop. Shouldn't we use a transactionRequest object and leverage the API's built-in error handling for insufficient funds? It seems less robust than repeatedly hitting the balance endpoint."
Sarah's comment highlights a critical best practice: minimizing redundant API calls. Repeatedly calling `getAccountBalance` for each transfer request introduces potential performance bottlenecks and doesn't utilize the bank API's designed error handling mechanisms, such as transactionRequest objects which often provide more detailed rejection reasons (like insufficient funds) than a simple balance check. The correct approach is to consolidate the balance validation within the API call itself, improving efficiency and robustness.
8 / 14
Review Comment
During code review, Sarah commented on the `transferFunds` function:
"I'm seeing you're directly calling `getAccountBalance(accountId)` within the loop. Shouldn't we use a transactionRequest object and leverage the API's built-in error handling for insufficient funds? It seems less robust than repeatedly hitting the balance endpoint."
Sarah's comment highlights a critical best practice: minimizing redundant API calls. Repeatedly calling `getAccountBalance` for each transfer request introduces potential performance bottlenecks and doesn't utilize the bank API's designed error handling mechanisms, such as transactionRequest objects which often provide more detailed rejection reasons (like insufficient funds) than a simple balance check. The correct approach is to consolidate the balance validation within the API call itself, improving efficiency and robustness.
9 / 14
Review Comment
During code review, Sarah commented on the `transferFunds` function:
"I'm seeing you're directly calling `getAccountBalance(accountId)` within the loop. Shouldn't we use a transactionRequest object and leverage the API's built-in error handling for insufficient funds? It seems less robust than repeatedly hitting the balance endpoint."
Sarah's comment highlights a critical best practice: minimizing redundant API calls. Repeatedly calling `getAccountBalance` for each transfer request introduces potential performance bottlenecks and doesn't utilize the bank API's designed error handling mechanisms, such as transactionRequest objects which often provide more detailed rejection reasons (like insufficient funds) than a simple balance check. The correct approach is to consolidate the balance validation within the API call itself, improving efficiency and robustness.
10 / 14
John from the payments team sent a Slack message: 'Just noticed an unusual number of declined transactions – seems like we're hitting a rate limit on the API. Anyone know if there's a setting to increase the concurrency?' What does 'rate limit' refer to in this context?
Rate limits are designed to prevent abuse and ensure fair access to an API. In this case, John's message indicates that the bank's API is limiting the number of requests being processed, likely due to high demand. This prevents overload and maintains service quality; it's distinct from transaction amounts or database errors.
11 / 14
During a PR review, Maria comments: 'The API response for the 'transferFunds' operation shows a status code of 403. According to the documentation, this typically means 'Forbidden.' What's the most likely reason for this error given our current implementation?'
A 403 status code signifies 'Forbidden,' meaning the user or application doesn't have permission to perform the requested action. While insufficient funds (option A) can also cause errors, it would typically result in a different HTTP status code. Maria's permissions are the most probable cause given the documentation; invalid data could trigger other error codes.
12 / 14
David is writing a PR description for a new feature that uses the banking API to initiate international wire transfers. Which of the following phrases best describes the core function of the SWIFT code in this context?
The SWIFT code (Society for Worldwide Interbank Financial Telecommunication) is a crucial element in international wire transfers. It's a standardized code that identifies the recipient bank and country, allowing funds to be routed securely across borders. Understanding this distinction is key to correctly describing the function of the code.
13 / 14
Emily, during a standup meeting, states: 'We're using the API to perform a `getBalance` inquiry on each customer account before processing a payment. It's efficient but I'm worried about potential rate limits.' What is Emily primarily concerned about regarding this approach?
Emily is rightly concerned about rate limits. Making frequent 'getBalance' inquiries – often called polling – can quickly exhaust an API's rate limit, leading to temporary or permanent blocking of requests. This demonstrates a critical understanding of API usage best practices and potential operational issues.
14 / 14
The system is attempting to initiate a payment using the banking API. The response indicates: 'Transaction declined - insufficient funds.' Which of the following actions would *immediately* resolve this issue?
The core reason for the transaction being declined is 'insufficient funds.' Therefore, the most direct solution involves verifying that the recipient's account actually possesses enough money. While other options (A, B, and D) might be part of a broader troubleshooting process, they don't address the fundamental problem.
What does the "Banking API Vocabulary" exercise cover?
Practice banking API vocabulary: account balance inquiry, transaction history, insufficient funds rejections, ACH transfers, and SWIFT BIC codes.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Banking API Vocabulary"?
This exercise has 14 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Fintech Protocol Language exercises?
Browse the full Fintech Protocol Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.