New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

Agentic AI


  • Chargebee Copilot
  • Catalog Setup Assistant
  • MCP Servers

Developer Resources


  • Developer Resources Overview
  • API Explorer
  • Articles and FAQ

Chargebee Apps


  • Chargebee Apps CLI Developer Guide

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Overview
  • Use Cases
  • Setting up Usage Based Billing
  • Usage Alerts
  • Prepaid credits
  • Mid-term Subscription Changes
  • FAQs

Invoices and Credit Notes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

E-Invoicing


  • Overview
  • Enabling E-Invoicing

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Mobile SDKs and Wrappers
  • Articles and FAQ

Site Configuration


  • Add Users & Assign Roles
  • Chargebee Notifications
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • OAuth Apps
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel Subscriptions (Legacy)

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • E-Invoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Subscriptions
  3. Articles and FAQ
  4. APIs
  1. Billing
  2. Subscriptions
  3. Articles and FAQ
  4. APIs

Secondary Payment source ID via API

Summary

This article explains how to retrieve the payment source ID of a secondary payment method (not marked as a BACKUP) which is applied while creating a subscription via API.

By using the Create subscription api, you can retrieve a transaction ID from the response under Linked Payments. This transaction ID can then be used with the Retrieve Transaction API to extract the payment source ID and override the billing profile if needed.

Description

When creating a subscription with a secondary payment method via API, you might need to extract the payment source ID without setting the method as a ‘backup'.

Here's how you can achieve this through Chargebee's API.

Create Subscription API Response: When you create a subscription using the Create Subscription API with a secondary card, the response will include a linked_payments section. This section contains the Transaction ID associated with the payment. Example Response:

"linked_payments": [
{
"txn_id": "txn_16BSRVUZShRX53j83",
"applied_amount": 55000,
"applied_at": 1736495808,
"txn_status": "success",
"txn_date": 1736495808
}
]

Retrieve Payment Source ID: Use the transaction ID obtained from the previous step with the Retrieve Transaction API to get the payment source ID of the secondary payment method.

Important Notes:

  • This method works effectively for regular subscriptions where payments are applied immediately.
  • For trial or $0 subscriptions:
    • No charge is applied until the end of the trial period, meaning the Create Subscription API will not generate a transaction ID for these subscriptions.
    • To retrieve the payment source details in such cases, you can use the payment gateway's API.
    • Implement the 3D Secure (3DS) flow using the gateway's JavaScript and server APIs to fetch transaction details.

Related Articles

Unable to create a subscription: "Cannot create the subscription as there is no valid card on file". How do I proceed?

Was this article helpful?