Difference between revisions of "Stripe"
(Stripe documentation) |
m |
||
| Line 10: | Line 10: | ||
The WHMCS official Stripe module was introduced in WHMCS 7.1. Stripe remotely stores a client's credit card, without storing the details within WHMCS. | The WHMCS official Stripe module was introduced in WHMCS 7.1. Stripe remotely stores a client's credit card, without storing the details within WHMCS. | ||
| − | Setup | + | ==Setup== |
Stripe uses the API keys found here. Start by activating the module in Setup > Payments > Payment Gateways. The module is listed as Stripe. | Stripe uses the API keys found here. Start by activating the module in Setup > Payments > Payment Gateways. The module is listed as Stripe. | ||
| Line 17: | Line 17: | ||
Ensure the "Disable Credit Card Storage" option in not enabled. Find this on the Security tab of General Settings. | Ensure the "Disable Credit Card Storage" option in not enabled. Find this on the Security tab of General Settings. | ||
| − | How does it work? | + | ===How does it work?=== |
| − | The client does not leave WHMCS | + | # The client does not leave WHMCS. |
| − | The module uses stripe.js for payments and card updates. | + | # The module uses stripe.js for payments and card updates. |
| − | The module uses the Stripe API for refunds and obtaining transaction information | + | # The module uses the Stripe API for refunds and obtaining transaction information. |
| − | A customer can edit their card at any time from the client area | + | # A customer can edit their card at any time from the client area. |
| − | An admin with access can request a payment for a token at any point | + | # An admin with access can request a payment for a token at any point. |
| − | Why does it avoid PCI compliance? | + | ===Why does it avoid PCI compliance?=== |
| − | No cardholder data ever touches or passes through your Network, Server or WHMCS System. | + | # No cardholder data ever touches or passes through your Network, Server or WHMCS System. |
| − | No cardholder data is ever retained or stored on your Network, Server or WHMCS system. | + | # No cardholder data is ever retained or stored on your Network, Server or WHMCS system. |
| − | Migration from a 3rd Party Module | + | ===Migration from a 3rd Party Module=== |
The WHMCS module uses the Stripe "cus_" reference to capture payments - e.g. cus_9MvIb7UlgJfJTn. Find this on the Credit Card Information screen from the Client Summary. The WHMCS module can replace any existing Stripe module that uses the same reference. Activate the WHMCS Module as above. Then, deactivate the existing Stripe module, whilst selecting the official module as a replacement. | The WHMCS module uses the Stripe "cus_" reference to capture payments - e.g. cus_9MvIb7UlgJfJTn. Find this on the Credit Card Information screen from the Client Summary. The WHMCS module can replace any existing Stripe module that uses the same reference. Activate the WHMCS Module as above. Then, deactivate the existing Stripe module, whilst selecting the official module as a replacement. | ||
| − | Special Notes for Transaction Fees | + | ===Special Notes for Transaction Fees=== |
Stripe provides the fee for transactions in the currency of the account. This can be different from the currencies configured in WHMCS. For the fees to be available, the currency of the Stripe account should be available in WHMCS. | Stripe provides the fee for transactions in the currency of the account. This can be different from the currencies configured in WHMCS. For the fees to be available, the currency of the Stripe account should be available in WHMCS. | ||
Revision as of 10:32, 7 November 2016
Contents
Supported Features
| Type | One Time | Recurring | Refunds | 3D Secure |
|---|---|---|---|---|
| Token | Yes | Yes | Yes | No |
| Remote Update Card | Remote Delete Card | AddPayMethod API |
|---|---|---|
| Yes | Yes | No |
The WHMCS official Stripe module was introduced in WHMCS 7.1. Stripe remotely stores a client's credit card, without storing the details within WHMCS.
Setup
Stripe uses the API keys found here. Start by activating the module in Setup > Payments > Payment Gateways. The module is listed as Stripe.
When active, enter the Secret and Publishable API Keys and click Save Changes. Stripe is now active for clients to use. Ensure the "Disable Credit Card Storage" option in not enabled. Find this on the Security tab of General Settings.
How does it work?
- The client does not leave WHMCS.
- The module uses stripe.js for payments and card updates.
- The module uses the Stripe API for refunds and obtaining transaction information.
- A customer can edit their card at any time from the client area.
- An admin with access can request a payment for a token at any point.
Why does it avoid PCI compliance?
- No cardholder data ever touches or passes through your Network, Server or WHMCS System.
- No cardholder data is ever retained or stored on your Network, Server or WHMCS system.
Migration from a 3rd Party Module
The WHMCS module uses the Stripe "cus_" reference to capture payments - e.g. cus_9MvIb7UlgJfJTn. Find this on the Credit Card Information screen from the Client Summary. The WHMCS module can replace any existing Stripe module that uses the same reference. Activate the WHMCS Module as above. Then, deactivate the existing Stripe module, whilst selecting the official module as a replacement.
Special Notes for Transaction Fees
Stripe provides the fee for transactions in the currency of the account. This can be different from the currencies configured in WHMCS. For the fees to be available, the currency of the Stripe account should be available in WHMCS.