The Credit Card Settlement Process (CCP610) settles and reconciles Payflow Pro and CyberSource credit card payments. This process:
1. Issues post-authorizations for all pre-sale transactions
2. Issues credits for all pre-credit transactions
3. Creates an exception report listing all pre-sales and invalid receipts and all pre-credits with invalid vouchers
4. Generates a report listing daily transactions
The following table defines the credit card settlement process parameters:
Parameter |
Definition |
---|---|
Organization ID |
The Organization ID for which you want to run the report. Parameter information is defaulted by Personify and can not be changed. |
Organization Unit ID |
The Organization Unit ID for which you want to run the report. Parameter information is defaulted by Personify and can not be changed. |
Payment Handler |
Determines which payment handler is included in the report. The settlement is applied using this payment handler. |
Merchant ID |
Determines the Personify Merchant ID number to be included in the report. |
Direct Batch |
Determines the current credit card settlement process as a direct batch. Enter a direct batch if you are using deferred credit card processing and you do not want the system to create the batch for you. Receipts created for deferred authorizations are created in this batch. The batch is posted after the process completes. |
List Txns From Previous Run |
Determines whether transactions from previous processing runs from the same day are included in the current process. Available options include: · Y – includes transactions from the previous credit card settlement process in the current credit card settlement process. · N – excludes transactions from the previous settlement process. |
Process Deferred Payments |
Determines whether the application automatically creates the batch for processing of deferred payments. If the parameter value is set to “Y,” the process will automatically create a batch for processing of deferred payments where direct batches are not defined. |
Void Authorization |
Added with the 7.3 release, this field determines whether the payment gateway will void orphan authorizations. Voided authorizations are not mapped with any Personify orders. Available options include: · Y – sends a request to the payment gateway to void orphan authorizations. · N – does not send a request to the payment gateway to void orphan authorizations. |