Type of Change

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

Description

Description

This PR introduces the invoice table along with supporting models, queries, schema definitions, and storage interfaces.
The goal is to enable subscription billing and payment tracking by storing invoices linked to merchants, customers, subscriptions, and connectors.

Key Features

• New Invoice table with fields for subscription, connector, merchant, customer, amount, currency, status, and metadata.
• Added InvoiceStatus enum to represent invoice lifecycle stages (e.g., PendingPayment, PaymentSucceeded, InvoicePaid, etc.).
• Implemented Diesel models: InvoiceNew, Invoice, InvoiceUpdate.
• Added storage query methods:
  • Insert new invoice
  • Find invoice by ID
  • Find invoice by merchant + invoice ID
  • Update invoice entry
• Integrated with router storage interface (InvoiceInterface).
• Added migrations:
  • up.sql: creates invoice table and indexes (payment_intent_id, subscription_id, merchant_id + customer_id).
  • down.sql: drops indexes and table.

Motivation and Context

• Provides a foundation for subscription billing system in Hyperswitch.
• Supports payment reconciliation and invoice lifecycle tracking.
• Enables robust query and update flows for invoices tied to subscriptions.

Schema Details

Table: invoice

• id (PK)
• subscription_id
• connector_subscription_id
• merchant_id
• profile_id
• merchant_connector_id
• payment_intent_id (unique)
• payment_method_id
• customer_id
• amount
• currency
• status
• provider_name
• metadata
• created_at
• modified_at

Indexes

• idx_payment_intent_id
• idx_subscription_id
• idx_merchant_customer

How did you test it?

This can't be tested as this is only creation of tables and their respective storage models.

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