General

Previous  Next |  Direct link to this topic

clip0018

Integrations

 

B1P&D should handle one-time Credit Card links

Enabling this option will hide some functionality surrounding copying links for one-time Credit Card documents. iPayment will assume that B1P&D will handle the delivery of the links using email.

 

Please see the B1P&D manual for information on how to setup this feature.

 

Note: Enabling this option will not automatically make B1P&D send out email links. You will need to configure B1P&D and use the iPayment specific keywords.

 

Warning: Remember to setup B1P&D before enabling this option!

Save Credit Card to Business Partner record when importing transactions

If this option is enabled iPayment will save the Credit Card details on the Business Partner record connected to the document imported from the One-time Credit Card integration table. This means that the token created for the Credit Card will be saved to the Business Partner and can then be used to process future transactions.

Authorize.NET integration

 

Currency

(Authorize.NET only)

Authorize.NET only:

The currency selected needs to match the currency that your Authorize.NET account was created in. Authorize.NET does not support changing currencies through the API so it is important that you get the account created in the correct currency.

 

Note: The demo mode runs in USD.

Customers needs to have a specific currency set. You cannot use the "Multi-currency" customer.

Data integration

(Authorize.NET only)

Authorize.NET only:

None:

This level is the default, which sends only the information required to complete a transaction successfully.

Level II data:

This level includes additional information about shipping and tax rates if these are available – providing these data may result in lower transaction fees with your provider when working with P-Cards customers.

Other

 

Process credit notes not linked to a settlement

Select this option if refunds should be possible without being linked to a base document/settlement

 

Secure trading

Requires CFT (Cardholder Funds Transfer) to be enabled

 

Authorize.NET

Requires ECC (Extended Credit Capabilities) to be enabled

Require CVV/CVV2 (Security code)

Enabling this option makes the Security Code (CVV) field on the “Add Credit Card” form mandatory.

CIM: Do Authorization on credit card add (fraud check)

(Authorize.NET only)

Authorize.NET only:

If you turn this off Authorize.NET will not do an automated 0.00$ Authorization check when adding credit-cards via the webpage.

Use internal browser

If enabled adding new Credit Cards will be done using a browser window inside SAP

Store Credit Card Display Information

If enabled all personal data on the credit card is stored locally and visible in the Credit Card window. This data is never used except to display in the Credit Card window.

 

If it is disabled then no personally identifying information is stored locally on the Credit Card holder. This can make it easier to be GDPR compliant, but you can no longer see any name, email or address on the card owner in the Credit Card window.

 

 

Use 'card on file' declaration when sending requests

(Secure Trading only)

Secure Trading only:

Enabling this option will send along a 'credentials on file' field in the initial request when storing a card.

For Visa cards it will also send along an 'initiation reason' field, containing information on why the merchant has initiated the transaction.

 

Including these fields will decrease the likelihood of declines caused by missing CVV codes when using cards on file.

 

You can learn more about this in the Secure Trading documentation in section 1.4 - Credentials on File (CoF):

https://www.securetrading.com//files/documentation/STPP-Payment-Pages-Setup-Guide-V2.pdf

 

Note: Enabling this options means you'll have to contact Secure Trading to have it included in your Site Security fields. See Configuration-->Secure Trading for more details.

Auth Method

(Secure Trading only)

Secure Trading only:

Auth methods are used to specify how a transaction is to be processed by the card issuer

 

If set to Gateway Default, iPayment will not specify AuthMethod when interacting with Secure Trading and Auths will happen using the method defined on the gateway website

 

If set to Pre-authrisations, iPayment make all calls using the 'Pre-Auth' Method. Read more about the Auth method via the More info link

 

If set to Final, iPayment make all calls using the 'Final' Method. Read more about the Auth method via the More info link

 

More info: https://docs.securetrading.com/document/api/advanced/auth-method/

ECI/Crypt Level

(Moneris Canada only)

Moneris Canada only:

This option controls which Moneris ECI/Crypt Level transactions are processed with.

 

Please be aware that this setting applies to ALL processed transactions.

Some processors might have special rules and requirements that transactions must fulfill to fit in a specific ECI/Crypt level.

It is your own responsibility to familiarize yourself with these rules, and make sure you choose the right ECI/Crypt level for your scenario.

 

If you're unsure, please contact Moneris support, who should be able to help you determine requirements for your processor.