Testing

This document provides comprehensive testing guidelines for the Convenient Checkout platform, covering various payment methods, error scenarios, and environment-specific considerations.

Test Data

Refer Test Data

Retry Mechanism Testing

🔄 Overview of Retry Functionality

The Convenient Checkout platform implements retry functionality to permit up to 5 attempts when a user encounters a failure during payment or payment method entry validation.

📋 Retry Logic for Different Session Modes

Payment Mode

• After 5 failed attempts, the session becomes invalidated
• A dead-end screen is displayed to the user

Payment Method Entry Mode

• After 5 failed attempts, the session becomes invalidated
• A dead-end screen is displayed to the user

Payment With Wallet Mode

• After 5 failed attempts, the retry count is reset
• The user is redirected back to the wallet screen
• A warning message is displayed informing the user about the need to add payment method details again

📊 Retry Behavior by Payment Method Type

Payment Method	Input Validation Errors Count as Retry	Business Rules Validation Errors Count as Retry	Errors from Stripe Count as Retry
Card	No	N/A	Yes
ACH/Bank Account	No	Yes	No

Environment-Specific Testing Considerations

🧪 Non-Production Environment

• All test transactions are simulated and no actual charges occur
• Use the provided test card numbers and bank account details
• Testing digital wallets requires properly configured personal devices

🚀 Production Environment

• Use real payment credentials
• Transactions will result in actual charges
• Ensure proper domain validation for digital wallet payments

Troubleshooting Common Testing Issues

💳 Card Payment Issues

• Verify you're using the correct test card for the desired scenario
• Check that expiration date is in the future
• Ensure CVC is provided correctly (3 digits for most cards, 4 for Amex)

🏦 Bank Account Issues

• Confirm routing number is valid (110000000 for test environment)
• Ensure all required fields are completed correctly

📱 Digital Wallet Issues

• Buttons Not Appearing: Verify device and browser support, and confirm wallet setup
• Payment Failures: Check test card configuration and network connectivity
• Integration Issues: Confirm CCG widget configuration and session request parameter setup

PCI Environment Testing

Stripe Card Tokenization

Stripe card tokenization allows you to securely create a payment method token for a card, which can then be used for payments or saved for future use. This is essential for PCI compliance and secure handling of card data.

Below is a sample cURL request to create a card payment method using Stripe's API:

curl --request POST \
  --url https://api.stripe.com/v1/payment_methods \
  --header 'Authorization: Bearer <STRIPE_TEST_KEY>' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data type=card \
  --data 'card[number]=4242424242424242' \
  --data 'card[exp_month]=8' \
  --data 'card[exp_year]=2030' \
  --data 'card[cvc]=3141' \
  --data 'billing_details[address[postal_code]]=00000'

Usage Notes:

• Replace <STRIPE_TEST_KEY> with your actual Stripe test secret key.
• Use only Stripe test card numbers in non-production environments.
• The response will include a payment_method token that can be used for test transactions.
• For production, ensure you follow all PCI DSS requirements and use secure environments.

For more details, see the official Stripe API documentation: Stripe Payment Methods API

Support: If issues persist, contact CCG support via ServiceNow using assignment group: CCG_NONPROD_SUPPORT.