juspay/hyperswitch

[FEATURE] Enhance Developer experience by enabling test card payments without need of signing up on Stripe (or any other payment processor)

Open

#727 opened on Mar 9, 2023

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (42,690 stars) (4,676 forks)batch import
C-featureS-awaiting-triagehelp wanted

Description

Feature Description

Problem Statement: Currently, developers, who are trying to integrate Hyperswitch and test basic payments flow, need to have credentials from one of the connectors (payment processors) like Stripe by signing up with them. Since the sign-up and the subsequent tweaking required at these connectors can be slightly long drawn, developers find it challenging to simulate and experience a simple payment on Hyperswitch.

Solution Creating a dummy test connector at Hyperswitch's end could solve the above challenge of simulating a simple payments and also enable developers to simulate various other flows such as refunds, webhooks, etc.

Feature Description: The dummy test connector should be able to accept different test card numbers to simulate the following payments scenarios for card payments (Non 3DS): a) Payment success b) Payment failure

  • Declined by the gateway
  • Expired card or expiration date does not match
  • Insufficient funds
  • Declined due to poor risk score
  • CVV / Security code did not match
  • Declined by issuing bank
  • Gateway Timeout

Since this is a Non-3DS card payments, the dummy connector should be able to confirm the payment status in the response object of the payments/confirm API call without triggering the redirection flow.

Possible Implementation

Two steps in implementing the solution:

  1. Mock server implementation for the dummy connector for all the payments endpoints
  2. Integrating Hyperswitch with the created dummy connector for all the payments endpoints

Have you spent some time to check if this feature request has been raised before?

  • I checked and didn't find similar issue

Have you read the Contributing Guidelines?

Are you willing to submit a PR?

No, but I'm happy to collaborate on a PR with someone else

Contributor guide

Tech stack
rust
Domain
backendapitesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingHTTP server basicsPayment processing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Start by studying existing connector implementations in Hyperswitch, particularly in the crates/router/src/connector directory. Understand the pattern for integrating a payment processor, including API calls and response handling. Then design a dummy connector that returns predefined responses based on test card numbers. Implement a mock server in Rust that simulates payment success, failure with various reasons, and gateway timeouts. Finally, integrate this dummy connector into Hyperswitch by adding the necessary configuration and routing logic. Refer to the issue comments for any additional details or maintainer hints.