Card Payment Vocabulary
Practice English vocabulary for card payment processing: authorization, capture, chargebacks, interchange fees, and card network terminology.
0 / 25 completed
1 / 25
What is the difference between 'authorization' and 'capture' in card payments?
Authorization reserves the funds on the cardholder's account (checking that funds are available). Capture (or settlement) is when the merchant actually claims the funds. Hotels, car rentals, and restaurants often pre-authorize then capture the final amount.
2 / 25
What is a 'chargeback' in card processing?
A chargeback is a forced reversal of a card transaction, initiated by the cardholder's issuing bank. Merchants have a window to dispute it with evidence. High chargeback rates lead to penalties or loss of card acceptance.
3 / 25
What is 'interchange fee' in card payments?
Interchange is set by card networks (Visa, Mastercard) and paid from the acquirer to the issuer. Rates vary by card type (debit vs. credit, consumer vs. commercial), merchant category, and region.
4 / 25
What does '3DS (3D Secure) authentication' add to card payments?
3D Secure (3DS2 is the current version) adds a cardholder authentication step. When triggered, liability for fraud shifts from the merchant to the card issuer. It is required for strong customer authentication (SCA) under PSD2 in Europe.
5 / 25
What is a 'card network' (e.g., Visa, Mastercard) and what role does it play?
Card networks (Visa, Mastercard, Amex) operate the rails that connect acquirers (merchant's bank) and issuers (cardholder's bank). They set the rules, manage dispute resolution, and charge network fees for using their brand and infrastructure.
6 / 25
Sarah: 'Hey team, we're seeing a high volume of declined transactions for new user signups. The API response consistently shows 'error code 103' – 'insufficient funds'. What does that actually *mean* in the context of our payment gateway integration? A) The bank doesn't like our application.
B) The cardholder's primary account has been frozen by their issuing bank.
C) Our API is incorrectly requesting the full transaction amount from the payment processor.
D) The user's billing address is invalid, triggering a fraud check.
'Insufficient funds' (error code 103) doesn't indicate a problem with our application or the user's address. Instead, it signifies that the issuing bank has denied authorization for the transaction – typically because their fraud systems flagged the request as suspicious, or because the cardholder's account balance was below the required threshold at the time of the attempt. This is a standard step in preventing fraudulent activity.
7 / 25
The correct answer addresses the *immediate* technical issue flagged in the API response – rate limiting. Option B is tempting but could mask an underlying problem and potentially violate Stripe's terms of service. While a circuit breaker (option A) would be good practice, it doesn't directly address the 'Forbidden' error. Option C highlights a crucial consideration: exceeding limits often triggers security measures, and option D suggests bypassing support which isn't a sustainable solution.
8 / 25
Error code 51 ('Card details rejected') almost always indicates that the information provided by the customer – specifically the CVV or expiry date – doesn't match what the issuing bank has on file. While fraud is a possibility, the error code itself points to a data entry problem rather than malicious activity. Tokenization should mitigate this issue, but it's still important for users to correctly enter their card details.
9 / 25
The correct answer is B. 'Error code 70' – 'Temporary decline' almost always indicates an issue outside of our control, such as a temporary outage on Braintree's side or network connectivity problems. Increasing retry attempts (option A) might mask the underlying problem and lead to unnecessary API calls. While logging (option D) is good practice, it doesn't address the immediate cause; restricting limits (option C) could prematurely halt legitimate transactions. Option B represents a proactive step to investigate potential external factors that are causing the transient decline.
10 / 25
{code}
During a PR review for the new payment processing module, Alex flags an issue. The API response from Adyen shows 'error code 200' – 'Insufficient Data'. He suspects it's related to missing customer data in our system. Which of the following actions should be taken *first*?
The correct answer is A because addressing the immediate data deficiency is the most logical first step. While investigating the source of the missing data (B) and analyzing logs (D) are good long-term strategies, failing to provide a default value directly impacts the API response. Increasing the timeout limit (C) is a reactive measure that doesn't solve the underlying problem; it's crucial to correct the input data before sending it to Adyen.
11 / 25
Sarah: 'Hey team, we're seeing a high volume of declined transactions for new user signups. The API response consistently shows 'error code 103' – 'insufficient funds'. What does that actually *mean* in the context of our payment gateway integration? A) The bank doesn't like our application.
B) The cardholder's primary account has been frozen by their issuing bank.
C) Our API is incorrectly requesting the full transaction amount from the payment processor.
D) The user's billing address is invalid, triggering a fraud check.
'Insufficient funds' (error code 103) doesn't indicate a problem with our application or the user's address. Instead, it signifies that the issuing bank has denied authorization for the transaction – typically because their fraud systems flagged the request as suspicious, or because the cardholder's account balance was below the required threshold at the time of the attempt. This is a standard step in preventing fraudulent activity.
12 / 25
The correct answer addresses the *immediate* technical issue flagged in the API response – rate limiting. Option B is tempting but could mask an underlying problem and potentially violate Stripe's terms of service. While a circuit breaker (option A) would be good practice, it doesn't directly address the 'Forbidden' error. Option C highlights a crucial consideration: exceeding limits often triggers security measures, and option D suggests bypassing support which isn't a sustainable solution.
13 / 25
Error code 51 ('Card details rejected') almost always indicates that the information provided by the customer – specifically the CVV or expiry date – doesn't match what the issuing bank has on file. While fraud is a possibility, the error code itself points to a data entry problem rather than malicious activity. Tokenization should mitigate this issue, but it's still important for users to correctly enter their card details.
14 / 25
The correct answer is B. 'Error code 70' – 'Temporary decline' almost always indicates an issue outside of our control, such as a temporary outage on Braintree's side or network connectivity problems. Increasing retry attempts (option A) might mask the underlying problem and lead to unnecessary API calls. While logging (option D) is good practice, it doesn't address the immediate cause; restricting limits (option C) could prematurely halt legitimate transactions. Option B represents a proactive step to investigate potential external factors that are causing the transient decline.
15 / 25
{code}
During a PR review for the new payment processing module, Alex flags an issue. The API response from Adyen shows 'error code 200' – 'Insufficient Data'. He suspects it's related to missing customer data in our system. Which of the following actions should be taken *first*?
The correct answer is A because addressing the immediate data deficiency is the most logical first step. While investigating the source of the missing data (B) and analyzing logs (D) are good long-term strategies, failing to provide a default value directly impacts the API response. Increasing the timeout limit (C) is a reactive measure that doesn't solve the underlying problem; it's crucial to correct the input data before sending it to Adyen.
16 / 25
Sarah: 'Hey team, we're seeing a high volume of declined transactions for new user signups. The API response consistently shows 'error code 103' – 'insufficient funds'. What does that actually *mean* in the context of our payment gateway integration? A) The bank doesn't like our application.
B) The cardholder's primary account has been frozen by their issuing bank.
C) Our API is incorrectly requesting the full transaction amount from the payment processor.
D) The user's billing address is invalid, triggering a fraud check.
'Insufficient funds' (error code 103) doesn't indicate a problem with our application or the user's address. Instead, it signifies that the issuing bank has denied authorization for the transaction – typically because their fraud systems flagged the request as suspicious, or because the cardholder's account balance was below the required threshold at the time of the attempt. This is a standard step in preventing fraudulent activity.
17 / 25
The correct answer addresses the *immediate* technical issue flagged in the API response – rate limiting. Option B is tempting but could mask an underlying problem and potentially violate Stripe's terms of service. While a circuit breaker (option A) would be good practice, it doesn't directly address the 'Forbidden' error. Option C highlights a crucial consideration: exceeding limits often triggers security measures, and option D suggests bypassing support which isn't a sustainable solution.
18 / 25
Error code 51 ('Card details rejected') almost always indicates that the information provided by the customer – specifically the CVV or expiry date – doesn't match what the issuing bank has on file. While fraud is a possibility, the error code itself points to a data entry problem rather than malicious activity. Tokenization should mitigate this issue, but it's still important for users to correctly enter their card details.
19 / 25
The correct answer is B. 'Error code 70' – 'Temporary decline' almost always indicates an issue outside of our control, such as a temporary outage on Braintree's side or network connectivity problems. Increasing retry attempts (option A) might mask the underlying problem and lead to unnecessary API calls. While logging (option D) is good practice, it doesn't address the immediate cause; restricting limits (option C) could prematurely halt legitimate transactions. Option B represents a proactive step to investigate potential external factors that are causing the transient decline.
20 / 25
{code}
During a PR review for the new payment processing module, Alex flags an issue. The API response from Adyen shows 'error code 200' – 'Insufficient Data'. He suspects it's related to missing customer data in our system. Which of the following actions should be taken *first*?
The correct answer is A because addressing the immediate data deficiency is the most logical first step. While investigating the source of the missing data (B) and analyzing logs (D) are good long-term strategies, failing to provide a default value directly impacts the API response. Increasing the timeout limit (C) is a reactive measure that doesn't solve the underlying problem; it's crucial to correct the input data before sending it to Adyen.
21 / 25
Sarah: 'Hey team, we're seeing a high volume of declined transactions for new user signups. The API response consistently shows 'error code 103' – 'insufficient funds'. What does that actually *mean* in the context of our payment gateway integration? A) The bank doesn't like our application.
B) The cardholder's primary account has been frozen by their issuing bank.
C) Our API is incorrectly requesting the full transaction amount from the payment processor.
D) The user's billing address is invalid, triggering a fraud check.
'Insufficient funds' (error code 103) doesn't indicate a problem with our application or the user's address. Instead, it signifies that the issuing bank has denied authorization for the transaction – typically because their fraud systems flagged the request as suspicious, or because the cardholder's account balance was below the required threshold at the time of the attempt. This is a standard step in preventing fraudulent activity.
22 / 25
The correct answer addresses the *immediate* technical issue flagged in the API response – rate limiting. Option B is tempting but could mask an underlying problem and potentially violate Stripe's terms of service. While a circuit breaker (option A) would be good practice, it doesn't directly address the 'Forbidden' error. Option C highlights a crucial consideration: exceeding limits often triggers security measures, and option D suggests bypassing support which isn't a sustainable solution.
23 / 25
Error code 51 ('Card details rejected') almost always indicates that the information provided by the customer – specifically the CVV or expiry date – doesn't match what the issuing bank has on file. While fraud is a possibility, the error code itself points to a data entry problem rather than malicious activity. Tokenization should mitigate this issue, but it's still important for users to correctly enter their card details.
24 / 25
The correct answer is B. 'Error code 70' – 'Temporary decline' almost always indicates an issue outside of our control, such as a temporary outage on Braintree's side or network connectivity problems. Increasing retry attempts (option A) might mask the underlying problem and lead to unnecessary API calls. While logging (option D) is good practice, it doesn't address the immediate cause; restricting limits (option C) could prematurely halt legitimate transactions. Option B represents a proactive step to investigate potential external factors that are causing the transient decline.
25 / 25
{code}
During a PR review for the new payment processing module, Alex flags an issue. The API response from Adyen shows 'error code 200' – 'Insufficient Data'. He suspects it's related to missing customer data in our system. Which of the following actions should be taken *first*?
The correct answer is A because addressing the immediate data deficiency is the most logical first step. While investigating the source of the missing data (B) and analyzing logs (D) are good long-term strategies, failing to provide a default value directly impacts the API response. Increasing the timeout limit (C) is a reactive measure that doesn't solve the underlying problem; it's crucial to correct the input data before sending it to Adyen.
Frequently Asked Questions
What does the "Card Payment Vocabulary" exercise cover?
Practice English vocabulary for card payment processing: authorization, capture, chargebacks, interchange fees, and card network terminology.
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 "Card Payment Vocabulary"?
This exercise has 25 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.