Cloudy Revenue Inventory Knowledge Base

Payment Gateway

The Payment Gateway object stores and manages payment gateway configurations used to securely process customer and vendor payments within Cloudy Inventory. It acts as the integration layer between Cloudy Inventory and external payment providers such as Stripe and Authorize.Net.

The Payment Gateway object allows administrators to configure payment processing settings, supported payment methods, API credentials, processing fees, payment link behavior, invoice display options, and security features. It is referenced by the Payment and Transaction objects to authorize, capture, settle, and refund payments.

Use Cases in Cloudy Inventory

1. Configure Online Payment Processing

Configure payment gateway credentials and enable customers to securely pay invoices online using supported payment providers.

2. Generate Secure Payment Links

Automatically generate secure payment links from Invoices or Payments, allowing customers to complete payments without logging into Salesforce.

3. Support Multiple Payment Methods

Allow customers to pay using supported payment methods such as:

• Credit Card
• ACH / Direct Debit

Supported card types include:

• Visa
• MasterCard
• American Express
• Discover
• JCB
• Diners Club

4. Configure Processing Fees

Automatically calculate processing fees using:

• Percentage of Transaction Amount
• Flat Amount

Optionally create Processing Fee line items on Quotes and Invoices.

5. Configure Payment Link Expiration

Control how long generated payment links remain active by configuring expiration days.

6. Enable Test and Production Modes

Switch between:

• Test Mode
• Live Mode

This allows administrators to validate gateway integrations before processing live customer payments.

7. Enable Digital Signature

Require customers to provide an electronic signature before completing online payments.

8. Display Invoice Information

Configure whether invoice lines, processing fee messages, and terms & conditions are displayed on the online payment page.

9. Secure Payment Credentials

Store encrypted API credentials including:

• API Login ID
• Client Key
• Public Key
• Secret Key
• Transaction Key

to securely authenticate with the payment provider.

Example Business Scenario

• Cloudy Motors Ltd. uses Stripe as its default Payment Gateway.
• The administrator creates a Payment Gateway record and configures the Stripe API credentials.
• Credit Card and ACH payments are enabled.
• The gateway is configured to charge a 2.90% processing fee for Credit Card payments.
• Payment links are configured to expire after 7 days.
• E-Signature is enabled for customer authorization.
• Invoice Lines and Terms & Conditions are displayed on the online payment page.
• When Test Customer Inc. receives an Invoice, a secure payment link is generated automatically.
• The customer opens the payment link, selects Credit Card, enters the card details, signs electronically, and completes the payment.
• Cloudy Inventory creates the corresponding Payment, Transaction, and Allocation records automatically and updates the Invoice status.

Best Practices

• Configure one Default Payment Gateway for each Legal Entity.
• Test gateway integration in Test Mode before switching to Live Mode.
• Store API credentials securely and update them whenever provided by the payment provider.
• Enable only the payment methods accepted by your business.
• Configure payment link expiration to improve security.
• Enable E-Signature for high-value or legally binding transactions.
• Configure processing fees carefully and communicate them clearly using the Processing Fee Message.
• Regularly verify API credentials after gateway updates or password changes.
• Restrict administrative access to Payment Gateway configuration records.
• Periodically review gateway transactions, settlements, and processing fees to ensure accurate payment reconciliation.

SEE ALSO :

_______👉Payment Gateway Configuration