Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(connector): [Stripebilling] add record back support for stripebilling #7561

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

NISHANTH1221
Copy link
Contributor

@NISHANTH1221 NISHANTH1221 commented Mar 18, 2025

Type of Change

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

Description

Add support for record back flow for Stripebilling.

What is record back flow ?
After payment is retried by revenue recovery, we need to update the billing processor invoice.

Stripebilling flow
Call the api end point in the connector integration to update the invoice status.

Additional Changes

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

Motivation and Context

How did you test it?

This can only be tested in local since the entire recovery flow is not complete. Tested locally by triggering the connector integration manually.
Here are the local testing logs :

Request
Screenshot 2025-03-19 at 8 22 57 PM

Response
Screenshot 2025-03-19 at 8 23 07 PM

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

@NISHANTH1221 NISHANTH1221 self-assigned this Mar 18, 2025
@NISHANTH1221 NISHANTH1221 requested a review from a team as a code owner March 18, 2025 16:29
Copy link

semanticdiff-com bot commented Mar 18, 2025

@NISHANTH1221 NISHANTH1221 added the A-connector-integration Area: Connector integration label Mar 18, 2025
srujanchikke
srujanchikke previously approved these changes Mar 20, 2025
@hyperswitch-bot hyperswitch-bot bot requested a review from a team as a code owner March 20, 2025 10:33
@hyperswitch-bot hyperswitch-bot bot added the M-api-contract-changes Metadata: This PR involves API contract changes label Mar 20, 2025
@NISHANTH1221 NISHANTH1221 removed the M-api-contract-changes Metadata: This PR involves API contract changes label Mar 20, 2025
@hyperswitch-bot hyperswitch-bot bot added the M-api-contract-changes Metadata: This PR involves API contract changes label Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-connector-integration Area: Connector integration api-v2 M-api-contract-changes Metadata: This PR involves API contract changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants