Study Guide
Table Of Contents
- PayPal Certified Developer Program Study Guide
- Contents
- List of Tables
- Online Payment Processing
- Internet Security and Fraud Prevention
- Why Every Business Should Be Concerned About Internet Fraud
- Liability for Internet Fraud
- Internet Fraud: What It Is and How It Happens
- Who Is at Risk for Online Fraud
- Reducing Exposure to Fraud
- What Banks and Card Associations Are Doing to Prevent Online Credit Card Fraud
- What PayPal Is Doing to Protect Your Business Against Fraud
- Disclosure and Compliance
- PayPal Fraud Protection Services
- Review Questions
- Getting Started With Account Setup
- API Credentials
- Name-Value Pair (NVP) API
- Express Checkout
- Direct Payment API
- Transactions
- Sandbox Testing
- Answers to Review Questions
- General Reference Information
- Glossary
- Index
Sandbox Testing
Testing Error Conditions
9
138 March 2008 PayPal Certified Developer Program Study Guide
Testing Using CVV Codes
You can simulate credit-card validation by triggering a CVV error code when you call
DoDirectPayment or use Virtual Terminal. To specify a CVV code, place a trigger value in
the NVP CVV2 field or the CVV2 SOAP element when you call DoDirectPayment, or enter
the trigger in Card Security Code when using Virtual Terminal.
Table 9.4 identifies valid CVV codes, corresponding triggers, and descriptions of the error
conditions.
N OTE: The specified CVV2 code is set, regardless of whether a PP API error code is set. If no
CVV2 code is specified, M is returned.Virtual Terminal displays the CVV2 error only if
the risk control blocks the payment.
Testing a CVV Code Using Virtual Terminal
Consider an example of testing for CVV code N using Virtual Terminal. You enter 116 in the
Card Security Code field:
TABLE 9.4 CVV Error Conditions and Triggers
CVV Code Trigger Description of Error
M115CVV2 matches (no error).
N116CVV2 does not match.
U125Service unavailable.
S123Service not supported.
P120Transaction not processed.
X130No response.