Testcase_ID Test case

Column1 Column2

ID_001 Successful Payment

ID_002 Payment Failure - Invalid Formate

ID_003 Expired Card

ID_004 Payment Failure - Insufficient Funds

ID_006 Payment Failure - Network Error

ID_007 Payment Refund

ID_008 Payment Security

ID_009 Partial Payment

ID_010 Payment Timeout

ID_011 Currency Support

ID_012 Payment Gateway Error Handling

ID_013 Payment Amount Overflow

ID_014 Negative Payment Amount

ID_015 Expired Token or Session

ID_016 Transaction Timeouts and Retries

ID_017 Unexpected Errors

ID_018 Unsuccessful Payment

ID_019 Multipal card added

ID_019 Payment with Saved Payment Methods

ID_020 UI Test Cases for Payment Gateway

ID_021 Functional Test scenario

ID_021 Functional Test scenario

ID_022 If multiple user use simultaneously.

 Test scenario Test Data
Column3 Column4

Verify that a payment is successfully processed when valid credit card

details are provided.
Credit/debit card number+wrong date+ right cvv
Credit/debit card number+ right date+ wrong cvv
Wrong credit/debit card number+ right date+ right cvv
And some other similar combinations

Verify that the payment fails when an expired credit card is provided.
Verify that the payment fails when the card does not have sufficient
funds.

Verify that the payment fails gracefully when there is a network error
during the transaction.

Verify that a successful refund can be issued for a previously

completed payment.

Verify that sensitive payment information is securely transmitted and

stored.

Verify that a partial payment (less than the total amount) can be
processed successfully.
- Initiate the payment
process.

- Allow the payment to

reach the timeout threshold
(e.g., simulate a long delay
in processing the payment
Verify that the payment process handles a timeout scenario gracefully. on the server).

Verify that the payment gateway supports multiple currencies for

international transactions.
- Introduce errors like
server-side issues,
Verify that the payment gateway handles various errors and edge unexpected responses, or
cases gracefully. invalid API configurations.

Attempt to process a payment with an amount that exceeds the

maximum limit allowed by the payment gateway.

Attempt to process a payment with a negative payment amount,

indicating a refund request for an amount greater than the original
payment.
Check if the payment is happening even after the session expires.

Simulate a scenario where the payment gateway takes an unusually

long time to respond to a payment request.

Generate unexpected errors during the payment process (e.g., system

crashes, server issues) to evaluate the system's resilience and
recovery mechanisms.

Verify that the user gets information about unsuccessful payment.

- Verify user is able to add multiple card but from that only one card can
be make default.

Use various saved payment methods (e.g., credit cards, digital wallets)
to test the payment gateway's ability to process payments using stored
customer payment information.

Check if all the labels and boxes are visible.

Verify the payment gateway company logo or name.

Check if the credit card number is masked or not.

Verify that all the payment options are visible.

Check Entered cvc number is masked or not?

Verify Card number is accepted 16 digits

Verify cvv must be 3 digit except american express(4 digit).

Check if the color scheme matches the specifications.

Check if each of the payment options is selectable.

Verify that the page does not proceed to the payment page before all
the mandatory information is filled.

Verify that the correct currency is reflected on the page.

Check if the payment is not getting processed for null value or free
plan.
Verify if multiple payment options are not getting selected. Only one at
a time.

Check if the application page is not getting redirected to some other

page or link.
Check if the payment gateway does not crash if multiple users are
using it simultaneously.
 Expected Output Actual Output Test Browser
Column5 Column6 Column7
The payment is successfully processed, and
the user receives a confirmation message. The
payment status on the Stripe dashboard is
updated as successful.

The payment should fail, and the user should

be informed that the card number is invalid.
The payment should fail, and the user should
be informed that the card has expired.
The payment should fail, and the user should
be informed that there are insufficient funds.
The payment should fail, and the user should
be informed that there was a problem
processing the payment due to a network
issue.
The refund should be processed successfully,
and the user should receive a confirmation
message. The payment status on the Stripe
dashboard should be updated to reflect the
refund.
All sensitive payment information should be
transmitted and stored securely, following best
practices and complying with PCI-DSS
standards.
The payment should be processed
successfully for the partial amount, and the
user should receive a confirmation message.
The payment status on the Stripe dashboard
should be updated accordingly.

The payment process should display an

appropriate error message indicating that the
payment has timed out.

OR

pop-up appears if the session has expired.

The payment should be processed
successfully in the chosen currency, and the
user should receive a confirmation message.
The payment status on the Stripe dashboard
should show the correct currency.
The payment gateway should provide
appropriate error messages and handle the
errors without crashing or exposing sensitive
information.
The payment gateway should reject the
payment request and provide an appropriate
error message indicating that the payment
amount is too large.
The payment gateway should reject the
negative payment amount request and provide
an appropriate error message stating that the
amount is invalid.
The payment gateway should detect the
expired token or session and prevent the
payment process from proceeding. The user
should be prompted to log in again or re-
authenticate.
The payment gateway should have built-in
timeouts and retries to handle delays in
processing without causing disruptions or
leaving transactions in an unknown state.
The payment gateway should be able to
recover from unexpected errors, log relevant
information, and resume normal operation
without data loss.
If all the given details are valid and payment is
unsuccessful due to sever or any other issue
user should be get the textmessage or any
other way he/she should be notified.

- If plan is ongoing and in between card should

be expired(e.g Card expired on 08/2023 and
next due is comming on the 09/2023) so
payment should not be deducted and user
should be get text message or email.
User should be able to add multiple card but
only one card should be make default.
The payment gateway should retrieve and use
the saved payment methods securely,
processing the payments without any issues.

- User should be able to saved multiple card

details.
All the labels and boxes should be displayed
on the proper alignment.
Payment gateway company logo or name
should be displayed on the proper alignment.
- For the security every card details should be
in masked form.(Hidden)
- In the every forwarded mail or text message
card details should be send in masked form
only last 4 digits should be displayed.
E.g(xxxx-xxxx-xxxx-1890)
The payment gateway have multiple payment
options like By
- UPI
- By card And so on.
The cvv number should be displayed in the
encrypted mode.
Genarally card number should be accepted in
16 digits.
- CVV number should be in 3 digits.(All other
cards)
- American express card should be accepted 4
digit cvv number.

User should be able to select anyoption from

displayed options.
If any one field is remains to blank and that
field is mandatory then validation message
should be displayed.
On the payble amount field amount should be
exact displayed.
If subscription is free then user should not able
to do payment.
User should be able to select only one option
from multiple payment.
If user select any subscription then user
should be redirect on the payment gateway
page which is integrated.
If multiple user should be do simulteneously
payment then page should not be crash.
 Test Result Test Comments
Column8 Column9