SoftSlate Commerce
Home » Documentation » HTML Documentation

Payflow Pro Advanced Settings

The Payflow Pro Processor provides a number of advanced settings allowing you to tailor your online processing to your business, on the Payment Configuration -> Payflow Pro Advanced Settings screen. To explain how these advanced settings work, here is a step-by-step guide for how the Payflow Pro Processor handles each order as it is submitted by a customer.

  1. The Payflow Pro Processor starts by comparing the customer's order with the settings defined under "Level One" of the Payflow Pro Advanced Settings:

    • If Customer's Status Equals: If the customer placing the order is logged in and has a "Status" corresponding to this value, the Level One settings will be applied to the order. All customers' status values can be modified at any time on the Orders and Customers -> Customers screen. For example, you may want to identify customers who have ordered in the past and label them with a status of "Qualified". When these customers come through to place a new order, you can automatically capture the order by setting the transaction type to "Sale" for their customer status. On the other hand, for all other customers, or for users who are placing an order without an account, you may want to authorize and authenticate their purchases first.
    • If Order Total Is Between: If there is no match on the customer's status, but the total price of the items in the current order falls within this range, the Level One settings will be applied to the order. This allows you to treat small orders, which may not be of great concern in terms of fraud, differently than large orders, which may require vetting. You could allow orders under, say, $100 to be captured automatically while larger orders would be authorized only, pending a manual review.
    • Delivery Country Is: If there is no match on either the customer's status or the order total, but the delivery address's country matches a selection in this drop down menu, the Level One settings will be applied to the order. The idea is you can treat orders going to different countries differently. Some countries may be a constant source of fraudulent orders, and others may not support AVS or card security code validations. In these cases, you can use this setting to identify those countries you wish to treat differently.
  2. If none of the above settings under "Level One" applies, the processor next looks for a match with the "Level Two" settings, and, failing that, a match with the "Level Three" settings. If no match can be found, the processor uses the "Transaction Type" and "Authenticate On These Results" settings under the "Default" column.
  3. Having determined which level of settings the given customer falls under, the processor next identifies the Transaction Type to be used for the order:

    • Authorization: If this option is selected under the level of settings that is in effect for the customer, an authorization request is sent to Payflow Pro, which places a hold on the customer's credit card account matching the amount of the order. You must capture the funds at a later time.
    • Sale: If this option is selected, the funds are immediately captured from the customer's credit card. There is no need to perform a delayed capture at a later time.
    • Authorize/Authenticate: First, the processor sends Payflow Pro an authorization request, which places a hold on the customer's credit card account matching the amount of the order. Next, the AVS and card security code results that come back from the authorization are tested against the checkboxes under the "Authenticate On These Results" settings. If the results are acceptable, the customer is considered "Authenticated" and the order is allowed to go through. If the results do not match one of the authentication checkboxes, the transaction is considered declined. An error message is given to the customer on the credit card payment screen asking him or her to double check the billing address and security code he or she has entered.
    • Authorize/Authenticate/Sale: First, the processor sends Payflow Pro an authorization request, which places a hold on the customer's credit card account matching the amount of the order. Next, the AVS and card security code results that come back from the authorization are tested against the checkboxes under the "Authenticate On These Results" settings. If the results are acceptable, the customer is considered "Authenticated" and an immediate Sale request is sent to Payflow Pro, capturing the funds that were just authorized. If the results do not match one of the authentication checkboxes, the transaction is considered declined. An error message is given to the customer on the credit card payment screen asking him or her to double check the billing address and security code he or she has entered.
  4. For the "Authorize/Authenticate" and "Authorize/Authenticate/Sale" transaction types, the processor checks the returned values for AVS Street, AVS ZIP, and card security code against the list of checkboxes. Note that a "Y" indicates a successful match for the street address, ZIP code, or security code. A "N" indicates a mismatch, and an "X" indicates that the customer's bank does not support that type of validation.

Copyright © 2009-2017 SoftSlate, LLC. All Rights Reserved.

Powered by SoftSlate Commerce

Foraker Design