DigetPay supports two recurring payment models:

• Scheduled Recurring
• Unscheduled Recurring

Both models use a payment token generated from the customer's initial payment, allowing future charges without collecting the card details again.

---

How Recurring Payments Work

The merchant can configure recurring payment settings directly from the Merchant Dashboard.

Available configuration includes:

• Enable or disable recurring payments.
• Billing cycle.
• Number of installments.
• Customer payment experience.

These settings apply automatically to newly created recurring payment plans.

---

Recurring Payment Flow

sequenceDiagram
    autonumber

    participant Customer
    participant Merchant
    participant DigetPay
    participant Gateway

    Customer->>Merchant: First payment
    Merchant->>DigetPay: Create initial payment
    DigetPay->>Gateway: Process payment
    Gateway-->>DigetPay: Approved
    DigetPay-->>Merchant: Payment approved + recurringToken

    Note over Merchant: Store recurringToken securely

    loop Future recurring payments
        Merchant->>DigetPay: Charge recurringToken
        DigetPay->>Gateway: Process recurring payment
        Gateway-->>DigetPay: Result
        DigetPay-->>Merchant: Success / Failed
    end

---

Recurring Payment Types

Scheduled Recurring

Scheduled recurring payments occur automatically on a predefined schedule.

Typical examples include:

• Monthly subscriptions
• Weekly memberships
• Daily services
• Installment plans

The billing cycle and number of payments are configured before the subscription starts.

Example

---

Unscheduled Recurring

Unscheduled recurring payments do not follow a fixed schedule.

Instead, the merchant initiates future charges whenever a new payment is required.

Common use cases include:

• Utility bills
• Pay-as-you-go services
• Metered billing
• Usage-based pricing
• Variable subscription amounts

Since there is no predefined schedule, each recurring payment is initiated by the merchant whenever applicable.

---

Merchant Dashboard Configuration

The Merchant Dashboard allows merchants to configure recurring plans without sending installment information during checkout.

Supported configuration includes:

---

Scheduled Payment Timeline

timeline

    title Monthly Subscription Example

    Checkout : Customer completes first payment

    Month 1 : First installment

    Month 2 : Automatic payment

    Month 3 : Automatic payment

    ...

    Month 12 : Final installment

---

Initial Payment

The customer completes the first payment normally using the checkout page or Embedded Integration.

During this payment:

• Customer authentication is performed.
• Payment authorization is completed.
• DigetPay generates a recurring payment token.
• The merchant stores the recurring token securely.

---

Future Payments

Future recurring payments use:

• Stored recurring token
• Original transaction reference
• Merchant API credentials

The customer's card information is not collected again.

---

Best Practices

• Store recurring tokens securely.
• Never expose recurring tokens to browsers or mobile applications.
• Use recurring tokens only from your backend.
• Monitor webhook notifications for recurring payment results.
• Handle failed recurring payments according to your business rules.

---

Related Documentation