cancel
Showing results for 
Search instead for 
Did you mean: 

Handling recurring billing with CyberSource REST API — best practices?

Hello community,

I’m integrating  REST APIs for SR Blinds, a UK-based online retailer of bespoke window blinds. We have a subscription / membership product (e.g. maintenance plans or fabric replacement insurance) that needs to charge customers on a recurring monthly basis.

We currently use the CS Payments API (v2) for one-off purchases, but I’m unsure of the best path forward to support recurring billing. Specifically:

  • Does CS support native recurring / subscription billing workflows (via tokenization, customer vaulting, or subscription objects)?

  • If so, which API endpoints or service do you recommend (e.g. Recurring Billing, Token Management, Customer Profiles)?

  • How do you handle payment method updates (e.g. card expiration, card change) on recurring subscriptions?

  • Are there best practices you’d suggest (such as retry logic on failed charges, notification workflows, PCI scope concerns)?

Thanks in advance for any guidance or code samples.

AmniClave
Member
0 REPLIES 0