Recurring Payment Rules
A Recurring payment is a charge that will happen again.
Typically this comes in two flavors: Subscription based payments and Installment based payments.
Subscriptions
Subscription based payments will not typically have an end date. Subscriptions will usually continue until the Subscription is canceled.
Installments
Installments will typically have an end date and are handled slightly differently than subscriptions.
Required Fields
All fields below should be considered required. Note that the moto_ecommerce_ind and the cit_mit_indicator are specific to the recurring type.
Subscription-Based Recurring Payments
For subscription-based recurring payments, send the following field:
recurring_pmt_num— Payment number in the sequence
Installment-Based Recurring Payments
For installment-based recurring payments, send the following fields:
recurring_pmt_num— Current payment numberrecurring_pmt_coun— Total number of payments
Examples
Example Installment
profile_key=xxx&profile_id=xxx&transaction_type=D&transaction_amount=5.00&card_id=xxx&moto_ecommerce_ind=3&card_on_file=Y&cit_mit_indicator=M104&account_data_source=Y&cardholder_street_address=123&cardholder_zip=55555card_exp_ date=1228&CVV2=123&merchant_initiated=y&transaction_id=xxx&recurring_payment_num=2&recurring_pmt_coun=22
Example Subscription
profile_key=xxx&profile_id=xxx&transaction_type=D&transaction_amount=5.00&card_id=xxx&moto_ecommerce_ind=2&card_on_file=Y&cit_mit_indicator=M103&account_data_source=Y&cardholder_street_address=123&cardholder_zip=55555card_exp_ date=1228&CVV2=123&merchant_initiated=y&transaction_id=xxx&recurring_payment_num=2
Important Note
In both examples, the transaction_id is submitted in subsequent CoF transactions and is the transaction ID from the last approved authorization request for those credentials.
Code samples
Copy-paste ready code in your preferred language for the Test environment.
API call