merchant_guide:store-settings-paymentgateway
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
Previous revision | |||
— | merchant_guide:store-settings-paymentgateway [2011/01/13 18:56] (current) – [Supported Payment Gateways] earlyimpact | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Store Settings - Payment Gateway ====== | ||
+ | ===== Supported Payment Gateways ===== | ||
+ | |||
+ | Choose the payment gateway that you will be using with this store, and enter the corresponding credentials. | ||
+ | |||
+ | * Here is a [[payment-gateways: | ||
+ | * The **credentials** that you need to enter are different depending on the payment gateway that you will be using. | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * Each SubscriptionBridge store can only be associated with one payment gateway at this time | ||
+ | * Once a store has been associated with a payment gateway, this setting cannot be changed | ||
+ | * If you are setting up a **test store** to familiarize with SubscriptionBridge, | ||
+ | * [[: | ||
+ | * [[: | ||
+ | * [[: | ||
+ | |||
+ | ===== Credit Card Types ===== | ||
+ | |||
+ | You can specify the **credit card types** that are accepted by your store. This setting __only applies__ to stores that are using the SubscriptionBridge shopping cart ([[: | ||
+ | |||
+ | ===== Card Authorization Settings ===== | ||
+ | |||
+ | ==== Why authorize a card? ==== | ||
+ | |||
+ | When a subscription is created, there are many cases in which a payment is not processed. For example, a gym membership with a 7-day free trial, an online gaming Web site subscription with a "First Month Free" promotion, etc. | ||
+ | |||
+ | In all of these cases, most payment gateways do not by default check the validity of the credit card used for the subscription (e.g. Authorize.Net does not validate the card in this scenario). It does so only at the time the first subscription payment is processed, which could be well into the future. | ||
+ | |||
+ | To avoid creating a subscription for a customer that is using invalid credit card information (e.g. invalid card security code), SubscriptionBridge allows you to authorize the card and stop the customer from proceeding if an authorization is not received. | ||
+ | ==== Available card authorization options ==== | ||
+ | |||
+ | Specifically, | ||
+ | |||
+ | * **Zero Dollar Authorization (ZDA)** \\ This enables applications like SubscriptionBridge to check the validity of a credit card account without authorizing any specific amount. This is clearly the best way to accomplish this goal. The problem is that - as of February, 2010 - not all processors are capable of handling Zero Dollar Authorizations ([[http:// | ||
+ | * **$1.00 Authorization** \\ SubscriptionBridge will do an " | ||
+ | * **Full Transaction Amount** \\ SubscriptionBridge will do an " | ||
+ | |||
+ | Other notes on this feature: | ||
+ | |||
+ | * The reason why you can choose both a $1 authorization and a ZDA (Zero Dollar Authorization) is that if you know that your processor does not support ZDAs, it does not make sense to have SubscriptionBridge attempt a $0 authorization every time and then fail back onto a $1 authorization. In that scenario, it makes more sense to select $1 authorizations from the start. | ||
+ | * **PayPal Website Payments Pro** and **Authorize.net** are handled the same way with regard to this feature. | ||
+ | * This feature is not supported by **PayPal Express Checkout**. | ||
+ | |||
+ | ==== Which one to choose ==== | ||
+ | |||
+ | Even if there is no free trial, the first transaction is typically processed several hours after the subscription has been setup. When using Authorize.Net, | ||
+ | |||
+ | This can create an issue if: | ||
+ | |||
+ | * You are providing a service that can be immediately " | ||
+ | * You are concerned with the possibility that the customer' | ||
+ | |||
+ | In this scenario a ZDA or $1 authorization does not help in that the card might authorize for $1, but not for the full subscription amount (e.g. that amount may be over the customer' | ||
+ | |||
+ | In all other cases (the product/ | ||
+ | ==== Letting customers know ==== | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Among the " | ||
+ | |||
+ | The default message is rather generic. You can __tweak the message so that it matches your authorization settings__. | ||
+ | |||
+ | For example, if you setup your store to do a //Full Transaction Amount// authorization, | ||
+ | |||
+ | ==== Online banking and $1 authorizations ==== | ||
+ | |||
+ | Many banks automatically recognize $1 authorizations as temporary transactions that are going to automatically disappear from a customer' | ||
+ | |||
+ | For example, here is the information provided by a major bank such as Bank of America (this is current as of March, 2010): | ||
+ | |||
+ | {{: | ||
+ | |||
+ | |||
+ | ===== Related Articles ===== | ||
+ | |||
+ | * [[store-settings-general|General Information]] | ||
+ | * [[store-settings-paymentGateway|Payment Gateway]] | ||
+ | * [[store-settings-languages|Languages]] | ||
+ | * [[store-settings-countriesStates|Countries and States]] | ||
+ | * [[store-settings-taxes|Tax Settings]] | ||
+ | * [[store-settings-misc|Miscellaneous]] | ||
+ | * [[merchant_guide: |
merchant_guide/store-settings-paymentgateway.txt · Last modified: 2011/01/13 18:56 by earlyimpact