📃
Developer Docs
  • Overview
  • Integration Options
  • Webhooks
    • Build a webhook endpoint
    • Check signature
  • Getting Started
    • 1. Creating User Accounts
    • 2. User Account Types & Permissions
    • 3. Generate Access Tokens
    • 4. Choose Integration Options
    • 5. Securing Embedded UIs
      • 5a. Securing Embedded UIs Using HMAC (deprecated)
    • 6. Loading the frontend library
      • 6a. Preloading PayEngine Web-Component in SPA
    • 7. Custom styling the Web-Components
    • 8. Handling Callbacks from Web-Components
    • 9. Available Web-Components
    • 10. Available Webhooks
  • Merchant Onboarding
    • Overview
    • Integration Options
    • Onboarding/Payments Application Workflow
    • Embedded Onboarding UI
    • Merchant onboarding APIs
    • Partner's Onboarding UI
    • Merchant Lifecycle
    • Onboarding to Partner Relationships
  • Processing Payments
    • Introduction
      • Transaction Flow and Status
    • SecureFields JS
      • SecureFields Bank Account
      • Using tokens
    • Credit Card Form
    • Connect with Plaid
    • Connect Mailgun
    • 3D Secure
    • Payments API
    • Searching Transactions
    • Registering a cloud connected device
    • Apple Pay
      • Apple Pay in your native app
    • Google Payâ„¢
    • Level 2 and Level 3 Data
    • Fraud Prevention
    • Reporting
    • PCI Compliance
    • Address Verification Service (AVS) Check
    • Hosted Payments
      • Embedded Payments Session Integration
    • Tap to Pay
  • Card Account Updater
  • ORCHESTRATION SYSTEM
    • Orchestration Overview
    • Onboarding Orchestration
    • Transactions Orchestration
    • Omnicommerce Orchestration
    • Merchant Servicing
    • Universal Reporting
  • TOKENIZATION
    • Automatic Network Tokenization
    • Token Migration Process
  • DISPUTE MANAGEMENT
    • Retrieval Requests & Chargebacks
  • Certification
    • Partner Certification
  • Data Sharing
    • Secure Data Sharing with PayEngine
  • eCommerce Integration
    • PayEngine Payment Gateway for WooCommerce
Powered by GitBook
On this page
  1. ORCHESTRATION SYSTEM

Transactions Orchestration

PreviousOnboarding OrchestrationNextOmnicommerce Orchestration

Last updated 10 months ago

Introduction

The Transactions Orchestration system addresses the critical needs of Vertical SaaS entities in the digital payment domain. It offers an adaptable and robust framework, enabling these businesses to navigate transaction routing and data management across multiple processors effectively, thus ensuring autonomy over their payment data.

Importance of Data Ownership

Owning payment data is crucial for Vertical SaaS companies. It empowers them with the freedom to make data-driven decisions, tailor their services to specific market needs, and build a robust financial ecosystem around their offerings. Gateway Orchestration ensures that these companies aren't just processing transactions; they're accumulating valuable data that can be leveraged for strategic growth and customer insight.

Multi-Processor Routing

The ability to route transactions to various processors is a cornerstone feature of this system. This flexibility allows Vertical SaaS companies to:

  • Optimize transaction processing by choosing the most suitable processor based on factors like transaction type, geography, or cost.

  • Avoid vendor lock-in, providing the agility to switch processors as business needs or market conditions change.

  • Enhance resilience against processing downtimes or disruptions by diversifying payment processing options.

Examples and References

Gateway Orchestration extends its capabilities with features like secure fields and tokenization, as detailed in . These secure fields allow for the safe handling of sensitive payment data, ensuring compliance and security while enhancing user experience.

In terms of setting up and configuring gateways, this platform offers an intuitive approach. As outlined in, companies can easily set up predefined gateway configurations. This feature streamlines the process of adding new payment options and simplifies the management of multiple payment gateways. In cases where more custom routing is required, Vertical SaaS companies can use the custom router to be able to construct their own payloads with custom http request properties while maintaining PCI compliance by never directly touching credit card PAN and other PCI-compliant data (see section for more details).

Customizable Gateway Solutions

The Gateway Orchestration system is not a one-size-fits-all solution. It's highly customizable to meet the unique needs of each Vertical SaaS company. Whether it's configuring specific gateway parameters or integrating unique payment methods, the system is built to adapt and scale according to the diverse requirements of SaaS platforms.

Conclusion

For Vertical SaaS companies, the Gateway Orchestration system is more than just a payment processing tool; it's a strategic asset. It empowers these companies to own their payment data, enjoy the flexibility of multi-processor routing, and benefit from customizable, secure payment solutions. As the digital payments landscape continues to evolve, this system stands as a testament to innovation, security, and flexibility in the fintech space.

documentation on using tokens with secure fields
gateway configuration documentation
Using Tokens