​
Paysight Billing Logic

This document explains how Paysight handles billing processes from product setup through payment processing, retries and invoicing. It is intended for merchants, finance users and developers who need to understand Paysight’s billing workflows and configuration options.

​
Overview

Paysight’s billing logic manages how subscriptions and one-time charges are processed, routed, retried, and reported. It connects business rules with the underlying payment infrastructure, optimizing approval rates, payment resilience and revenue collection. Key components include:
  • Subscriptions and Products: Define what customers buy, how often they are billed, pricing, and discounts.
  • Payment Processing: Transactions are routed through Merchant ID (MID) Groups to multiple processors for higher approval.
  • Retry and Failover: Automated retries and fallback routing increase collection success.
  • Invoicing and Reporting: Paysight generates invoices and provides data for reconciliation and finance teams.

​
Core Concepts

​
Subscriptions and Billing Cycles

  • Subscriptions can be recurring (monthly, yearly) or one-time.
  • Billing occurs on defined schedules linked to subscriptions.
  • Changes to subscription status (pause, cancel) affect billing events.

​
Products and Pricing

  • Products define pricing tiers, currency and billing intervals.
  • Discounts, taxes and prorations are applied per business rules.
  • Each product links to the billing engine for payment attempts.

​
MID Groups and Payment Routing

  • Transactions are routed dynamically through MID Groups that bundle multiple Merchant IDs.
  • This optimizes approval rates by selecting the best MID based on card type, geography, and processor capacity.
  • Failover routing retries payments through alternate MIDs when declines occur.

​
Billing Configuration

  • Create and manage products and subscription plans within the Paysight dashboard.
  • Configure billing cycles, discount rules, taxes, and volume caps.
  • Set retry schedules and maximum retry attempts to minimize revenue loss.
  • Adjust MID Group membership and routing priorities when managing payment processors.

​
Payment Processing and Retry Logic

  • Payments are initiated via the Payment API or Card Submit API tied to subscriptions and invoices.
  • MID Groups handle routing logic automatically based on current MID status and capacity.
  • If a MID reaches its cap or is temporarily disabled, Paysight skips it and moves to the next eligible MID.
  • Failed payments trigger retry attempts per configured schedules.
  • Status updates flow back via webhooks for event-driven reconciliation.

​
Invoicing and Reporting

  • Paysight generates electronic invoices aligned with billing events.
  • Customers receive notifications according to configured workflows.
  • Reports detail revenue by product, declines, retries and processor performance.
  • Finance teams use reports to monitor billing health and forecast revenue.

​
Troubleshooting and Common Issues

  • Monitor transaction declines for card or processor issues.
  • Use MID Group insights to adjust routing and avoid bottlenecks.
  • Investigate payment failures with the Customer Service API.
  • Use the Mitigation API to handle chargebacks or disputes related to billing.

​
Best Practices

  • Regularly review and update MID Group configurations to optimize routing.
  • Use automated retry strategies thoughtfully to balance collection and customer experience.
  • Keep billing schedules and invoicing notifications up-to-date.
  • Integrate webhooks to synchronize payment status with your CRM system.
Paysight’s billing logic provides a seamless, flexible platform to manage subscriptions, payments, and revenue recovery while maximizing approval rates through intelligent routing and retries.