Recurring Payments

For card payments and electronic bank credits and debits it is possible to use pre-existing payment as a template for a subsequent payment. This allows for a recurring payment, without the need to store the customer’s account or card details. For example, if the following response, with TrackingNumber 123456783 is received from RAVEN:

810010, USD, cc_debit, 0802, 376431088062008, BWL00020637A, 15000,Submitted, 123456783

A subsequent payment may be issued with the tracking number from the above payment provided as the TemplateNumber.

For example:

PaymentRoutingNumber,CurrencyCode, PaymentType,TemplateNumber,Amount
810010, USD, cc_debit, 123456783, 15000


The template payment should be one that processed successfully, however this is not mandatory. It is possible for the original payment to be for a zero amount in which case it will be invalid but this payment still be used as a template.

The template and the payment to which it is being applied need to be of the same category (i.e. both card payments or both ACH payments), but they do not need to be the same type. For example, the original type may be a cc_debit, but the subsequent payment could be a cc_credit.

It is an error to supply a Field with values if those same values will be supplied by the template. For example it is an error to supply a CardNumber if a TemplateNumber is already supplied. For each category of payments the fields which will be supplied by the template are indicated by an †.

There are time limits to the use of Payment Templates. For example, a payment may only be used as a template for 180 days after the original payment or its last use as a template. The only exception to this rule is in the case of annual subscriptions: the limit is 14 months from the original payment or its last use as a template.