Recurring and Subscription Payment
Netvalve offers robust options for subscription and recurring payments for merchant.
How Subscription & Recurring Payments Work with Netvalve
Merchant can opt for below options to process subscription or recurring payments.
Option1: Rebill to process subscription / recurring payments
In this option, Credit card data is stored with the bank / processor. You can use Auth / Sale to setup a recurring transaction. Once Auth / Sale is approved, You can use netvalve transaction id to process rebills.
For each recurring/subscription cycle (e.g., monthly), initiate a payment request using netvalve transaction id using rebill API.
Step1: Auth / Sale API to setup the recurring transaction.
Step2: Use Rebill API to process the recurring / subscription.
https://docs.netvalve.com/#tag/Payment-Service/operation/rebillOperation
Option2: Netvalve Token to process subscription / recurring payments.
In this option, Credit card data is securely stored with Netvalve token vault. You need to request Netvalve team to enable this option. Once configured, you can create the token with Netvalve and use these tokens to process subscription or recurring payments.
To create netvalve tokens, you can use below optionns:
Option A: Token Create with verification.
Option B: Token Create without verification
Option C: Token Create as part of Auth / Sale
Once payment token is created with Netvalve then you can use the payment token to process the recurring or subscription transaction.
For more details refer to:
https://netvalve.atlassian.net/wiki/x/J4CiEg
For this option, merchant needs to follow CIT and MIT framework from Visa and MC. Refer to the link for more details:
https://netvalve.atlassian.net/wiki/x/B4AWG
Option3: Netvalve Gateway managed subscription / recurring (Coming Soon)
In this option, Netvalve gateway will be storing the credit card data and recurring schedule. Merchant will setup the recurring schedule as part of Auth / Sale or standalone subscription API.
Once created then netvalve gateway will be charging the customer based on the schedule.
Option | Credit Card Storage | Merchant Flow Steps | API Reference |
|---|---|---|---|
1 | Bank / Processor | Auth/Sale → use transaction ID for rebill | /sale,/rebill |
2 | Netvalve Token Vault | Request enablement → Token Create options then use token to process the payment. | /createToken, /sale or |
3 | Netvalve Token Vault | Set up schedule → automatic charges as part of Auth / Sale or standalone API | (To be announced; subscribe for updates) |