> ## Documentation Index
> Fetch the complete documentation index at: https://docs.slm.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Processing Configuration Considerations

## Payments Merchant Options

This section describes how to configure Subscribe behavior related to transaction generations

| Field | Required/Optional | Description | Valid values |
| - | - | - | - |
| cashbox\_transaction\_prefix | Required | A merchant-specific string pre-pended to the Transaction ID for any transactions initiated by Subscribe (Subscription renewal transactions). | String of up to 5 letters |
| affiliate\_cycles | Optional | An affiliate is the sourcing channel of the subscription. Configure the number of cycles we will associate the transaction with its affiliate ID. This allows you to define whether you want to recognize the sourcing channel with the subscription for the full lifecycle or only for several cycles. Cycle numbering will include paid cycles (will exclude free cycles). | Default (0) - infiniteAccepts any number. Entered number indicates the number of cycles for which the affiliate will appear on the transaction. |
| use\_credit\_reason\_on\_tx\_item | Optional | When a renewal transaction uses a currency credit on the subscription, the text defined in this field will appear as the SKU for the transaction. If nothing is defined, the transaction SKU will be **AutoBillCreditConversion**. | Empty (default)AMU /MAC |

## Payment Processing Merchant Options

This section describes settings related to the way Vindicia process a transaction with the payment providers. In most cases, these settings should not be modified and the default values should be kept.

| Field | Required/Optional | Description | Valid values |
| - | - | - | - |
| initial\_recurring | Optional | Defines how the first billing cycle of a Subscription is handled. This field instructs the system **to handle the first transaction of a new subscription as if it's part of an existing recurring transaction** and not as an initial first transaction of a subscription. | **Note:** Leave as default. Use this field with care, and only in very special cases, as it might interfere with the CIT/MIT regulations 0: sends the first scheduled transaction for a Subscription to the Payment Provider as a one-time (eCommerce) transaction. (Default.) 1: sends the first transaction to the Payment Provider as a recurring transaction. |
| online\_recurring | Optional | Defines whether or not **one-time transactions are submitted to Payment Providers with the recurring flag set to true**. By default, Subscribe only sets the recurring flag to true for recurring transactions (subscriptions). In some cases, for large merchants with payment providers such as Chase Paymentech, marking one time transactions as recurring results in a better approval rate. | **Note:** Leave as default. Use this field with care, and only in very special cases, as it might interfere with the CIT/MIT regulations NULL, 0: Subscribe will not submit one-time transactions as recurring. (Default.) 1: Subscribe will submit one-time transactions with the recurring flag set to true. |
| merchant\_auth\_expiration\_days | Optional | Used to define the number of days an authorization remains valid, when an authorization is processed before (without) capturing the transaction. | Null (default value): uses the payment provider auth expiration days. Recommended value : 7 |
| **Parent topic:**[Payment Processing](../topics/paymentProviderConfiguration) | | | |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.