Recurring Payments

For card payments and electronic bank credits and debits it is possible to use a 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 a response with TrackingNumber 123456783 is received from RAVEN:

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

You may use the tracking number from the original payment as the TemplateNumber for subsequent payments.

For example:

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


The template payment should be one that was successfully processed , however, it is not mandatory. It is possible for the original payment to be for a zero amount (in which case it will be invalid but can 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. In each category of payments the fields which are supplied by the template are indicated by an †.

There are time limits to the use of Payment Templates. As a default, RAVEN will store payment details for use as a template for 90 days after the original payment. However, you may instruct RAVEN to keep details for 180 days by checking the appropriate field.

If you are processing annual subscriptions and require details to be stored for a longer time period, you will need to inform us at the time of setup, and we will keep details for 14 months from the original payment.