Project

General

Profile

Actions

Task #814

open

Epic #786: Square Payment Gateway Integration

Feature #811: Customer Management

Duplicate Handling

Added by Redmine Admin about 2 months ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
04/22/2026
Due date:
% Done:

0%

Estimated time:

Description

Before creating a new customer, check if a Square customer already exists for the user. Prevent duplicate records using email or stored mapping.

Actions #1

Updated by Deeksha Singh about 1 month ago

Module: Duplicate Customer Handling (Square)
TC_ID_DUPLICATE_01
Title: Verify system checks existing customer before creating new one
Preconditions: Customer already exists in Square
Steps:

Initiate customer creation
Check API flow
Test Data: Existing email/user
Expected Result: Existing customer is found, no new customer created

TC_ID_DUPLICATE_02
Title: Verify duplicate customer is not created for same email
Preconditions: Customer exists with same email in Square
Steps:

Attempt to create customer again
Test Data: Same email
Expected Result: No duplicate customer created in Square

TC_ID_DUPLICATE_03
Title: Verify stored mapping is used to prevent duplicate
Preconditions: Customer ID already stored in DB
Steps:

Initiate payment or customer creation
Test Data: Same user
Expected Result: Existing customer_id is reused

TC_ID_DUPLICATE_04
Title: Verify new customer is created if no existing record found
Preconditions: No customer exists in Square or DB
Steps:

Initiate customer creation
Test Data: New email/user
Expected Result: New customer is created successfully

TC_ID_DUPLICATE_05
Title: Verify handling of partial duplicate data (same email, different user)
Preconditions: Same email used for different user
Steps:

Attempt to create customer
Test Data: Same email, different user_id
Expected Result: System handles correctly (reuse or restrict based on logic), no unwanted duplicate

Actions

Also available in: Atom PDF