Practice payment processing vocabulary: authorization, capture, settlement, chargeback, authorized but not captured, refund vs. reversal, and gateway decline codes.
0 / 14 completed
1 / 14
When a customer checks out, the gateway first requests an ___. What does this step do?
Authorization reserves the payment amount on the cardholder's account and gets approval from the issuing bank. No money moves yet — the funds are simply held. Authorization codes expire if not followed by a capture.
2 / 14
After packing the order the fulfilment system sends a ___ request to collect the previously reserved funds.
Capture is the second step in a two-step payment flow. It tells the payment processor to collect the previously authorized funds. Without a capture, the authorization hold eventually expires and the customer is not charged.
3 / 14
At end of day the processor runs ___ to transfer funds from issuing banks to acquiring banks.
Settlement is the batch process (often nightly) in which the payment processor and card networks move the actual funds from the cardholders' issuing banks to the merchant's acquiring bank.
4 / 14
A customer disputes a charge and the bank initiates a ___. What happens to the merchant?
A chargeback is a forced reversal initiated by the cardholder's bank after a dispute. The funds are returned to the customer and debited from the merchant, plus a chargeback fee. Merchants can contest chargebacks with evidence.
5 / 14
The payment log shows: 'Transaction status: authorized but not ___.' What does this mean for the customer?
'Authorized but not captured' means the payment gateway received bank approval and reserved the funds, but the merchant has not yet sent a capture request. The customer sees a pending charge but is not yet billed.
6 / 14
Sarah: 'Hey team, I'm seeing a lot of 'pending' transactions on the dashboard. The API response is showing a 203 status code for these – any ideas why they aren't fully processing?',
During a code review discussion with your lead, Mark replies: 'It looks like we might be experiencing intermittent issues with our payment processor's 'authorization hold' feature. The system is temporarily reserving funds while it verifies the customer's card details with the issuing bank.
Which of the following best describes what Mark is referring to in this context?
The 'authorization hold' feature is a standard practice in payment processing. It's not an error; it's a temporary measure where the processor reserves funds while confirming the customer's card details with their issuing bank (the bank that originally issued the credit/debit card). Option A incorrectly frames this as a failure, and options C & D present inaccurate technical scenarios. Option B accurately describes this common process.
7 / 14
Sarah: 'Hey team, I'm seeing a lot of 'pending' transactions on the dashboard. The API response is showing a 203 status code for these – any ideas why they aren't fully processing?',
During a code review discussion with your lead, Mark replies: 'It looks like we might be experiencing intermittent issues with our payment processor's 'authorization hold' feature. The system is temporarily reserving funds while it verifies the customer's card details with the issuing bank.
Which of the following best describes what Mark is referring to in this context?
The 'authorization hold' feature is a standard practice in payment processing. It's not an error; it's a temporary measure where the processor reserves funds while confirming the customer's card details with their issuing bank (the bank that originally issued the credit/debit card). Option A incorrectly frames this as a failure, and options C & D present inaccurate technical scenarios. Option B accurately describes this common process.
8 / 14
Sarah: 'Hey team, I'm seeing a lot of 'pending' transactions on the dashboard. The API response is showing a 203 status code for these – any ideas why they aren't fully processing?',
During a code review discussion with your lead, Mark replies: 'It looks like we might be experiencing intermittent issues with our payment processor's 'authorization hold' feature. The system is temporarily reserving funds while it verifies the customer's card details with the issuing bank.
Which of the following best describes what Mark is referring to in this context?
The 'authorization hold' feature is a standard practice in payment processing. It's not an error; it's a temporary measure where the processor reserves funds while confirming the customer's card details with their issuing bank (the bank that originally issued the credit/debit card). Option A incorrectly frames this as a failure, and options C & D present inaccurate technical scenarios. Option B accurately describes this common process.
9 / 14
Sarah: 'Hey team, I'm seeing a lot of 'pending' transactions on the dashboard. The API response is showing a 203 status code for these – any ideas why they aren't fully processing?',
During a code review discussion with your lead, Mark replies: 'It looks like we might be experiencing intermittent issues with our payment processor's 'authorization hold' feature. The system is temporarily reserving funds while it verifies the customer's card details with the issuing bank.
Which of the following best describes what Mark is referring to in this context?
The 'authorization hold' feature is a standard practice in payment processing. It's not an error; it's a temporary measure where the processor reserves funds while confirming the customer's card details with their issuing bank (the bank that originally issued the credit/debit card). Option A incorrectly frames this as a failure, and options C & D present inaccurate technical scenarios. Option B accurately describes this common process.
10 / 14
During a standup update, David says: 'We're seeing some intermittent failures with our Stripe API. The error codes are consistently returning 'unprocessable entity'. What does this generally indicate in the context of payment processing?'
The 'unprocessable entity' HTTP status code from Stripe signifies that the request data sent by your application was invalid according to Stripe's requirements. This often means there's a problem with the format of your payment details (e.g., incorrect card number or expiry date), preventing the transaction from being processed—it is *not* a general server error.
11 / 14
Maria writes in a Slack message: 'I'm getting lots of 403 Forbidden errors when trying to process refunds via the Payment Gateway API. The logs show the requests are correctly authenticated. What's likely happening?'
A 403 Forbidden error indicates that your application, despite being authenticated correctly, doesn't have permission to perform the requested action (processing refunds). This often arises from misconfigured API keys or insufficient roles/permissions associated with the account used for payment processing—the issue isn't a server overload.
12 / 14
You are reviewing a PR that implements a new webhook handler for charge captures. The code includes the following comment: 'We're using idempotency keys to prevent duplicate capture requests.' What is the primary purpose of an idempotency key in this scenario?
Idempotency keys are crucial for handling potential webhook retries. They allow the system to identify and prevent processing the *same* capture request multiple times, ensuring data consistency and preventing accidental double-charging—it's about guaranteeing a single execution of the action.
13 / 14
The API response for a payment authorization is: `{"status": "authorized", "transaction_id": "txn_1234567890"}`. What does the 'authorized' status primarily signify?
'Authorized' indicates that the payment request has been accepted by the acquiring bank and is moving through the processing stages. It doesn't mean the funds have actually left the customer's account—further verification steps may still be required before completion.
14 / 14
During a code review discussion, David mentions: 'We need to handle the case where a payment fails after authorization but before capture. The system should send an email notification to the customer.' What is the most appropriate term for this post-authorization, pre-capture event?
A 'pending transaction' accurately describes the state of a payment that has been authorized but not yet captured (or settled). This is the period between authorization and final funding, where additional checks or actions might still occur—the other options represent different stages of the payment lifecycle.
What does the "Payment Processing Vocabulary" exercise cover?
Practice payment processing vocabulary: authorization, capture, settlement, chargeback, authorized but not captured, refund vs. reversal, and gateway decline 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 "Payment Processing 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.