Difference between revisions of "SagePay Repeats"
From WHMCS Documentation
| Line 6: | Line 6: | ||
}} | }} | ||
| − | + | <div class="docs-alert-success"> | |
| − | + | <span class="title">NOTE</span><br /> | |
| + | We recommend using the newer [[SagePay|Sagepay Tokens]] module instead as it supports more features. | ||
| + | </div> | ||
SagePay Repeats is the remote storage version of the SagePay module where card details are stored on SagePay's server for rebilling rather than in your WHMCS database. | SagePay Repeats is the remote storage version of the SagePay module where card details are stored on SagePay's server for rebilling rather than in your WHMCS database. | ||
Revision as of 15:05, 20 January 2016
Supported Features
| Type | One Time | Recurring | Refunds | 3D Secure |
|---|---|---|---|---|
| Token | Yes | Yes | No | Yes |
| Remote Update Card | Remote Delete Card | AddPayMethod API |
|---|---|---|
| No | No | No |
NOTE
We recommend using the newer Sagepay Tokens module instead as it supports more features.
SagePay Repeats is the remote storage version of the SagePay module where card details are stored on SagePay's server for rebilling rather than in your WHMCS database.
By using the Repeats option the PCI Compliance requirements you have to meet are lessened, and the risks in accepting and storing credit card details on your server are completely negated.
The client's card details are sent to SagePay upon their first payment and stored and can be charged at a later date. To update their credit card details the client would need to pay an invoice using the new card details and they will be updated at SagePay at the same time.