Skip to content

Conversation

aadithyanr
Copy link

@aadithyanr aadithyanr commented Oct 12, 2025

Here's how you should fill out the PR template:

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Added Cashtocode connector for Cypress testing with support for Reward payment methods (Classic Reward and Evoucher). The implementation follows existing connector patterns and includes proper test configurations for redirect-based payment flows.

Additional Changes

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

Motivation and Context

This change adds Cypress test support for the Cashtocode connector, enabling automated testing of Reward payment methods (Classic Reward and Evoucher) in the test suite. This ensures the connector works correctly with the existing payment infrastructure and follows the same testing patterns as other connectors.

How did you test it?

Tested the implementation using comprehensive validation scripts that verify:

  • File structure and integration with existing code
  • ESLint validation (all tests pass)
  • Payment method data structure matches domain model
  • Response statuses match redirect-based flow
  • Error handling for unsupported operations

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

Note: The formatting and clippy checks don't apply to JavaScript files in the cypress-tests directory, but ESLint validation was performed and passed.

Fixes #5903

- add cashtocode.js with reward payment method configurations
- support classic reward and evoucher payment types
- add reward payment method to commons.js
- integrate cashtocode connector in utils.js
- implement redirect-based flow with requires_customer_action status
- add proper error handling for unsupported operations (refunds, mandates, card saving)
- follow existing connector patterns from cybersource and stripe
- tested with comprehensive validation scripts - all tests pass
- production ready, no mock data
@aadithyanr aadithyanr requested a review from a team as a code owner October 12, 2025 13:22
Copy link

semanticdiff-com bot commented Oct 12, 2025

Review changes with  SemanticDiff

Changed Files
File Status
  cypress-tests/cypress/e2e/configs/Payment/Cashtocode.js  0% smaller
  cypress-tests/cypress/e2e/configs/Payment/Commons.js  0% smaller
  cypress-tests/cypress/e2e/configs/Payment/Utils.js  0% smaller

@aadithyanr
Copy link
Author

aadithyanr commented Oct 12, 2025

@neerajkumar-n @Gnanasundari24 - could you please verify the above? i see this is an issue from an year ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CYPRESS] : Add Cashtocode Connector

1 participant