Payment Processors is where you add and configure Merchant Accounts for CORESense supported Payment Processors and assign those Merchant Accounts to Sales Channels.
|
Field |
Description |
|
Payment Processor: |
CORESense supported Payment Processors. Currently supported Payment Processors include: Braintree - Back office and eCommerce only. Supports Braintree as the processor. EdgeExpress - Back office, eCommerce and POS (card swipe only. Supports GlobalPay as the processor. OpenEdge Transaction - POS (Genius P400 and MX915/925 only). Supports GlobalPay as the processor. Tempus - Back office, eCommerce and POS (card swipe or Ingenico Lane 3000/5000. Supports First Data as the processor. PayPal Commerce Platfprm - eCommerce |
|
Merchant Account: |
Client-given Name of Merchant Account created using the Payment Processor. |
|
Active: |
Status of Merchant Account. |
|
Actions: |
Configure Manager payment processor-specific settings. Message Mapping: When a request is sent to a payment processor it will respond with a code and a default message. This section allows you to override those default messages with custom short and long messages. The message codes and default messages are generally specific to a Payment Processor and you can find information on both in their developer api documentation and also in their user documentation. Delete: Delete a Merchant Account. Note that you cannot delete a Merchant Account that is linked to a Sales Channel. You must un-link the Merchant Account first. |
Use the Add New Merchant Account link to add a new account to the Available Payment Processors list.
NOTE: The configuration is unique to each payment processor and fields will display based on who the processor is and you will need to consult the processor representative regarding the data needed for those fields. This DOES NOT create an account with your Merchant Account provider. This form allows you to enter information about your Merchant Account, for use in payment processing.
CORESense supported Payment Processors. Currently supported Payment Processors include:
Braintree - Back office and eCommerce only. Supports Braintree as the processor. Includes option for 3DS2, L1 or L2 processing.
EdgeExpress - Back office, eCommerce and POS (card swipe only. Supports GlobalPay as the processor.
EdgeExpress PayPage - Back Office and eCommerce
OpenEdge Transaction - POS (Genius P400 and MX915/925 only). Supports GlobalPay as the processor.
Tempus - Back office, eCommerce and POS (card swipe or Ingenico Lane 3000/5000. Supports First Data as the processor.
Affirm - eCommerce
PayPal Commerce Platform (PPCP) - PayPal Checkout comes with PayPal payments, card processing, and country-specific payment options. eCommerce only.
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
|
Merchant Id: |
Provided by Braintree. |
| Public Key: | Provided by Braintree |
| Private Key: | Provided by Braintree |
| Tokenization | Should be set to Yes. |
| Tokenization Key | This is generated inside your Braintree online account. |
| Merchant Account Id: | Optional Id for differentiating different business entities using the same Merchant Account. It is provided by Braintree. |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
| Enable 3DS | True - 3DS2 is enabled. False - It is not enabled. |
| Include Level 2 Data: | Yes - Include required by Braintree fields to process Level 2 transactions. |
| Include Level 3 Data: | Yes - Include required by Braintree fields to process Level 3 transactions. |
PayPal must included in the braintree_js file. This is present by default.
To use Apple Pay with Braintree, you can:
Contact Braintree support with your Merchant Account Info
Enable Apple Pay as a payment method on your Checkout page. CORESense will add apple pay to the braintree_js file.
Set up an Apple Pay Developer Account
Create an Apple Pay Merchant ID
Generate an Apple Pay payment processing certificate
Register your sandbox domain name in the Braintree Control Panel
Add domains to your Braintree Panel
Set up a device that supports Apple Pay payments
Add test cards to your Apple Pay Wallet
Braintree 3DS (3-D Secure) is a security protocol that adds a layer of authentication to eCommerce transactions, primarily by using two-factor authentication (like a one-time passcode or app verification) to verify a customer's identity with their bank.
Website Setup
Contact CORESense support to have you websites setup for 3DS.
Backoffice Setup
Under System Settings>Payment Processors>Available Payment Processor click Configure for your Braintree account. Under Enable 3DS, select Yes.
Under System Settings>Technical Configurations goto the Braintree_3ds_status_code_settings table. This table includes the following columns:
status - The status of the 3DS authentication
3ds_required_it_true_reject - Displays whether a successful 3DS authentication is required for this status. The fields in this column cannot be changed.
flag_order (1,0 - Set to 1, if you want the order flagged for review.
>3ds_reject_message - The message that is displayed to the customer.
Under Setup>System Settings>Automation>Fraudulent Order Detection Automation Set the 3DS Authentication Risk Flag - [Checkbox] Enable 3DS Authentication Risk Detection
An order will fail fraud detection if 3DS Required is set to false in the merchant account configuration and the 3DS authentication status is flagged for review in technical configuration>3DS Status Code Settings under flag_order. 1 means you want the order to fail fraud detection, 0 means you not.
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
|
XWeb Id: |
Provided by Global Payments. |
| Terminal Id: | Provided by Global Payments |
| Auth Key | Should be set to Yes. |
|
Card Present: |
Yes - Credit Cards are being swiped or read by a card reader or manually entered by a CORESense user. No - Ecommerce or phone sales. Generally your payment processor account is setup by the provider for either 'card present' or 'card not present'. |
| Tokenization | Should be set to Yes. |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
|
XWeb Id: |
Provided by Global Payments. |
| Terminal Id: | Provided by Global Payments |
| Auth Key | Should be set to Yes. |
| Tokenization | Should be set to Yes. |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
| Payment Page Branding - Body: |
|
| Payment Page Branding - Button: | |
| Payment Page Branding - Special CSS: | |
| Payment Page Branding - Special CSS2: |
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
|
XWeb Id: |
Terminal ID provided by Global Payments. |
| TID: | Provided by Global Payments. |
| Auth Key | Should be set to Yes. |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
| Transaction Logging | Keep detailed transaction logs? If unsure, select no.) |
| Tokenization | Should be set to Yes. |
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
|
RNID: |
Provided by Tempus. |
| RNCERT: | Provided by Tempus. |
|
Card Present: |
Yes - Credit Cards are being swiped or read by a card reader or manually entered by a CORESense user. No - Ecommerce or phone sales. Generally your payment processor account is setup by the provider for either 'card present' or 'card not present'. |
| Use Tokenization | Should be set to Yes. |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
| Live API URL | If not specified, will default to https://secure2.spectrumretailnet.com/ppsapi |
| Test API URL | If not specified, will default to https://dev.spectrumretailnet.com/ppsapi |
| Hosted-Pay (iFrame): |
Yes - indicates that this merchant account is using Tempus's hosted payment iFrame for PCI compliant transactions. Use of the Tempus iFrame requires new credentials from Tempus . When Tempus iFrame is enable for the SOI, a "Switch to SRED Interface" hyperlink in SOI -> Payments -> Charge customer credit cards section is displayed and must be clicked to the use the SRED to enter the credit card information or swipe the credit card. |
| Hosted-Pay URL: | This is required if Hosted-Pay (iFrame) is yes and is provided by Tempus to the client. |
|
PPAPI URL: |
This is required if Hosted-Pay (iFrame) is yes and is be provided by Tempus to the client. |
| Debit Returns | Whether your processor allows returns against debit cards. |
| Transaction Logging | Keep detailed transaction logs? If unsure, select no.) |
| Tokenization | Should be set to Yes. |
|
Field |
Description |
|
Merchant Account: |
Client given Name of Merchant Account. |
|
Settlement Time: |
The time of day that you want to submit transactions for settlement. |
| Active: |
Yes - Available to use No - Not Available to use |
| Live |
Yes - Transactions are posted to the Payment Processors production server. No - If available, transactions are posted to the Payment Processors test server. Take care to always check that this is set to 'Live' when mapping the processor to an active Sales Channel. |
| Transaction Logging | Keep detailed transaction logs? If unsure, select no.) |
|
Field |
Description |
|
Channels: |
All active Sales Channels are listed under here. |
|
Merchant Account: |
Assign the Merchant Account to use for each of the channels. |
The Tempus and OpenEdge Transaction Payment Processors integration with Payment Card Readers. These readers are setup per POS Terminal in the POS Replication Manager.
© 2023 CORESense · info@coresense.com · 125 High Rock Avenue, Saratoga Springs, NY 12866