[FEATURE]: [Square] Use `connector_request_reference_id` as reference to the connector · juspay/hyperswitch#2318

2023-09-22T13:24:00.000Z

### :memo: Feature Description - We transmit our reference id from Hyperswitch to the connector, enabling merchants to subsequently locate the payment within the connector dashboard. - Presently, there is a lack of uniformity in this process, as some implementations employ `payment_id` while others utilize `attempt_id`. - This inconsistency arises from the fact that `payment_id` and `attempt_id` correspond to two distinct entities within our system. ### :hammer: Possible Implementation - To mitigate this confusion, we've introduced a new field called `connector_request_reference_id` in our RouterData. - This id should replace them as a reference id to the connector for payment request. - One might need to have exposure to api docs of the connector for which it is being implemented. - You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/2052 :bookmark: Note : All the changes needed should be contained within `hyperswitch/crates/router/src/connector/` ### :package: Have you spent some time checking if this feature request has been raised before? - [X] I checked and didn't find a similar issue ### :package: Have you read the Contributing Guidelines? - [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md) ### :sparkles: Are you willing to submit a PR?

(15 commentaires) (0 réactions) (0 assignés)Rust (4 676 forks)batch import

A-connector-integrationC-featuregood first issuehacktoberfest

Métriques du dépôt

Stars: (42 690 stars)
Métriques de merge PR: (Merge moyen 6j 22h) (213 PRs mergées en 30 j)

Description

:memo: Feature Description

We transmit our reference id from Hyperswitch to the connector, enabling merchants to subsequently locate the payment within the connector dashboard.
Presently, there is a lack of uniformity in this process, as some implementations employ payment_id while others utilize attempt_id.
This inconsistency arises from the fact that payment_id and attempt_id correspond to two distinct entities within our system.

:hammer: Possible Implementation

To mitigate this confusion, we've introduced a new field called connector_request_reference_id in our RouterData.
This id should replace them as a reference id to the connector for payment request.
One might need to have exposure to api docs of the connector for which it is being implemented.
You can check this PR for further reference https://github.com/juspay/hyperswitch/pull/2052

:bookmark: Note : All the changes needed should be contained within hyperswitch/crates/router/src/connector/

:package: Have you spent some time checking if this feature request has been raised before?

I checked and didn't find a similar issue

:package: Have you read the Contributing Guidelines?

I have read the Contributing Guidelines

:sparkles: Are you willing to submit a PR?

Guide contributeur

Direction de recherche: Inspectez le code du connecteur Square dans `crates/router/src/connector/square` et remplacez les références à `payment id` ou `attempt id` par `connector request reference id` dans les demandes de paiement. Référez vous à la PR liée (#2052) et à la documentation de l'API Square pour le mappage correct des champs.
Stack technique: rust
Domaine: backend
Type d'issue: Fonctionnalité
Difficulté: 2
Temps estimé: 1-3 heures
Statut d'activité: Active
Clarté: Claire
Prérequis: GitRust
Accessibilité débutant: 75