Cloudy Wave Cloudy Wave
Let’s Talk
Let’s Talk

Cloudy Business Ops 3600 Knowledge Bases

Payment Gateway

A Payment Gateway is the service that securely processes electronic payments, such as credit cards, ACH transfers, or digital wallets, between customers, vendors, and the business. In Cloudy Business Ops 360, the Payment Gateway object stores configuration details and controls how payments are routed, authorized, and captured.

This object acts as the bridge between Cloudy Business Ops 360 and external financial institutions (e.g., Stripe, Authorize.Net), ensuring seamless and secure payment transactions.

Key Purpose of Payment Gateway

  1. Secure Transaction Processing:
     Stores encrypted credentials (API keys, client keys, etc.) for connecting to external gateways.
  2. Flexible Payment Methods:
     Supports ACH transfers, credit card payments, and specific card types.
  3. Business Entity Alignment:
     Associates gateways with a Legal Entity to ensure correct compliance, currency, and taxation.
  4. Customizable Payment Experience:
     Provides options to show invoice lines, set payment link expiration, and display terms & conditions.
  5. Multi-Environment Support:
     Includes both Test Mode and Live Mode for safe setup, testing, and production usage.

Use Cases in Cloudy Business Ops 360

  1. Customer Payments:
    • Configure multiple gateways (e.g., Stripe, Authorize.Net).
    • Accept payments via credit card or ACH depending on business needs.
  2. Gateway Selection:
    • Mark one gateway as Default for standard transactions.
    • Use different gateways for different legal entities or regions.
  3. Payment Links:
    • Generate customer-facing payment links that automatically expire after a set number of days.
    • Include invoice lines and terms & conditions to provide transparency.
  4. Testing and Deployment:
    • Configure and test payments in Test Mode before going live.
    • Switch to Live Mode for production transactions.
  5. Security and Compliance:
    • Store sensitive credentials in encrypted fields.
    • Capture digital signatures if required.

Example Scenario

  • Business Need: A company wants to process both credit card and ACH payments.
  • Configuration:
    • Gateway Type: Stripe
    • Enable Credit Card? = Checked
    • Enable ACH? = Checked
    • Default? = Checked
    • Status: Live Mode
  • Result: Customers can pay invoices securely using cards or ACH through Stripe. Expired links are controlled via Payment Link Expiration Days, and invoice lines are shown with terms & conditions.

Best Practices

  • Always set one Default gateway for streamlined operations.
  • Use Test Mode before switching to Live Mode to validate configurations.
  • Enable only the necessary payment methods (ACH, Credit Card) to simplify customer experience.
  • Link gateways to the correct Legal Entity for financial compliance.
  • Use Terms & Conditions to clearly define customer responsibilities and avoid disputes.