juspay/hyperswitch

research(connector-errors): When should we not save a card

Open

#1,599 opened on Jul 4, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Rust (42,690 stars) (4,676 forks)batch import
A-payment-methodsC-researchhelp wanted

Description

Currently we don't save a card when we receive an error from the connector

However This could be any error such as insufficient balance, card network down etc...

We should be saving cards if the card info is valid & it's a third party card...

However parsing this info from the connector errors is tricky.. for e.g if a payment was failed was it due to wrong card details or was it due to some other error....

We need to analyze the errors returned by connectors & find out where such knowledge/info can be extracted...

Contributor guide

Tech stack
rust
Domain
backend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
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.
needs investigation
Prerequisites
Rustpayment processing concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the connector error handling code in Hyperswitch, focusing on how errors are categorized. Look at the router module where payment flows are processed. Identify patterns in connector responses that distinguish between card validation errors and transient errors. Propose a method to extract whether card details are valid from error messages.