Stripe Payment Gateway - Configuration Requirements
- Persia Xenopoulou (Deactivated)
- Former user (Deleted)
- p_demou (Deactivated)
Back to Stripe Payment Gateway Main Page
Learn to set up Stripe Payment Gateway related business processes and rules.
 Mandatory Configuration: Links to manuals of Stripe Payment Gateway Configuration modules that are required for the module to work correctly
 Related Configuration: Links to manuals of Configuration modules other than the Stripe Payment Gateway's that offer additional functionality or are required for the module to work correctly
 Optional Configuration: Links to manuals of the Stripe Payment Gateway Configuration modules that offer additional functionality but are not required for the module to work correctly
Mandatory Configuration
The following modules must be configured to use the Stripe Payment Gateway
| Module Name | Manual | Description |
|---|---|---|
Payment Gateway Provider | Configuring the Stripe Payment Gateway Provider | Define the parameters which are needed to communicate with each payment gateway. |
Related Configuration
The following modules are related to but are not a part of, Stripe Payment Gateway. Such entities either:
- Must be configured accordingly to be able to start using Stripe Payment Gateway module (Configuration Type = Mandatory)Â
OR - May be configured to use Stripe Payment Gateway module at its full capacity (Configuration Type = Optional)
| Module Name | Manual | Description | Configuration Type |
|---|---|---|---|
Financial Transaction Payment Methods | Configuring Payment Methods | Create a payment method that will be used to identify payments that need to be handled by Stripe. The Payment Method created above should be added to Provider Payment Methods. In this way, the System will know that any payment made with the specific Payment Method, it will be handled by Stripe | Mandatory |
| Financial Transaction Types | Financial Transaction Types | Configure different Financial Transaction Types for Payment and Payment Cancellation Classifications to easily identify/separate them. The Payment Cancellation Type must then be added to Provider Payment Cancellation Causes. In this way, the System will know that any Payment Cancellations of these type must be handled by Stripe | Optional |
| Accounts Receivable Payment Preferences | Payment Preference | Configure Payment Preferences that will be related to Stripe and will be used when registering an Accounts Receivable and making a Payment to an account that should be handled via Stripe | Mandatory |
| Accounts Receivable Classifications | Accounts Receivable Classification | Configure Classifications that can be used in the Wallet Definitions Auto Top Up Rules | Optional |
| Wallet Definitions | Wallet Definitions | Configure Auto Top Up Rules if you would like the Wallet to be automatically topped up | Optional |
| Automatic Payment Run Definitions | Automatic Payment Run Definitions | Used to identify unsettled bills, wallets that need Top-up and payments that have been cancelled and create Stripe Payment Gateway Requests | Mandatory |
Optional Configuration
The following entities are available and can be configured under Stripe Payment Gateway.  A working CRM.COM model can exist without them being configured.
| Module Name | Manual | Description |
|---|---|---|
| Financial Transaction Types | Financial Transaction Types | Financial Transaction Types having a Cancellation Classification are used in the Stripe Payment Gateway Provider to determine when refunds should be triggered to credit a Stripe registered cards. When a Stripe payment is cancelled in CRM.COM, the money must be refunded (paid back to the card). |
Related Areas
Filter by label
There are no items with the selected labels at this time.