Introduction:

The purpose of this guide is to provide Orange CRM users with guidelines for setting up FlexPay.
By following the outlined steps, you will have correctly configured your Orange CRM system allowing transactions to process correctly between your CRM and FlexPay. Of course, each user has their own unique way of leveraging their CRM, the guidelines below should assist you in respecting your internal processes while getting the best out of FlexPay.

Prerequisites:

You have received your FlexPay login credentials and your SFTP is already set up. If you have not received these yet, just reach out to your FlexPay Client Success Manager. 

Main Points of Configuration:

1. Banking: You will need to add a new merchant bank specifically for FlexPay.
2. Scheduled batch drops: Creating your batch job schedules to make sure that transactions are sent to FlexPay and returned to your CRM.
3. Default Retry logic: There may be product-specific retry limits configured into the acquisition center. You will need to align these with FlexPay limits in order to allow the transaction to be efficiently recovered.

Configuration

Merchant Banks:

• Click on Add Merchant Bank.
• Select your program from the drop down menu.
• Create your FlexPay bank name under the name field. e.g. Product 1 FlexPay.
• You will only be needing one merchant bank setup for all merchant gateways per program.

Setup Tab:

If fields are not listed here, please leave the field as default.

Processing options section:

If fields are not listed above, please leave the field as default.

** Create a FlexPay Bank Route:

1. Create a FlexPay Bank route directly from "Assign Customer To"
2. Within the bank route, assign CASH and FlexPay merchant bank. You may have to do this directly from Bank --> Bank Route (and not from the merchant bank)
3. Assign customer to FlexPay bank route

Note: Make sure that for inactive acquisition centers to set FlexPay up the acquisition center round robin and make them temporarily active so that it picks up transactions from this acquisition center. If all of the above steps are not followed, transactions can get stuck "in queue".

Gateway Response Codes:

Orange will properly auto-fill these.

**GO TO THE INTEGRATION GUIDE AND VERIFY THAT THE SUCCES, ERROR CODES, RETRY CODES, AVS SUCCESS AND AVS FAIL CODES  ARE CORRECTLY LISTED HERE**

File Delivery and Pickup:

If fields are not listed here, please leave the field as default.

Limits Tab:

If fields are not listed here, please leave the field as default.

You can configure the Daily Limits and Monthly Limits sections if there are existing limitations to how many transactions can be sent to FlexPay per day or month only.

Credit Cards Tab:

• Enable the cards types which you are processing. Deposit bank should be "undeposited funds".
• Set all Batch related to the field to their maximum capacities.
• As there are no transaction fees within FlexPay the fee settings can be left at 0 values.

Acquisition center:

Billing Plans tab - specific initial fee schedule:

If we are processing the initial transaction of a client then the retry count will need to be adjusted here to ensure it is allowed to go through all of FlexPays attempts. Retry Amount/Attempt: Make sure retry attempts are at 15 minimum.

Batch Job Schedule:

• From Merchant Bank Setup: Batch Jobs [Menu]->Click on the [NEW Batch Job] button. Follow parameters that best suit your internal processes.
• Make sure that the new Batch Job is on the same queue as other batch jobs for that program, and follows the execution time.
• There is a second batch job to verify or create, if it does not already exist, for the instance of Orange CRM you are working on. Each instance of Orange requires one FlexPay Import job to be created.

FTP Access:

Each CRM instance will need a folder named "FlexPay" in its Orange FTP server. Don’t forget to create this folder as this is where data gets posted from Orange to the server. 

Testing

Testing as such is not a required step as we have already done all the hard work for you with your CRM provider, however, you may wish to gradually increase traffic flow to FlexPay as you familiarize yourself with the platform.
A great way to test is doing the same steps that you would be doing to go live, however limiting the limits (as mentioned above), and process very few transactions. It is recommended that you do this by limiting the number of transaction per batch and slowly increase it at your own pace. For example, you may wish to send $5K of transactions on day one, then $8K on day two etc. If you do testing, please make sure to revert your settings (i.e putting the number of
transaction per batch back to agreed number). 

Going Live

Technically you are already live, however, you are now ready to send all you transactions to FlexPay and no longer wish to divert to other bank routes.

• Under the limits tab in the FlexPay Merchant Bank, increase your amounts sent by batch to their maximum values.
• Configure your pre-existing bank routes to refund only. (DO NOT DISABLE THEM).
• Bank Assignments: The bank assignments will need to be rerouted so that your transactions all route to FlexPay. The "Assignments" tab is on the top right hand of your Merchant Bank screen. Go to the bank which you have set to "refund only", select the existing bank name by double clicking on them and re-select the FlexPay route. When you refresh there should be no more bank routes left in the dialogue box. Click save. Open your FlexPay bank route, all the routes will now be populated in its "Assignments" tab.

Upon the next batch run, your transactions will now be pointing to FlexPay.

And now you are ready to go!