SagePay Repeats - Revision history

SarahK: /* Adding the SagePay Repeat Payments Payment Gateway */

2022-09-28T18:59:19Z

‎Adding the SagePay Repeat Payments Payment Gateway

SarahK: /* Adding the SagePay Repeat Payments Payment Gateway */

2022-09-07T21:01:15Z

‎Adding the SagePay Repeat Payments Payment Gateway

SarahK at 17:15, 30 March 2022

2022-03-30T17:15:52Z

SarahK at 18:46, 21 February 2022

2022-02-21T18:46:05Z

John at 15:05, 20 January 2016

2016-01-20T15:05:03Z

John at 08:41, 17 September 2013

2013-09-17T08:41:09Z

John at 17:02, 24 May 2011

2011-05-24T17:02:01Z

John: Created page with 'SagePay Repoeats 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…'

2011-05-24T17:01:48Z

Created page with 'SagePay Repoeats 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…'

New page

SagePay Repoeats 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.

@@ Line 21: / Line 21: @@
 # Go to the appropriate location for your version of WHMCS:
-#* For WHMCS 8.6 and later, go to '''Addons > [[Apps and Integrations|Apps & Integrations]]''' or '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations'''.
+#* For WHMCS 8.0 and later, go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations''' or '''Addons > [[Apps and Integrations|Apps & Integrations]]'''.
-#* For WHMCS 8.0 to 8.6, go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' and choose '''All Payment Gateways'''.
+#* For WHMCS 7.10 and earlier, go to '''Setup > Products/Services > [[Payment Gateways]]''' and choose '''All Payment Gateways'''.
 # Click '''SagePay Repeat Payments'''.
 # Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.

@@ Line 20: / Line 20: @@
 To set up the SagePay Repeat Payments payment gateway in WHMCS:
-# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Payment Gateways'''.
+# Go to the appropriate location for your version of WHMCS:
-# Choose the '''All Payment Gateways''' tab.
+#* For WHMCS 8.6 and later, go to '''Addons > [[Apps and Integrations|Apps & Integrations]]''' or '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations'''.
 # Click '''SagePay Repeat Payments'''.
 # Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.

@@ Line 1: / Line 1: @@
 {{gateways
 | type = token
@@ Line 5: / Line 16: @@
 | 3dsecure =yes
 }}
-<div class="docs-alert-success">
+=== Test Mode ===
-<span class="title">NOTE</span><br />
-We recommend using the newer [[SagePay_Tokens_v2|Sagepay Tokens v2]] module instead.
+You can use test mode to simulate payment processing without actually causing a transaction to occur. This can be useful to test your configuration.
-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.
+== Troubleshooting ==
-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.
+''N/A''
-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.
+{{modules}}

@@ Line 8: / Line 8: @@
 <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.
+We recommend using the newer [[SagePay_Tokens_v2|Sagepay Tokens v2]] module instead.
 </div>

@@ Line 6: / Line 6: @@
 }}
- '''NOTE:''' We recommend using the newer [[SagePay|Sagepay Tokens]] module instead as it supports more features.
+<div class="docs-alert-success">
+<span class="title">NOTE</span><br />
 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.

← Older revision		Revision as of 08:41, 17 September 2013
Line 1:		Line 1:
		+	{{gateways
		+	\| type = token
		+	\| onetime = yes
		+	\| recurring = yes
		+	\| 3dsecure =yes
		+	}}
		+
		+	'''NOTE:''' We recommend using the newer [[SagePay\|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.		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.