📖
Inyo Developer Portal
  • API REFERENCES
    • Payments Gateway v2
      • Getting started
      • Background
        • System architecture
        • Gateway environment settings
      • Authentication Methods
      • Environments
      • Technical Resources
      • Mitigating Fraud
      • APIs
        • Tokenizing cards
        • Payment
          • Pull Transaction
            • Handling AVS / CVC
            • Handling 3D secure
          • Push Transaction
          • Pull and push in one step
          • Capture
          • Refund
          • Void
          • Get a payment
          • Get a list
        • Webhooks
        • Domain tables
          • Response Code
          • Payment Status
        • Test data
          • Cards
    • Remittances
      • Getting Started
      • Authentication
      • Data Population
        • Country
        • State
        • Banks
        • Payers
        • Settlement Rates
      • Sender
        • Sender Object
        • Register a Sender
        • User Agreement
        • Get Sender by ID
        • Sender Verification
          • ID Documents
            • Expired ID Documents
          • KYC Status
          • KYC Using Widget
          • KYC Using API
            • Get KYC fields
            • Update KYC Information
            • Initiate KYC
            • Get KYC Information
          • Sender Tier Upgrade
        • Sender ID Information
      • Funding Account
        • Add Funding Account
          • OAuth Integration
        • Funding Account Object
        • Get Funding Account
        • Delete Funding Account
      • Recipient
        • Recipient Object
        • Add a Recipient
        • Get Recipient Details
        • Update Recipient
        • Recipient Document
      • Recipient Account
        • Recipient Account Object
        • Add a Recipient Account
        • Get Recipient Account
        • Get Account Information
      • Transaction
        • Transaction Object
        • Get Transaction Limits
        • Create a Transaction
          • 3DS Verification
          • Bonus/Discount
        • Get Transaction Details
        • Cancel Transaction
        • Delivery Request
        • Self-Payout
        • Transaction Invoice
      • Webhooks
        • Subscriptions
          • Subscribe
          • List Subscriptions
          • Pause Subscriptions
          • Remove Subscription
        • Integration
        • Events
      • Widget
        • Widget v1.0
          • Widget v1.0 Types
        • Widget v2.0
      • SANDBOX
        • Test Values
          • Geo-Fencing
          • Sender Verification
          • Funding Account
          • Transaction
  • USE CASE
    • Remittance
Powered by GitBook
On this page
  1. API REFERENCES
  2. Payments Gateway v2
  3. Background

System architecture

1. Microservices Architecture

Inyo gateway is built on a microservices architecture, where each functionality is encapsulated in a standalone service, compiled and tested and deployed automatically. This approach ensures:

  • Modular development and deployment.

  • High scalability to handle varying workloads.

  • Fault isolation, where issues in one service do not affect others.

Each microservice is containerized, enabling consistent environments and seamless deployment across different platforms

2. Payment Router Mechanism

A central component of the architecture is the Payment Router, which dynamically selects the optimal payment route based on:

  • Transaction Type: Determines whether the operation is a pull or push.

  • Payment Method: Identifies the payment type (e.g., ACH, Card, or different payouts formats).

  • Currency: Considers the currencies of the origin and destination countries to ensure compatibility and compliance with local regulations.

The router ensures that every transaction is processed efficiently and routed to the appropriate provider, optimizing performance and reliability.

3. Provider-Specific Microservices

To cater to the diverse requirements of payment providers, each provider has its own dedicated microservice. These microservices:

  • Implement the specific rules and standards mandated by their respective providers.

  • Manage provider-specific APIs, ensuring seamless integration.

  • Are independently deployable, allowing for quick updates and scaling.

4. Integration with Payment Router

The provider microservices are tightly integrated with the Payment Router, making them readily available for the gateway to:

  • Offer a wide range of payment integrations to client banks.

  • Dynamically scale as new providers are added, enhancing the system’s flexibility.

This tightly coupled design ensures that the gateway remains extensible and capable of supporting future integrations without disrupting existing services.

5. Scalability and Security

The architecture leverages modern design principles to ensure:

  • Horizontal Scalability: Services can scale independently based on load.

  • Enhanced Security: Each microservice operates in an isolated environment, reducing vulnerabilities.

This architecture makes Inyo gateway a powerful tool for businesses, enabling seamless financial transactions while maintaining the highest standards of performance and reliability.

PreviousBackgroundNextGateway environment settings

Last updated 4 months ago