Create Recurring Payin

Recurring Payin is a method for setting up automated, recurring payments from customers. This allows merchants to collect funds on a scheduled basis without requiring manual intervention for each payment.

Recurring Payins are useful for:

  • Subscription Services: Monthly or yearly subscription payments
  • Membership Fees: Recurring membership or service fees
  • Utility Bills: Automated bill payments

Key Features

  • Flexible Scheduling: Support for WEEKLY, MONTHLY, QUARTERLY, and YEARLY frequencies
  • Auto Debit: Automatic payment processing without customer intervention
  • Fixed or Variable Amounts: Support for both fixed recurring amounts and variable amounts
  • Payment Plans: Integration with existing payment plans or standalone recurring payments
  • Activation Delays: Configurable delays before the first payment is processed

Prerequisites

Before creating a Recurring Payin, ensure you have:

  1. Customer Created: The customer must exist in the system (optional but recommended)
  2. Payin Method: A valid payin method ID for the payment type
  3. Payment Plan (Optional): If using an existing payment plan, ensure it's properly configured

Recurring Payin Types

  • With Payment Plan: Uses an existing payment plan configuration
  • Standalone: Creates a new recurring payment configuration without a payment plan

Status Flow

  • CREATED: Initial status when recurring payin is created
  • ACTIVE: When the recurring payin is active and processing payments
  • CANCELLED: Permanently cancelled recurring payments
  • COMPLETED: When all scheduled payments have been completed

Webhook Notifications

Finmo will send webhook notifications for recurring payin events:

  • RecurringPayin_CREATED: When a recurring payin is created
  • RecurringPayin_ACTIVATED: When the recurring payin becomes active
  • RecurringPayin_PAYMENT_PROCESSED: When a scheduled payment is processed
  • RecurringPayin_PAYMENT_FAILED: When a scheduled payment fails
  • RecurringPayin_CANCELLED: When the recurring payin is cancelled
Body Params
string

Customer ID (cus_*). Optional but recommended for customer-specific recurring payments

string
required

Payin method Name to be used for recurring payments

string

Payment plan ID (paymentplan*). If provided, other payment plan fields will be ignored

boolean
Defaults to true

Whether payments should be automatically debited without customer intervention

string
enum

Frequency of recurring payments. Required if payment_plan_id is not provided

Allowed:
string

Currency code for the recurring payment (ISO 4217). Required if payment_plan_id is not provided

string

Country code for the recurring payment (ISO 3166-1 alpha-2). Required if payment_plan_id is not provided

number
required
≥ 0.01

Amount for each recurring payment. Required if is_recurring_amount_fixed is true or not provided

date-time
required

Start date and time for the recurring payments (ISO 8601 format)

date-time

End date and time for the recurring payments (ISO 8601 format). Optional

integer
≥ 0

Delay in minutes before the first payment is processed. Optional

boolean
Defaults to true

Whether the recurring amount is fixed. If false, amount field is not required

Responses

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json; charset=utf-8