X-Payments Help - User contributions [en]

XP Cloud:Tokenization and Re-Use of Saved Credit Cards

2020-04-13T11:10:21Z

Mouse: Mouse moved page X-Payments Cloud:Tokenization and Re-Use of Saved Credit Cards to XP Cloud:Tokenization and Re-Use of Saved Credit Cards: Moving to the new workspace

<noinclude>{{XPC manual TOC}}</noinclude>

In this section:
:* [[#TokenizationOverview | Tokenization: Overview]]
:* [[#TokenizationRelatedConfiguration | Tokenization related configuration for Authorize.Net / Intuit QuickBooks Payments]]
:* [[#ChargeSavedCard | Charging Saved Credit Cards]]
:* [[#ViewPaymentsBySavedCard | Viewing Payments Made with Saved Credit Cards]]
:* [[#GetUpdateTokenizedCard | Get/update tokenized card feature]]

<div id="TokenizationOverview"> </div>
====Tokenization: Overview====
If you serve repeat customers or need to run recurring payments, you may want to be able to store your customers' credit or debit card information so you will not have to ask for it again every time a purchase is made. However, according to PCI DSS, an industry-wide standard that must be met by any organization that stores, processes, or transmits cardholder data, storing customers' card information is not allowed for regular merchants - unless they take steps to implement a number of security aspects and undergo an expensive and time-consuming process of certification to ensure that all the PCI DSS requirements have been thoroughly met.

X-Payments Cloud provides a PCI DSS compliant solution that allows you to charge customer credit cards again when you use certain payment gateways. You get all the benefits of storing your customers' card information - without actually storing it on your system. This is made possible through the use of the so-called "tokenization". Tokenization is a means of protecting sensitive cardholder data that was designed to reduce the risks associated with storing credit card information for merchants. The technology is meant to prevent the theft of the credit card information in storage. It replaces your customer's credit card details with a special number (token) that can be used to charge again the customer’s credit card via an integrated payment gateway. As sensitive information is stored not on the merchant site, but in a secure PCI DSS compliant environment of the payment system, use of tokenization significantly simplifies PCI DSS compliance for the merchant.

Support for tokenization and re-use of saved credit card information is available for a number of payment gateways with which X-Payments Cloud works. To find out whether a specific payment gateway supports tokenization, see the list of [[X-Payments_Cloud:Supported_payment_gateways | supported payment gateways]] for X-Payments Cloud.

If your store has an active (enabled) payment configuration associated with a payment method with tokenization support, customers that have a user account at your store will be able to save their credit card information for future orders. They will be able to save a card during checkout: [[File:xpc_savecard_checkout.png|740px|border]] or via a special section in their user profile (For instance, in X-Cart 5, the respective page can be found under '''My account''' > '''Details''' > '''Saved cards'''): [[File:xpc_savecard_profile.png|740px|border]] All sensitive information associated with the card will be saved in a secure PCI DSS compliant environment of the payment system and available for re-use via X-Payments Cloud through the use of tokenization.

X-Payments Cloud allows a customer to save up to three credit or debit cards. Customers who have one or more saved cards associated with their user profile can choose which card to use for each specific order at your store. They can also manage the saved cards in their user profile.

<div id="TokenizationRelatedConfiguration"> </div>
====Tokenization related configuration for Authorize.Net / Intuit QuickBooks Payments====

For Authorize.Net and Intuit QuickBooks Payments, using sensitive customer payment information tokenization has some specifics described below.

During the initial transaction - when a customer chooses to save their credit card for future use and enters the credit card information to be saved using a secure form provided by X-Payments Cloud - this secure form in which the information is entered requires them to enter a Card Security Code (CSC/CVV2). This code is required only for the authorization of the transaction used to save the credit card info, and it is not saved or stored anywhere. Further payment transactions on the saved credit card do not require that CSC/CVV2 be entered.

However, the merchant back end of each of the above-named payment gateways provides some security settings allowing the merchant to customize the credit card authorization process for online transactions. Among them, there is a setting that can be used to allow or forbid the processing of transactions with Card Security Code unavailable. If this setting is adjusted in such a way that CSC/CVV2 is required for all payment transactions at all times, it will cause problems related to the store's ability to use the tokenization feature: for a saved credit card all payment transactions but for the very first one (the one that was used to save the card info) will be rejected by the payment gateway because of the missing CSC/CVV2. The payment gateway may generate errors similar to the following: "A validation error occurred while processing this transaction: Card Verification Code not available."

To avoid this problem, make sure that the payment gateway setting requiring the gateway to reject payment transactions with no CSC/CVV2 is not enabled. This will not cause your store to stop requesting CSC/CVV2 altogether because the X-Payments Cloud secure form employed by your store to collect credit card information treats the CVV field as required at all times - regardless of the payment gateway settings.

Following are instructions for how to achieve proper payment gateway account configuration for the specific payment gateways.
* Intuit QuickBooks Payments In the merchant settings, change the setting for '''If CSC is not available''' to ''Accept Transaction'':
: [[File:qb_transaction_security_settings.png|700px|border]]
* Authorize.Net CIM 
:# Log on to the Merchant Interface at https://account.authorize.net.
:# Select '''Settings''' under '''Account''' in the main menu on the left.
:# Click '''Card Code Verification'''.
:# Click to select the check box(es) next to the Card Code responses for which the payment gateway should reject transactions. Make sure you do not enable the option to reject transactions where the Card Code is unavailable. This, however, is different from transactions for which the Card Code is incorrect; we strongly recommend you keep the option to reject any transactions with incorrect Card Code enabled.
:# Click '''Submit'''. A confirmation message indicates that your settings have been successfully applied.

<div id="ChargeSavedCard"> </div>

====Charging Saved Credit Cards====

X-Payments Cloud allows you to charge again the cards that have been used at your store to pay you via an X-Payments Cloud integrated payment method with support for tokenization and have been saved in the customer's user profile for future use.

'''To charge a saved credit card via the X-Payments Cloud admin panel''':

# Find the initial payment that was made using the card that needs to be charged and open its details for viewing. To find the initial payment, use any of the following links: [[File:xpc_links2initial_payment.png|740 px|border]] or [[File:xpc_link2initial_payment.png|740 px|border]] If necessary, use [[X-Payments_Cloud:Searching_for_Payments|filtering/advanced search]].
# On the Payment details page displaying the details of the initial payment, click the 'Charge this card again' link. A popup form titled 'Charge this card again' will be displayed allowing you to specify the parameters of the new payment: [[File:xpc_charge_card_again.png|740px|border]]
# In the 'Charge this card again' form, enter the amount that needs to be charged. If you wish you can also provide a comment for yourself - something to make your job easier later when you will be figuring out what this payment is for.
# Click the '''Charge this card again''' button at the bottom of the form. [[File:xpc_charge_card_again1.png|740px|border]] Confirm the action. The card will be charged, and the new payment will be created in X-Payments Cloud. The newly created payment will be marked as associated with the initial payment: [[File:xpc_charge_card_again2.png|740px|border]] 

<div id="ViewPaymentsBySavedCard"> </div>
====Viewing Payments Made with Saved Credit Cards====

In X-Payments Cloud, all payments made using a saved card are linked to the initial payment made using this card and are considered "based" on this payment. You can tell whether a payment was made using a saved card by the contents of its Reference ID field: independent payments have reference IDs like "#N", whereas payments based on another payment (payments made using a saved card) have a link in the Reference ID field that looks like "Payment #N" and points to the Payment details page of the initial payment.

You can view the full list of payments for a specific saved credit card by using this button on the Payment details page of the initial payment made using this card: [[File:xpc_related_payments.png|740px|border]]

====Get/update tokenized card feature====

X-Payments Cloud supports the Get/update card feature for some payment integrations. These include:
:* Authorize.Net;
:* Chase Paymentech Orbital.

The Get/update card feature aims to protect your customer relationships by enabling you to quickly and easily update the details of tokenized cards that have been used for payment at your store (including the masked card number, expiry date, etc.)

Customer card information may change for a variety of reasons, including card expirations, lost or stolen cards, upgrades and so on. The Get/update tokenized card feature enables you to provide uninterrupted service to your customers keeping the updating process transparent to them.

To use the feature, you will need to enable the payment gateway's card information updating service in your payment gateway account (or, depending on the gateway, to have the gateway support enable it for you). This way you will get access to the gateway's interface allowing you to request an update of information for the credit cards that have been previously saved for use at your store and are now stored in the gateway's secure vault. Depending on the gateway, the tools you will get for updating your customers' payment card information will range from the simplest button that you click to request an update to more complex schedulers enabling you to schedule payment information updates according to your needs. After you request an update of your customers' payment information, the gateway will submit a request to VISA/Master Card to check if there have been any changes for the cards stored by the gateway for use in your store. After VISA/Master Card has processed the request (which may take up to 2-3 days), the gateway will get a report of any changed payment card details. Based on the report, the information stored by the payment gateway will be updated to reflect the changes. The updated cards will then be linked to the existing tokens. This way your store will be able to charge the cards after re-issue using the same old tokens already stored by X-Payments.

In X-Payments Cloud, you also get a button allowing you to request an update of information for any card involved in tokenized payments directly from the page of any payment made using that card: [[File:xpc_get_update_card_button.png|740px|border]]

If a customer with a tokenized card makes a payment at your store via X-Payments Cloud after the card has been re-issued, the card information will be updated automatically and transparently to the customer.

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Tokenization and Re-Use of Saved Credit Cards

2020-04-13T11:10:21Z

Mouse: Mouse moved page X-Payments Cloud:Tokenization and Re-Use of Saved Credit Cards to XP Cloud:Tokenization and Re-Use of Saved Credit Cards: Moving to the new workspace

#REDIRECT [[XP Cloud:Tokenization and Re-Use of Saved Credit Cards]]

XP Cloud:Managing High Risk Transactions (Accept/Decline)

2020-04-13T11:09:40Z

Mouse: Mouse moved page XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline) to XP Cloud:Managing High Risk Transactions (Accept/Decline)

<noinclude>{{XPC manual TOC}}</noinclude>

Some payment gateways provide merchants with fraud protection tools that allow them to identify potentially fraudulent transactions and manage their own fraud risk – to make their own decisions about which payments to accept or decline.

For example, some payment solutions by PayPal allow the merchant to set up Fraud Protection filters which make it easier for the merchant to detect and respond to fraudulent transactions. Depending on the merchant's preferences, the transactions identified as having a higher likelihood of risk can be rejected or held pending for review by the merchant so the merchant can explicitly accept or deny the payment.

X-Payments supports this feature for some payment gateway integrations (See [[X-Payments_Cloud:Supported_payment_gateways | Supported payment gateways]], "Accept" and "Decline" columns).

When a transaction is identified as high-risk by the payment gateway, the payment gets the "Authorized with warning"/"Charged with warning" status in X-Payments Cloud:
:[[File:XP_charged_with_warning.png|border]]

The following section appears on the Payment details page for the payment:
:[[File:XP2.0_accept_decline.png]]
You can use the '''Accept''' and '''Decline''' buttons in this section to specify whether you want to accept or decline the transaction.

If the transaction is accepted, the payment status is updated from "Authorized with warning" or "Charged with warning" to simply "Authorized" or "Charged".
If the transaction is declined, the payment becomes "Declined".

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline)

2020-04-13T11:09:40Z

Mouse: Mouse moved page XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline) to XP Cloud:Managing High Risk Transactions (Accept/Decline)

#REDIRECT [[XP Cloud:Managing High Risk Transactions (Accept/Decline)]]

XP Cloud:Managing High Risk Transactions (Accept/Decline)

2020-04-13T11:09:03Z

Mouse: Mouse moved page X-Payments Cloud:Managing High Risk Transactions (Accept/Decline) to XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline): Moving to new workspace

X-Payments Cloud:Managing High Risk Transactions (Accept/Decline)

2020-04-13T11:09:03Z

Mouse: Mouse moved page X-Payments Cloud:Managing High Risk Transactions (Accept/Decline) to XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline): Moving to new workspace

#REDIRECT [[XP Cloud:XP Cloud:Managing High Risk Transactions (Accept/Decline)]]

XP Cloud:Supported payment gateways

2020-03-02T09:22:30Z

Mouse: Mouse moved page X-Payments Cloud:Supported payment gateways to XP Cloud:Supported payment gateways: Moving to a new namespace

<noinclude>{{XPC manual TOC}}</noinclude>

The table below provides a list of payment gateways supported by X-Payments Cloud.
 
'''Legend:'''

* '''Auth''': Allows to authorize the availability of funds for a transaction (The buyer's funds are temporarily placed on hold to ensure the availability of the authorization amount for capture).
* '''Capture''': Allows to capture the amount of the authorization (The money authorized for the order is moved from the buyers's account to the merchant's account).
* '''Sale''': Supports transactions of 'Sale' type (Authorization and capture actions are completed simultaneously at the time the payment is processed).
* '''Void''': Allows the removal of an authorization hold from the buyer's account by the merchant.
* '''Refund''': Allows to issue refunds (The money is returned to the buyer's account).
* '''Get Status''': Can provide information about the status of a transaction to X-Payments Cloud.
* '''Get Card''': Can provide new/updated information about a saved credit card. For example, if a credit card gets re-issued, it is possible to get the renewed expiration date. If any other information changes, like the credit card number or the billing address, it is possible to access this updated credit card information as well.
* '''Accept''', '''Decline''': Allows to accept or reject transactions with a higher likelihood of risk.
* '''Test''': Can test whether the merchant account details entered in X-Payments Cloud are valid.
* '''3D-Secure via Cardinal Commerce''': Supports 3-D Secure payer authentication via Cardinal Commerce (both 3-D Secure v1 and v2 are supported). Best for PSD 2 in the European Union.
* '''Tokenization''': Supports tokenization (Allows to charge customer credit cards again - without X-Payments Cloud storing cardholder data).
* '''p''': Supports partial transactions (For example, "Capture + p" = Allows to capture a partial amount of the authorization).
* '''m''': Supports multiple transactions (For example, "Capture + m" = Allows to perform the capture action multiple times).

{| class="wikitable" width=90%
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.paypal.com/ PayPal]
| PayFlow Pro
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.paypal.com/ PayPal]
| PayPal Payments Pro (PayPal API)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.paypal.com/ PayPal]
| PayPal Payments Pro (Payflow API)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.anz.com/ Australia and New Zealand Banking Group Limited]
| ANZ eGate
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [https://paymentgateway.americanexpress.com/ American Express]
| American Express Web-Services API Integration
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]] + p, m
||
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://www.authorize.net Authorize.Net LLC]
| Authorize.Net
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|- style="vertical-align:top;"
| [https://www.bambora.com/ Beanstream Internet Commerce, Inc.]
| Bambora (Beanstream)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.beanstream.com/ Beanstream]
| Beanstream (legacy API)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [https://www.bendigobank.com.au Bendigo Bank]
| Bendigo Bank  
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://billriant.com Billriant.com]
| BillriantPay
| [[File:Check.svg|25px]]
|
|
|
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://bluepay.com/xpayments-partner-page BluePay]
| BluePay  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [https://home.bluesnap.com/ BlueSnap Inc.]
| BlueSnap Payment API (XML)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]]
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|- style="vertical-align:top;"
| [https://www.braintreepayments.com/ Braintree, a division of PayPal, Inc.]
| Braintree, direct integration with CC storing
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.caledoncard.com/ Blue Pay Canada (formerly Caledon Computer Systems, Inc.)]
| Blue Pay Canada (formerly Caledon)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.cardinalcommerce.com/ CardinalCommerce Corporation]
| Cardinal Commerce Centinel
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
|
|
|
|
| Built-in, only 3-D Secure v1
|
|
|- style="vertical-align:top;"
| [http://www.chasepaymentech.com/ Chase Paymentech]
| Chase Paymentech Orbital  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]] + p
|
| [[File:Check.svg|25px]]
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|- style="vertical-align:top;"
| [https://www.commbank.com.au/ CommWeb - Commonwealth Bank of Australia]
| CommWeb - Commonwealth Bank  
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.cybersource.com/ CyberSource]
| CyberSource - SOAP toolkit API  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.dibspayment.com/ DIBS Payment Services AB]
| DIBS
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [http://www.securepay.com.au/ SecurePay Pty Ltd]
| [http://www.directone.com.au/ DirectOne - Direct Interface]  
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [https://secure.5thdl.com Sparrow (formerly 5th Dimension Logisitics, LLC)]
| Sparrow (formerly 5th Dimension Gateway)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
| [[File:Check.svg|25px]] + p
|
|
|
|
|
|
|
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.echo-inc.com/ Electronic Clearing House, Inc.]
| ECHO NVP
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
| [[File:Check.svg|25px]]
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [http://www.elavon.com/ Elavon, Inc.]
| Elavon (Realex API)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.barclaycardbusiness.co.uk/about_us.html Barclaycard Business]
| ePDQ MPI XML (Phased out)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.eprocessingnetwork.com/Info.html eProcessing Network, LLC]
| eProcessing Network - Transparent Database Engine
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.moneris.com/ Moneris Solutions]
| eSELECTplus  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.eway.com.au/Company/Company.aspx Web Active Corporation Pty Ltd]
| eWay Rapid - Direct Connection
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.eway.com.au/Company/Company.aspx Web Active Corporation Pty Ltd]
| eWay Realtime Payments XML
| [[File:Check.svg|25px]]
|
|
|
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.globalpaymentsinc.com Global Payments, Inc]
| Global Iris/HSBC - RealAuth Remote
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.goemerchant.com/ GoEmerchant, LLC]
| GoEmerchant - XML Gateway API
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.heidelpay.de Heidelberger Payment GmbH]
| HeidelPay
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.innovativegateway.com/ Intuit, Inc. Innovative Gateway]
| Innovative Gateway
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.itransact.com/ iTransact, Inc.]
| iTransact XML  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.firstdata.com/ First Data Corporation]
| First Data Payeezy Gateway (formerly Global Gateway e4)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.merituspayment.com/ Meritus Payment Solutions]
| Meritus Web Host
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]] (works only in "Sale" mode, is disabled in "Auth only" mode)
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.nab.com.au/ NAB - National Australia Bank]
| NAB - National Australia Bank
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.netbilling.com/ Netbilling, Inc.]
| Netbilling - Direct Mode  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://netevia.com/ Netevia]
| Netevia
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://www.nmi.com/ Network Merchants, LLC]
| NMI (Network Merchants Inc.)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [http://www.netregistry.com.au/ Netregistry Pty Ltd]
| NetRegistry  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.ogone.com/ Ingenico Payment Services (formerly Ogone)]
| Ingenico ePayments (Ogone e-Commerce)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.paygate.net/ PayGate]
| PayGate Korea  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [http://www.psigate.com/ Payment Services Interactive Gateway Inc.]
| PSiGate XML API
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [http://www.quantumgateway.com/ Quantum Services LLC]
| QuantumGateway - Transparent QGWdatabase Engine
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.quantumgateway.com/ Quantum Services LLC]
| QuantumGateway - XML Requester
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://quickpay.net/ QuickPay ApS]
| QuickPay  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://payments.intuit.com/ Intuit Inc.]
| Intuit QuickBooks Payments  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://www.globalpaymentsinc.com/ Global Payments Inc.]
| Global Payments (formerly Realex)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.sagepay.com/ Sage Pay]
| Sage Pay Go - Direct Interface
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| Built-in, only 3-D Secure v1
| [[File:Check.svg|25px]]
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [https://paya.com/ Paya]
| Paya
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]]
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.securepay.com/ SecurePay.com Inc.]
| SecurePay USA  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.securepay.com.au/ SecurePay - A Business of Australia Post]
| SecurePay Australia
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [https://www.simplify.com/commerce/ MasterCard]
| Simplify Commerce by MasterCard
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [https://www.emerchant.com/skipjack-gateway/ Skipjack Financial Services, Inc.]
| SkipJack
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.suncorp.com.au/ Suncorp]
| Suncorp
| [[File:Check.svg|25px]]
|
|
|
|
|
|
|
|
|
|
|
|
|- style="vertical-align:top;"
| [http://www.usaepay.com/ GorCorp Inc.]
| USA ePay - Transaction Gateway API
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|
|-
! scope="col" style="width: 15%;"| '''Payment service provider'''
! scope="col" style="width: 20%;"| '''Payment system'''
! scope="col" style="width: 6%;"| '''Sale'''
! scope="col" style="width: 6%;"| '''Auth'''
! scope="col" style="width: 10%;"| '''Capture'''
! scope="col" style="width: 6%;"| '''Void'''
! scope="col" style="width: 10%;"| '''Refund'''
! scope="col" style="width: 6%;"| '''Get status'''
! scope="col" style="width: 6%;"| '''Get card'''
! scope="col" style="width: 6%;"| '''Accept'''
! scope="col" style="width: 6%;"| '''Decline'''
! scope="col" style="width: 6%;"| '''Test'''
! scope="col" style="width: 6%;"| '''3D-Secure via Cardinal Commerce'''
! scope="col" style="width: 6%;"| '''Tokenization'''
! scope="col" style="width: 6%;"| '''Account updater'''
|- style="vertical-align:top;"
| [https://www.myvirtualmerchant.com/VirtualMerchant/ Elavon, Inc.]
| Elavon Converge (ex VirtualMerchant)
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|- style="vertical-align:top;"
| [http://www.plugnpay.com/ Plug and Pay Technologies]
| WebXpress
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|
|- style="vertical-align:top;"
| [http://www.worldpay.com/ Worldpay]
| Worldpay Corporate Gateway - Direct Model
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
|
|
|
|
| Built-in, only 3-D Secure v1
|
|
|- style="vertical-align:top;"
| [http://www.worldpay.us/ WorldPay US, Inc.]
| WorldPay Total US  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p, m
|
| [[File:Check.svg|25px]]
|
|
|
|
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
|- style="vertical-align:top;"
| [http://www.worldpay.us/ WorldPay US, Inc.]
| WorldPay US (Lynk Systems)  
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]]
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]] + p
| [[File:Check.svg|25px]] + p
|
|
|
|
|
|
| [[File:Check.svg|25px]]
|
|}

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Supported payment gateways

2020-03-02T09:22:30Z

Mouse: Mouse moved page X-Payments Cloud:Supported payment gateways to XP Cloud:Supported payment gateways: Moving to a new namespace

#REDIRECT [[XP Cloud:Supported payment gateways]]

Template:XPC manual main TOC

2020-03-02T09:19:57Z

Mouse:

# [[XP_Cloud:General_information | X-Payments Cloud: General information]]
# [[XP_Cloud:Getting started | Getting started with X-Payments Cloud]]
# [[XP_Cloud:Two-factor User Authentication | Two-factor User Authentication]]
#* [[XP_Cloud:Setting_up_User_Authentication_with_the_Google_Authenticator_App | with the Google Authenticator App ]]
#* [[XP_Cloud:Setting_up_User_Authentication_with_SMS/Text_Messages | with SMS/Text Messages ]]
#* [[XP_Cloud:Setting_up_User_Authentication_with_Backup_Codes | with Backup Codes]]
#* [[XP_Cloud:Setting_up_an_Additional/Alternative_Method_of_User_Authentication | Adding an Alternative Method ]]
#* [[XP_Cloud:Changing_Your_Preferred_User_Authentication_Method | Changing the Preferred Method]]
# [[XP_Cloud:General Settings | General Settings]]
# [[XP_Cloud:Payment Configurations | Payment Configurations]]
#* [[XP_Cloud:Adding_a_Payment_Configuration | Adding a Payment Configuration]]
#* [[XP_Cloud:Payment_Configurations_List | Payment Configurations List]] 
#* [[XP_Cloud:Viewing_the_Details_of_a_Payment_Configuration | Viewing the Details of a Payment Configuration]] 
#* [[XP_Cloud:Enabling/Disabling_a_Payment_Configuration | Enabling/Disabling a Payment Configuration]] 
#* [[XP_Cloud:Editing_the_Details_of_a_Payment_Configuration | Editing the Details of a Payment Configuration]] 
#* [[XP_Cloud:Deleting_a_Payment_Configuration | Deleting a Payment Configuration]] 
# [[XP_Cloud:3D-Secure Settings | 3D-Secure Settings]]
# [[XP_Cloud:KOUNT Antifraud Screening | KOUNT Antifraud Screening]]
# [[XP_Cloud:NoFraud_Fraud_Prevention | NoFraud Fraud Prevention]]
# [[XP_Cloud:Signifyd_Fraud_Protection | Signifyd Fraud Protection]]
# [[XP_Cloud:Managing Users | Managing Users]]
# [[XP_Cloud:Customizing the User Interface | Customizing the User Interface]]
#* [[XP_Cloud:Customizing the Payment Form Appearance|Customizing the Payment Form Appearance]]
#* [[XP_Cloud:Translating or Editing the User Interface Text |Translating or Editing the User Interface Text ]]
# [[XP_Cloud:Managing Payments | Managing Payments]]
#* [[XP_Cloud:Payments List | Payments List]]
#* [[XP_Cloud:Payment Statuses | Payment Statuses]]
#* [[XP_Cloud:Searching_for_Payments | Searching for Payments]]
#* [[XP_Cloud:Viewing_the_Details_of_a_Payment | Viewing the Details of a Payment]]
#* [[XP_Cloud:Deleting_a_Payment | Deleting a Payment]]
#* [[XP_Cloud:Auth_and_Capture_(Capturing_Funds)|Auth and Capture (Capturing Funds)]]
#* [[XP_Cloud:Voiding_an_Authorization | Voiding an Authorization]]
#* [[XP_Cloud:Issuing_a_Refund | Issuing a Refund]] 
#* [[XP_Cloud:Emulating_Transactions | Emulating Transactions]] 
#* [[XP_Cloud:Clearing_Cardholder_Data | Clearing Cardholder Data]]
# [[XP_Cloud:Supported payment gateways | Supported Payment Gateways]]

XP Cloud:Managing Users

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Managing Users to XP Cloud:Managing Users: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>
At the time of creation of the first user account for access to your X-Payments Cloud, this user account is granted root administrator privileges. Such a user account has full access to all the features of the X-Payments Cloud admin panel. If you can login to X-Payments Cloud and are currently the only user of the admin panel of your X-Payments Cloud instance, you are the root administrator.

X-Payments Cloud, however, can be configured to allow login to its admin panel to more than one user. You, the root administrator, have the ability to create additional admin accounts for your partners or staff, and to specify the set of privileges that needs to be available to each of them.

Unlike the root administrator who has full access to X-Payments Cloud functionality, non-root X-Payments Cloud users have limited privileges. Such users:
* can edit their own user name, email address and password.
* can [[X-Payments:Two-factor_authentication | choose and configure one or more methods of two-factor user authentication]] for personal use;
* can access to payment details/cardholder data - if the respective permission has been given to them by the root admin;
* can view/edit the X-Payments Cloud settings (general / payment processing / appearance / translations) - if the respective permissions have been given to them by the root admin;
* cannot add/manage other user accounts.

====Adding a New User Account====

To add a new user account in X-Payments Cloud:

# In the X-Payments Cloud standalone admin panel, go to the 'Users List' page ('''Settings''' -> '''Users''').
# Click the '''Add user''' button. The 'Create new account' page opens. [[File:xpc_add_user.png|740 px|border]]
# Complete the following fields:
#* '''User name''': Enter a name by which the user will be identified in X-Payments Cloud (letters, digits, hyphens, underscores and the'at' sign are allowed).
#* '''Email''': Enter the user's email address. This will be used for user login and notifications.
#* '''Expiration date''': If you want the user account to be automatically deactivated after a certain period of time, enter the account expiration date. After this date, the account will be locked with the status ''Locked due to account expired''. You will be able to unlock the user by changing the account expiration date. You can leave the field empty to create an account that never expires.
#* '''Inactivity period''': Enter the number of days of account inactivity (not logging in, etc) after which the account will be locked. After the specified number of days of inactivity the user account will be locked with the status ''Locked due to account inactivity''. Recommended values are 1 to 90; if a number outside this range is used, the defined 'Inactivity period' value will be ignored, and the account will be locked automatically after 90 days. The inactivity period is counted from the moment the user last logged in or, if the user never logged in, from the time of account creation.
#* '''Permissions:''' Set user permissions for the user account being created by selecting the sections of the X-Payments back end to which you want the new user to have access.
#* '''Note''': (Optional) Enter a comment for yourself regarding the user account being created. The comment will not be visible to the user.
# Click '''Save changes'''. The user account will be created. An email notification will be sent to the account owner. After you have clicked '''Save changes''', the page will refresh and you will see the 'Account details: <user name>' page with the details of the user account you have just added. You can use this page to edit the account details. For example, you can change the user registration email address or activate the option "Force to change password on next login" to request that the user changes their password on their next login to X-Payments Cloud.

Note that after a user account is created, it needs to be activated by the account owner. User accounts that have not yet been activated have the status ''Waiting for email activation''.
:[[File:xpc_user_waiting4account_activation.png|740 px|border]]
To activate their newly created user account, a user must use the account activation link provided in the 'account created' notification message sent to their email address. After clicking on this link the user will be prompted to set their password for access to the X-Payments Cloud back end. After successful account activation, the status of the user account in X-Payments Cloud will be updated to ''Active''.

====Users List====

Existing user accounts can be viewed and managed on the 'Users List' page ('''Settings''' -> '''Users'''):

: [[File:XP2.0_users_list.png|border]]

For each user account on the list, you can see its current status. The possible account statuses are as follows:
* '''Full permissions''': This is the permanent status used for the X-Payments root admin. It cannot be changed nor assigned to any other user in X-Payments.
* '''Active''': This is the normal working status of a user account; it means that the user can log in to the X-Payments back end and perform actions within the permissions scope defined by their account details. The 'Active' status is set for all user accounts automatically after account activation / email address change confirmation by the user; it can also be assigned to a user account manually by the root admin after the account was locked (see the instructions for changing the account status below).
* '''Waiting for email activation''': This is an automatic status; it is used for newly created user accounts before account activation by the account owner.
* '''Waiting for email verification''': This is an automatic status; it is used for user accounts for which registration email address has been changed by the X-Payments root admin, but the change has not yet been confirmed by the account owner.
* '''Waiting for password recovery''': This is an automatic status; it is used for user accounts for which password recovery has been requested.
* '''Locked due to account inactivity''': This is an automatic status assigned to a user account after the expiration of the account inactivity period, as provided by the user account details (see the instructions for [[#Changing a User's Account Status|Changing a User's Account Status]]).
* '''Locked due to danger activity''': This is an automatic status temporarily assigned to a user account for which repeated failing login attempts are detected (related to the 'Dangerous activity blocking period (minutes)' option in X-Payments [[X-Payments:General_settings|General settings]]).
* '''Locked due to account expired''': This is an automatic status assigned to a user account after the account expiration date, as provided by the user account details. To unlock a user account in this state, X-Payments root admin must change the 'Expiration date' value in the account details.
* '''Locked by administrator''': This is a status that can be used to temporarily disable a user account; it can be set manually by the X-Payments root admin (see the instructions for [[#Changing a User's Account Status|Changing a User's Account Status]]).

On this page you can:
* Open the details of a specific user account for viewing/editing;
* Lock active user accounts / unlock user accounts with the ''Locked by administrator'', ''Locked due to danger activity'' and ''Locked due to account inactivity'' status;
* Delete user accounts.

====Viewing a User's Account Details====

To view the details of a specific user account, click on the user name in the Users List. The 'Account details: <user name>' page opens showing all the information related to the user account:

:[[File:XP2.0_account_detail_admin_view.png|border]]

On this page you can:
* View/edit the user account details (user name, email address, expiration date, inactivity period, user permissions, etc);
* Change the user account status (lock the account if it is active / unlock the account if it is locked);
* Delete the user account.

====Editing a User's Account Details====
The 'Account details: <user name>' page allows you to edit the details of a specific user account.

To edit such details as user name, expiration date, inactivity period, user permissions and comment about the user, simply edit the contents of the respective fields and click '''Save changes'''.

To change the user's email address:
# Click on the 'Change user email' link: [[File:XP2.0_change_user_email_link.png]] The 'Change user email' box will be expanded providing a field where you can enter a new email address: [[File:XP2.0_change_user_email_box.png]]
# Use the '''New e-mail''' field to enter a new email address.
# Click '''Change'''. After you click the '''Change''' button, a notification will be sent to the email owner with a confirmation link. The user will need to click on this link to confirm the change of the email address. The email address stored in the user account details will be updated only after the confirmation. Until that time the email address in the user's account details will be displayed like so: ''<old email address>'' will be changed to ''<new email address>''

====Changing a User's Account Status====
The current status of a user account is visible on the 'Users List' page:
: [[File:XP2.0_account_status.png|border]]
and on the 'Account details: <user name>' page:
: [[File:XP2.0_account_status1.png|border]]

To change the status of a user account, do one of the following:
* On the 'Users List' page, click the button dropdown element opposite the user name and select the required action (''Lock'' / ''Unlock'') from the menu: [[File:XP2.0_lock_user_l.png|border]] 
* On the 'Account details: <user name>' page, click the button dropdown element at the bottom of the page and select the required action (''Lock account''/''Unlock account''): [[File:XP2.0_lock_user_detpage.png|border]] 

====Requesting Password Change for a User Account====
There may be times when you will want to request that one or more users of your X-Payments installation change their X-Payments password(s). To request password change:
* On the 'Account details: <user name>' page, select the '''Force to change password on next login''' check box and click '''Save changes'''.

====Deleting a User Account====
To delete a user account, do one of the following:
* On the 'Users List' page, click the button dropdown element opposite the user name and select the required action (''Delete account'') from the menu. Confirm the deletion. 
* On the 'Account details: <user name>' page, click the button dropdown element at the bottom of the page and select the required action (''Delete account''). Confirm the deletion.

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Signifyd Fraud Protection

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Signifyd Fraud Protection to XP Cloud:Signifyd Fraud Protection: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__

X-Payments Cloud provides an integration with [https://www.signifyd.com/ Signinfyd], a popular fraud protection solution for e-commerce.

When a buyer places an order in a store connected to X-Payments Cloud with Signifyd protection enabled, the order information gets sent to Signifyd. Signifyd creates a case for the order within the Signifyd Console evaluating the respective payment transaction via its own proprietary algorithms. As a result of this evaluation, the transaction is assigned a certain score reflecting its level of safety/riskiness for the merchant. The merchant can set a specific score threshold level that will enable them to know that a transaction is safe and may be processed automatically. If a transaction is deemed risky (potentially fraudulent), it will be marked as requiring manual review by the merchant. The merchant can then investigate the order information in the Signifyd Console and make an informed decision as to whether they should accept or decline the respective payment transaction.

More information on Signifyd is available on the Signifyd website:
* [https://www.signifyd.com/how-it-works/ How it works]
* [https://www.signifyd.com/resources/ Resources]

==Setting up your Signifyd integration==
To start using Signinfyd to score the payment transactions that take place in your store connected to X-Payments Cloud, complete the following steps: 

# Contact Signifyd Sales team to apply for a Signifyd account. 
# Log in to X-Payments Cloud.
# Go to the General settings page ('''Settings''' -> '''General''') and specify that you are going to use Signifyd as your Antifraud service: 
## Scroll down the page to the Services section.
## In that section, use the '''Antifraud service''' box to select "Signifyd - Guaranteed Fraud Protection". [[File:xpc_select_signifyd.png|740px|border]] 
## Click '''Save''' at the bottom of the page to save your changes.
# Now if you look again at the '''Antifraud service''' setting on the same page, you will see that Sygnifyd has been selected as your Antifraud service, and the page now provides a link to configure it. [[File:xpc_signifyd_selected.png|740px|border]] Click on the Configure link to access the page for Signifyd configuration and adjust the Signifyd settings: [[File:Xp_signifyd_configure_link.png|740px|border]] The page for Signifyd configuration opens: [[File:Xpc_signifyd_settings_page.png|740px|border]] 
# In a new browser tab or window, go to the Signifyd console at https://app.signifyd.com/ [[File:xp31_signifyd_app_login_screen.png|740px|border]] Make sure you have a ''team'' set up in your Signifyd account (See "[https://www.signifyd.com/resources/faq/working-with-teams/how-do-i-create-a-team/ How do I create a team]"). Also make sure you have an ''API key'' generated for that team (See "[https://www.signifyd.com/resources/faq/api/how-do-i-create-an-api-key/ How do I create an API key]").
# On the page with Signifyd configuration settings in X-Payments Cloud, find a URL in the field marked "Enter the following URL in the Webhook Address field". The URL should look like https://<your_xpayments_domain>/callback.php. Copy this URL to clipboard, switch back to the browser tab or window where you have the Signifyd console open.
# Go to the [https://app.signifyd.com/settings/notifications Notifications] page, scroll down to the Webhooks section.
# Use the Webhooks section to add some webhooks. To create a webhook, paste the URL you have copied into the '''Webhook Address''' field, then select the proper '''Team''' and '''Event Type''' values. [[File:xp31_signifyd_notifications_webhooks.png|740px|border]] You should create webhooks for each of the following event types:
#* Case Creation,
#* Case Rescore,
#* Case Review,
#* Guarantee Completion. As a result, the contents of your Webhooks section should look similar to the following: [[File:xp31_signifyd_notifications_webhooks1.png|740px|border]]
# Get the API key for your Signifyd team, go back to the browser tab or window with X-Payments and paste the API key into the '''API Key''' field on the page with your Signifyd configuration settings.
# If you want X-Payments to give you a warning when Signifyd score for a transaction is below a certain threshold, set the threshold value using the '''Warning score threshold''' setting on the Signifyd configuration settings page in X-Payments Cloud. Signifyd score is a value from 0 to 1000; 0 indicates the highest risk of fraud, 1000 indicates the lowest risk. For example, if you set the threshold to 600, and a transaction gets a score of 473, it will be deemed potentially fraudulent and flagged for manual review.
# Click '''Save''' to save your Signifyd configuration in X-Payments Cloud. [[File:xpc_signifyd_settings_page1.png|740px|border]] 
# Make sure the status of your Signifyd configuration in X-Payments Cloud is ''Enabled'': [[File:xpc_signifyd_enabled.png|740px|border]] 
# Go back to the tab or window with the Signifyd console and test the webhooks you have created. For each of the webhooks, click the '''Test''' button. Provided that X-Payments Cloud has been connected to your Signifyd account correctly, you should see the message "Event successfully posted" shown on the same line with the webhook you are testing: [[File:xp31_signifyd_event_successfully_posted.png|740px|border]] 
That is all. Signifyd is ready to use with X-Payments Cloud.
 

==Using Signifyd to score transactions==
Once a payment transaction is scored by Signifyd, you will be able to view the results of the check conducted by Signifyd on the Payment details page created for this payment in your X-Payments Cloud admin panel. For example, here you can see the result of a passed check (with Signifyd Warning score threshold set to 300): [[File:xpc_signifyd_fraud_check_passed.png|740px|border]] 
And here is the result of a check through Signifyd for a similar order paid for using the same card, but with Signifyd Warning score threshold set to 600 (Manual review is required): [[File:xpc_signifyd_fraud_check_review_required.png|740px|border]] 
You can find out more about how Signifyd scores transactions from this article:
* [https://www.signifyd.com/resources/faq/general/how-does-signifyd-score-a-transaction/ How does Signifyd score a transaction?]
 
You can view the detailed Signifyd check results for the transaction by following the link "Transaction details on the Signifyd web-site: <Signifyd Case ID>". This way you can learn more about the transaction to decide whether it will be safe to accept it. 
You can also control the case financial guarantee by Signifyd using the button in the same section. [https://www.signifyd.com/resources/manual/signifyd-guarantee/signifyd-guarantee/ See more info on case guarantee]

To view Signifyd results in your online store's admin panel, go to the section where you view order details. The result of checking by Signifyd will be available in the order details similarly to what you see in X-Payments Cloud. For example, in X-Cart 5 you can do it as follows:
# On the '''Orders''' > '''Orders list''' page, select the order and open its details for viewing. 
# Scroll down the page till you see the box with the information on the card that was used to pay for the order and click on the 'View payment information' link. [[File:xpc_view_order_xc_payment_info_signifyd.png|740px|border]] The Signifyd result will be shown along with the rest of the information regarding the payment: [[File:xpc_view_order_xc_payment_signifyd_info.png|740px|border]] 

[[Category:X-Payments Cloud User Manual]]

XP Cloud:NoFraud Fraud Prevention

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:NoFraud Fraud Prevention to XP Cloud:NoFraud Fraud Prevention: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__

X-Payments Cloud provides integration with [https://www.nofraud.com/ NoFraud]. NoFraud is a comprehensive fraud prevention service that employs every known fraud prevention technology in a single centralized system, producing the most precise decision-making fraud prevention application. NoFraud sits between your store site and your payment gateway reviewing payment transactions in real time through complex algorithms so that only the legitimate transactions are sent to the gateway for processing. Any transactions declined by NoFraud are bounced back to the customer while they are still at the cart. Approved transactions are passed along to the gateway for uninterrupted processing. For the small percentage of transactions where a Pass or Fail decision is not available, NoFraud can contact the cardholder for verification. This eliminates the need for manual review of transactions and prevents the declining of legitimate customers. NoFraud takes just a few minutes to set up and does not require training or dedicated staff to run or maintain. With no setup fees and low per-transaction billing rates, NoFraud allows anyone to try the system with little risk. All you need to do is choose a plan to match your needs. You can even get a free trial by contacting NoFraud at info@nofraud.com or 888-773-3669.

==Getting started with NoFraud==

To start using NoFraud, complete the steps below:
# If you have not yet done so, [https://portal.nofraud.com/users/sign_up sign up for a NoFraud account]. [[File:xpc_nofraud_signup.png|740px|border]] 
# After creating your NoFraud account, log in to the [https://portal.nofraud.com/users/sign_in Account Manager] portal. [[File:xpc_nofraud_login.png|740px|border]] On the bottom left of your portal account, you will see a few tabs that require merchant information input. Make sure all the required information for your account has been provided correctly. NoFraud provides some help guides and references in the "Resources" section that you may find helpful. For example, the [https://portal.nofraud.com/resources/NoFraud-Portal-Guide.pdf NoFraud Portal Guide] provides a thorough explanation of all the settings. Please pay particular attention to the "Integration" tab. Through this tab, you will need to select the type of integration you are using. From the 'Add new integration' menu, select the 'Direct API' method. After adding your integration in your portal account, you will get an '''API key''' code for your integration (this code is generated automatically). [[File:xp3_nofraud_integration.png|600px|border]] You will need to copy this code from your account and input it into the appropriate field in the X-Payments Cloud admin panel, so for now simply copy the code to clipboard. 
# In a new browser tab or window, log in to the X-Payments Cloud admin panel, go to the General settings page ('''Settings''' -> '''General''') and specify that you are going to use NoFraud as your Antifraud service: 
## Scroll down the page to the Services section.
## In that section, use the '''Antifraud service''' box to select "NoFraud - Full Service Fraud Prevention". [[File:xpc_select_nofraud.png|740px|border]] 
## Click '''Save''' at the bottom of the page to save your changes.
# Now if you look again at the '''Antifraud service''' setting on the same page, you will see that NoFraud has been selected as your Antifraud service, and the page now provides a link to configure it. [[File:xpc_nofraud_selected.png|740px|border]] Click on the Configure link to access the page for NoFraud configuration and adjust the NoFraud settings: [[File:Xp_nofraud_configure_link.png|740px|border]] The page for NoFraud configuration opens: [[File:Xpc_nofraud_settings_page.png|740px|border]] 
# Adjust the settings on the NoFraud settings page. Be sure to click '''Save''' to save your changes. 
#* '''Status''' (Not configured / Enable / Disable): This setting indicates whether NoFraud module is active. For now just leave it as is. After you provide the rest of the required settings (below) and save the changes, NoFraud module will be enabled automatically. You will then be able to use this setting to disable/re-enable NoFraud for your current payment configuration as you require.
#* '''API key''': Use this field to input the API key code you have obtained in your NoFraud portal account.
#* '''Test/Live mode''': Set the mode for your NoFraud integration. Note that this setting must match the mode you have chosen for your NoFraud integration in your portal account settings. 
# Make sure NoFraud fraud prevention service is enabled: [[File:Xp_nofraud_enabled.png|740px|border]] 
That is all; NoFraud service has been activated. From now on, any payment transactions via X-Payments Cloud will be screened by NoFraud.
 

==Using NoFraud==
Once activated in X-Payments Cloud, NoFraud works automatically for all the incoming payments.

What happens when a buyer submits their credit or debit card info to pay for an order in a store accepting payments via X-Payments Cloud and protected by NoFraud?

Technically, the process involves three steps:

At the first step, X-Payments Cloud makes a call to NoFraud to invoke NoFraud fraud screening service. In this call, information about the payment transaction (including the IP address, email address, shipping address, card details, billing info, order details, etc.) is submitted to NoFraud. This happens for each new card prior to contacting the payment gateway.
NoFraud’s fraud screening service uses proprietary algorithms to check the information submitted to it and applies the custom rules configured for the merchant's account. NoFraud account settings provide substantial flexibility for configuring the rules. In practice, NoFraud will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, NoFraud’s fraud screening service responds with a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined). X-Payments will honor the decision returned by NoFraud. If the decision is to process the transaction, X-Payments Cloud will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments Cloud will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen.

At the second step, X-Payments Cloud contacts the payment gateway for order processing. This, of course, does not happen for transactions that have been blocked.

At the third step, X-Payments Cloud once again contacts NoFraud to find out the transaction result, including the results of the CVV и AVS checks. NoFraud's fraud screening service also stores this information for future use.

The results of checking by NoFraud can be viewed in X-Payments Cloud, in the admin panel of the online store and in the NoFraud portal.

To view NoFraud results in X-Payments Cloud:
# Go to the Payments page and locate the payment for which you would like to view the NoFraud results.
# Open the payment details for viewing. On the Payment details page, you will be able to see whether the NoFraud check has been passed successfully of failed in the 'NoFraud - Full Service Fraud Prevention' section: [[File:xpc_nofraud_passed_xp.png|740px|border]] If NoFraud is not able to set either 'passed' or 'failed' status right away, it sets the status 'Being reviewed by NoFraud'. The status 'Being reviewed by NoFraud' means that NoFraud needs time to conduct additional customer verification. Once the process is completed, NoFraud will send the final verification result to the X-Payments Cloud administrator by email. Note that the NoFraud status of the payment in X-Payments Cloud will ''not'' be updated. 

To view NoFraud results in your online store's admin panel, go to the section where you view order details. The result of checking by NoFraud will be available in the order details similarly to what you see in X-Payments Cloud. For example, in X-Cart 5 you can do it as follows:
# On the '''Orders''' > '''Orders list''' page, select the order and open its details for viewing. 
# Scroll down the page till you see the box with the information on the card that was used to pay for the order and click on the 'View payment information' link. [[File:xpc_view_order_xc_payment_info.png|740px|border]] The NoFraud result will be shown along with the rest of the information regarding the payment: [[File:xpc_view_order_xc_payment_nofraud_info.png|740px|border]] 

To view the results of a NoFraud check in the NoFraud portal, simply follow the transaction id link provided in the details of the payment in X-Payments Cloud. [[File:xpc_nofraud_result_link2portal.png|740px|border]] 

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:NoFraud Fraud Prevention

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:NoFraud Fraud Prevention to XP Cloud:NoFraud Fraud Prevention: Test page move from API

#REDIRECT [[XP Cloud:NoFraud Fraud Prevention]]

X-Payments Cloud:Signifyd Fraud Protection

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Signifyd Fraud Protection to XP Cloud:Signifyd Fraud Protection: Test page move from API

#REDIRECT [[XP Cloud:Signifyd Fraud Protection]]

X-Payments Cloud:Managing Users

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Managing Users to XP Cloud:Managing Users: Test page move from API

#REDIRECT [[XP Cloud:Managing Users]]

XP Cloud:Customizing the User Interface

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Customizing the User Interface to XP Cloud:Customizing the User Interface: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>
X-Payments Cloud provides a lot of flexibility allowing you to change the appearance of the payment form for your customers and, should you require that, to change the wording of any text element in the user interface of the X-Payments Cloud admin panel or payment form.
For more information, see the following topics:
* [[X-Payments_Cloud:Customizing the Payment Form Appearance|Customizing the Payment Form Appearance]]
* [[X-Payments_Cloud:Translating or Editing the User Interface Text |Translating or Editing the User Interface Text ]]

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Payment Statuses

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Payment Statuses to XP Cloud:Payment Statuses: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

You can find out the status of any payment made in your online store via X-Payments Cloud by looking at the [[X-Payments_Cloud:Payments_List | payments list]]. The status is will be shown in the Status column.

The possible payment statuses are as follows:
* ''Authorized'' - The money in the customer's account has been placed on hold to ensure the availability of funds for capture.
* ''Charged'' - The payment amount has been moved from the customer's account to the merchant's account.
* ''Refunded'' - The payment has been returned to the customer.
* ''Partially refunded'' - The payment has been partially returned to the customer.
* ''Declined'' - The payment has been declined (The payment gateway declined the transaction or canceled the payment authorization, or the customer refused to complete the payment).

You can check the meanings of specific payment statuses using the Transaction statuses legend table in the lower part of the Payments page.
:[[File:xpc_transaction_statuses.png|640px|border]]

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Managing Payments

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Managing Payments to XP Cloud:Managing Payments: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

Payments made in your online store via X-Payments Cloud can be viewed and managed using the Payments page.

For more information on the specific features and user actions related to payments see the following articles:

* [[X-Payments_Cloud:Payments_List | Payments List]] 
* [[X-Payments_Cloud:Payment_Statuses | Payment Statuses]] 
* [[X-Payments_Cloud:Searching_for_Payments | Searching for Payments]] 
* [[X-Payments_Cloud:Viewing_the_Details_of_a_Payment | Viewing the Details of a Payment]] 
* [[X-Payments_Cloud:Deleting_a_Payment | Deleting a Payment]] 
* [[X-Payments_Cloud:Auth_and_Capture_(Capturing_Funds)|Auth and Capture (Capturing Funds)]] 
* [[X-Payments_Cloud:Voiding_an_Authorization | Voiding an Authorization]] 
* [[X-Payments_Cloud:Issuing_a_Refund | Issuing a Refund]] 
* [[X-Payments_Cloud:Managing_High_Risk_Transactions_(Accept/Decline) | Managing High Risk Transactions (Accept/Decline)]] 
* [[X-Payments_Cloud:Emulating_Transactions | Emulating Transactions]] 
* [[X-Payments_Cloud:Clearing_Cardholder_Data | Clearing Cardholder Data]] 
* [[X-Payments_Cloud:Tokenization_and_Re-Use_of_Saved_Credit_Cards | Tokenization and Re-Use of Saved Credit Cards ]] 

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Customizing the User Interface

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Customizing the User Interface to XP Cloud:Customizing the User Interface: Test page move from API

#REDIRECT [[XP Cloud:Customizing the User Interface]]

X-Payments Cloud:Managing Payments

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Managing Payments to XP Cloud:Managing Payments: Test page move from API

#REDIRECT [[XP Cloud:Managing Payments]]

X-Payments Cloud:Payment Statuses

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Payment Statuses to XP Cloud:Payment Statuses: Test page move from API

#REDIRECT [[XP Cloud:Payment Statuses]]

XP Cloud:Searching for Payments

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Searching for Payments to XP Cloud:Searching for Payments: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

X-Payments Cloud allows you to filter the [[X-Payments_Cloud:Payments List |payments list]] to find specific payments based on certain criteria.

To search for a payment or a group of payments:
# Click on the Advanced search link above the Payments table to access the Advanced search form: [[File:xpc_payments_table_advanced_search.png|640px|border]]
# In the Advanced search form, specify your search criteria:
#* '''Reference ID''': Reference ID associated with the payment(s). Reference ID is obtained from the online store. It identifies the online store order for which the payment was made.
#* '''Customer name''': Name of the customer associated with the payment(s).
#* '''Email''': Email address of the customer associated with the payment(s).
#* '''Payment configuration''': The payment configuration that was used for the payment(s).
#* '''Customer IP''': The IP address of the customer associated with the payment(s).
#* '''Payment ID''': The payment ID.
#* '''Status''': Specify the payment statuses you want to be displayed.
#* '''Date''': Specify the time period during which the payment(s) were submitted/updated.
#* '''Amount''': Specify the currency that was used for the payment(s) and the payment amount range.
#* '''All payments related to this one''': If searching for all the payments associated with a specific payment, enable this checkbox.
# Click '''Search payments'''. The Advanced search will be closed, and you will see a list of payments filtered according to the search criteria you have provided.

To clear the Advanced search form and start over, use the '''Reset form''' button at the bottom of the form.

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Customizing the Payment Form Appearance

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Customizing the Payment Form Appearance to XP Cloud:Customizing the Payment Form Appearance: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>
X-Payments Cloud provides an interface for the customization of its payment form. The appearance of the payment form can be changed via the Appearance page of your X-Payments Cloud admin panel ('''Settings''' -> '''Appearance''').
:[[File:xpc_appearance_page_link.png|740px|border]] 
Note that this page is available only from the X-Payments Cloud standalone admin panel (not if accessed from within the admin panel of your online store.

Here is what the Appearance page looks like:
:[[File:xpc_appearance.png|740px|border]] 

First, you need to select the template that will determine the appearance of your payment form.
At the top of the page, there is a template selector in the '''Select template''' box. The selector provides access to a few pre-configured templates based on different color schemes.
:[[File:xpc_appearance_select_tpl.png|740px|border]] 
After selecting the template you require from the drop-down list, below the template selector, you will be able to preview the way your payment form will look based on this template.
Simply choose the template that best suits your preference, but do not worry if the fonts or the color combination used by the template are not ideal - you will be able to tweak the template at a later time.

Second, you need to adjust the payment form layout settings:

* '''Ask for Cardholder name''': This setting determines whether Cardholder name input via the payment form should be enabled. If you disable the "Ask for Cardholder name" option here, the Cardholder name will be taken from the buyer's completed billing address form.

* '''Display "Save card" option enabled by default''': This setting affects only payment configurations that support tokenization. It determines the initial state of the check box option to save the payment card for future use with the store - as shown to the customer on the payment form. (NB: This option is titled "I want to use this credit card for my future orders in this shop"). If you enable the option 'Display "Save card" option enabled by default', the payment form will be loaded for your customers with the "Save card" option pre-enabled; your customers will be able to disable it if they wish to. If you keep this option disabled, the check box option to save the card will be first loaded as disabled; your customers will be able to enable it.

After adjusting the payment form layout settings, be sure to save your changes by clicking '''Save'''.
:[[File:xpc_appearance_save.png|740px|border]]

If, after completing the above steps, you are still not quite happy with the appearance of your payment form, it is possible to tweak the payment form template to further improve the form appearance.

To work on your template, click on the Edit link next to the name of your chosen payment form template in the '''Select template''' box:
:[[File:xpc_appearance_edit_default_link.png|740px|border]]
(Note that the Edit link is provided only for the template that is active currently; after changing the template selection in the '''Select template''' box, you have to save the payment form settings with the '''Save''' button for the Edit link to appear for the newly selected template. For example, before you make any changes to your payment form settings, the form uses settings by default, and its appearance is determined by the template named "Default". This "Default" template has the Edit link from the very start, and you can see it as soon as you enter the Appearance page ('''Settings'''>'''Appearance''') for the first time. If you then switch the template selector to a different template - for instance, "Orange" - the Edit link that used to be displayed next to the template selector disappears. Not to worry, this state is temporary: after you save the payment form layout settings with the '''Save''' button at the bottom of the page, the new teplate - "Orange" - will be activated for your payment form, and the Edit link will reappear.)

After you click on the Edit link, the selected template settings are opened for editing:
:[[File:xpc_appearance_edit_default.png|740px|border]]

As you can see from the screenshot above, we have chosen to work on the template "Default". On this page, we can view and adjust all the aspects of the payment form appearance that are controlled by this template. On the left-hand side of the page, there is a preview of the payment form that allows us to preview the changes we make.

# Create a copy of the template "Orange". To do so, click the button '''Save copy as...''' below the payment form preview area: [[File:xp3_templates_save_copy.png|700px|border]] A popup form appears on the screen allowing you to enter a name for your template copy: [[File:xp3_templates_save_copy1.png|700px|border]] Simply replace the name of the original template with a new one (Below you can see how we changed the name "Orange" to "test") and click '''Save''': [[File:xp3_templates_save_copy2.png|700px|border]] The template copy will be created: [[File:xp3_templates_save_copy3.png|700px|border]] Now you can safely play with the settings on the template copy without running the risk of spoiling the original template (in our case, "Orange"). If you do not like the result, you will be able to discard the template copy and start anew at any time.
# The settings below the template selector allow you to adjust the various aspects of the payment form appearance. Click the tabs ('''General styles''', '''Logo and header''', '''Payment info''', '''Card details''' and '''Buttons''') to access the settings you require. [[File:xp3_templates_edit_tabs.png|700px|border]] To change the template, try changing the original styles to the ones you require. Your changes will be shown on the preview in real time: [[File:xp3_templates_test_edited.png|700px|border]] 
# Click '''Save''' to save the changes: [[File:xp3_templates_test_save.png|700px|border]] Now you have a new template which you can select when configuring your [[X-Payments:Managing_store_connections | online stores]].
# If necessary, you can delete the template or save its copy under a new name: [[File:xp3_templates_delete_saveas.png|700px|border]] 

See also:

* [[X-Payments_Cloud:Translating or Editing the User Interface Text |Translating or Editing the User Interface Text ]]

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Translating or Editing the User Interface Text

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Translating or Editing the User Interface Text to XP Cloud:Translating or Editing the User Interface Text: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>
Text elements that appear in the X-Payments Cloud user interface (words, phrases and sentences - both in the X-Payments Cloud admin panel and on the payment form where your customers enter their payment card information) are specified with the help of text labels. This enables you to easily change the wording of these text elements or translate them into other languages. This can be done using the section Translations page of your X-Payments Cloud admin panel ('''Settings''' -> '''Translations'''):
:[[File:xpc_translations_page_link.png|740px|border]] 
Note that this page is available only from the X-Payments Cloud standalone admin panel (not if accessed from within the admin panel of your online store.

Below you can see what this page looks like in the X-Payments Cloud admin panel:
:[[File:xpc_translations.png|740px|border]] 

You can take the following approaches when customizing the user interface text in X-Payments Cloud:

* Translate the entire user interface of X-Payments Cloud - or just the part visible to customers - into another language (or more than one languages);
* Override the text of individual labels.

To change a certain text label in X-Payments (or to translate it into another language):
# Complete the following fields:
#* '''Language code (2-letter)''' - Enter the two-letter ISO code of the language for which the label is intended. The default language of text elements in X-Payments Cloud is English, so if you want to add a new value for a text label in the English language - so this new value will override the original one - specify "EN". To add a translation into another language, specify the two-letter ISO code of the target language; for example, to translate something into French, specify "FR".
#* '''Original label''' - Quote the original text label used in X-Payments (in the English language).
#* '''Translation''' - Add the phrase/translation that you want to use in the place of the original label.
# Click '''Add new'''. [[File:xpc_translations_add.png|740px|border]] 
As a result, the updated text label/translation will be added to the list of modified text labels above. For example, in the screenshot below you can see such a label:
:[[File:xpc_translations_add1.png|740px|border]] 
Now when a user selects a language for which modified versions of some text labels have been added via the Translations page, the text in the X-Payments Cloud user interface will be displayed based on the modified versions of the labels.

See also:

* [[X-Payments_Cloud:Customizing the Payment Form Appearance|Customizing the Payment Form Appearance]]

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Searching for Payments

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Searching for Payments to XP Cloud:Searching for Payments: Test page move from API

#REDIRECT [[XP Cloud:Searching for Payments]]

X-Payments Cloud:Translating or Editing the User Interface Text

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Translating or Editing the User Interface Text to XP Cloud:Translating or Editing the User Interface Text: Test page move from API

#REDIRECT [[XP Cloud:Translating or Editing the User Interface Text]]

X-Payments Cloud:Customizing the Payment Form Appearance

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Customizing the Payment Form Appearance to XP Cloud:Customizing the Payment Form Appearance: Test page move from API

#REDIRECT [[XP Cloud:Customizing the Payment Form Appearance]]

XP Cloud:Payments List

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Payments List to XP Cloud:Payments List: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

You can find the list of all the payments made by your customers using your X-Payments Cloud enabled payment method on the Payments page. This list is presented in the form of a table:
: [[File:xpc_payments_page.png|740px|border]]

For each individual payment the following information is available:
* '''Payment''' - The payment's ID number.
* '''Order''' - Reference ID of the order to which the payment pertains. For card setup payments (authorizations made when saving a card in a customer's profile without placing an order) this shows as 'Card setup'. [[File:xpc_payments_list_order_cardsetup.png|500px|border]] For tokenized payments (payments made using a card saved in a customer's profile for use in the store or previously saved as a method of payment on subscription), the Reference ID of the original order (the one associated with the initial payment in which the token for the payment card was saved) and a link to the details of the initial payment are provided. [[File:xpc_payments_list_order_referenceid.png|500px|border]] If there is no original order (the card was saved in the user profile without placing an order), a link to the card setup payment is provided: [[File:xpc_payments_list_order_from_cardsetup.png|500px|border]] 
* '''Origin''' - Information about the payment origin. For original payments, this shows as "Customer". For tokenized payments (payments made using a card saved in a customer's profile for use in the store or previously saved as a method of payment on subscription), this shows as a link to the original payment in which the card token was obtained. [[File:xpc_payments_list_origin_payment_number.png|500px|border]] 
* '''Submitted''' - Date and time when the payment was submitted.
* '''Last update''' - The last time that the payment was updated.
* '''Status''' - The payment status (See [[#Payment Statuses|Payment Statuses]] for more information).
* '''Payment configuration''' - The payment configuration that was used to conduct the payment.
* '''Customer IP''' - The IP address of the customer who made the payment.
* '''Amount''' - The payment amount.

The table in the screenshot above does not provide all the above-listed types of information because some of the columns are hidden. You can change the set of visible columns in the Payments table as follows:
# Click on the Settings button in the table header: [[File:xpc_payments_table_settings.png|740px|border]]
# Specify the columns that you want to be displayed by selecting the respective checkboxes. [[File:xpc_payments_table_columns.png|740px|border]]
# Click '''Apply'''.

It is possible to change the sort order of payments. To change the way the payments are sorted, simply click on the table column headers. The table header will reflect the selected method of sorting:
:[[File:xpc_payments_table_sorting.png|740px|border]]

It is possible to filter payments / find specific payments based on certain criteria. See [[#Filtering payments / Advanced search|Filtering payments / Advanced search]]

On the Payments page you can:
* Open the details of a specific payment for viewing;
* Clear cardholder data for some or all payments ('''Note''': The user does not have to have the [[X-Payments:Managing_users|permission]] to view cardholder data to be able to clear cardholder data);
* Delete payments;
* Capture payments with the 'Authorized' status.

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Issuing a Refund

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Issuing a Refund to XP Cloud:Issuing a Refund: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

Depending on the payment gateway you use, you may be able to refund payments received from your customers. Some payment gateways support only full refunds, whereas others support both full and partial refunds.

To issue a refund in X-Payments Cloud:

# In the list of payments on the Payments page, locate the payment you require.
# Click on the payment ID link. [[File:xpc_refund0.png|740px|border]] The page with the payment details - the Payment details page - will be displayed. 
# On the Payment details page, locate the section for Refund actions: [[File:xpc_refund.png|740px|border]]. By default, the input box in this section shows the full amount that has been charged and is now available for refund. You can use this amount without change or - if you need to issue a partial refund - you can edit this amount specifying the amount you require. 
# Click '''Refund'''. The specified amount will be refunded.

Sometimes, even when the payment gateway supports refunds, you may not be able to issue a refund for some payment transactions. For example, if using Authorize.Net you cannot refund your customer before the payment transaction has been submitted for settlement. (For Authorize.Net transactions, funding takes place after settlement; before settlement, no money can be returned to the buyer since no money has yet been captured.) In such situations, an attempt to issue a refund of the payment via X-Payments Cloud will fail. To resolve this issue, in the case of a failed refund attempt, X-Payments Cloud will automatically attempt to void the initial transaction.

'''Attention Authorize.Net users''':
To ensure the correct processing of Authorize.Net refunds, you need to make sure that the option selected in the "Expanded Credit Capabilities" setting in the payment configuration for Authorize.Net in X-Payments matches the respective setting in your merchant account. More information on Expanded Credit Capabilities (ECC) is available here: https://account.authorize.net/help/Miscellaneous/Pop-up_Terms/Expanded_Credit_Capabilities.htm

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Issuing a Refund

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Issuing a Refund to XP Cloud:Issuing a Refund: Test page move from API

#REDIRECT [[XP Cloud:Issuing a Refund]]

XP Cloud:Auth and Capture (Capturing Funds)

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Auth and Capture (Capturing Funds) to XP Cloud:Auth and Capture (Capturing Funds): Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

Depending on the type of order fulfillment process used by your store, you may choose to set up your account in such a way that the capture of funds from your buyers' accounts will not happen automatically at the time of payment processing, but will be delayed so you can capture the funds manually at a later time (You will need to ensure that your preferred payment gateway supports this feature).

'''To enable the manual capture of transactions in X-Payments Cloud''', you will need to adjust your payment configuration settings accordingly:

# Go to the Payment processing page (Settings -> Payment processing) and locate the payment configuration for which you need to enable manual capture. Open the details of this payment configuration for viewing/editing.
# On the Payment configuration details page, set the '''Initial transaction''' to ''Auth'': [[File:xpc_initial_transaction.png|border]] Choosing ''Auth'' ensures that, when a customer makes a payment, the payment amount will be authorized, but not captured - until the time you decide to capture funds manually. {{Note|In the case of ''Auth and capture'', the authorization is immediately followed by automatic capture, so you will not have to or be able to capture the funds manually.}}

'''To capture the funds after an 'Auth' transaction''', use one of the following methods:

''Method 1:''
This method is good for when you need to capture the entire authorized amount (not good for partial capture).

# In the list of payments on the Payments page, locate the 'Authorized' payment for which you need to do a capture.
# Click on the '''Capture''' button displayed next to the payment status. For example, to capture $54.53 for the payment 60137553979 (000025-9FKZ), we will need to use this button: [[File:xpc_capture_auth_listview.png|740px|border]] The authorized amount will be captured. The Payment details page will open showing you the updated payment details: [[File:xpc_capture_auth_listview1.png|740px|border]] 

''Method 2:''
This method is good for both the whole amount and partial captures.

# While viewing the details of a payment on the Payment details page, locate the section for Capture/Void actions: [[File:xpc_capture_auth_detailsview.png|740px|border]] 
# Make sure that the amount shown in the input box is correct. If you need to capture a partial amount, adjust the contents of the input box accordingly - only the specified amount will be captured.
# Click '''Capture'''. The screenshot below demonstrates the capturing of $20 (partial capture, as the originally authorized amount was $28.32): [[File:xpc_capture_auth_detailsview1.png|740px|border]] The amount specified in the input box will be captured: [[File:xpc_capture_auth_detailsview2.png|740px|border]] 

If your payment gateway supports multiple capture transactions, you can capture funds several times, gradually decreasing the authorized amount.

If funds are not available for capture, the '''Capture''' button disappears.

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Payments List

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Payments List to XP Cloud:Payments List: Test page move from API

#REDIRECT [[XP Cloud:Payments List]]

X-Payments Cloud:Auth and Capture (Capturing Funds)

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Auth and Capture (Capturing Funds) to XP Cloud:Auth and Capture (Capturing Funds): Test page move from API

#REDIRECT [[XP Cloud:Auth and Capture (Capturing Funds)]]

XP Cloud:Deleting a Payment

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Deleting a Payment to XP Cloud:Deleting a Payment: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

It is possible to delete any payment in X-Payments Cloud. To delete a payment, use one of the following methods:

''Method 1'':

# On the Payments page, select the payment(s) you wish to delete and click the '''Delete''' button. [[File:xpc_delete_payment_listview.png|740px|border]]
# Confirm the deletion. [[File:xpc_delete_payment_confirm.png|740px|border]]
The selected payment(s) will be removed.

''Method 2'':

# While [[X-Payments_Cloud:Viewing_the_Details_of_a_Payment | viewing the details]] of the payment on the Payment details page, click on the '''Delete this payment''' button. [[File:xpc_delete_payment_detailsview1.png|740px|border]]
# Confirm the deletion. [[File:xpc_delete1_payment_confirm.png|740px|border]]
The selected payment(s) will be removed.

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Viewing the Details of a Payment

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Viewing the Details of a Payment to XP Cloud:Viewing the Details of a Payment: Test page move from API

<noinclude>{{XPC manual TOC}}</noinclude>

To view the details of a specific payment:
# In the list of payments on the Payments page, locate the payment for which you want to view detailed information.
# Click on the payment ID link. [[File:xpc_view_payment_details.png|740px|border]] The page with the payment details - the Payment details page - will be displayed: [[File:xpc_view_payment_details1.png|740px|border]] 

The Payment details page provides general information about the payment:
* '''Amount''' - Payment amount.
* '''Status''' - The current payment status + date and time of the last status update.
* '''Payment time''' - Time at which the payment was made.
* '''Payment configuration''' - Name of the payment configuration for the payment gateway through which the payment was made.
* '''Payment ID''' - Payment ID.
* '''Reference ID''' - Reference ID. For tokenized payments (payments made using a card saved in a customer's profile for use in the store or previously saved as a method of payment on subscription), this field also provides the Reference ID of the original order (the one associated with the initial payment in which the token for the payment card was saved) and a link to the details of the initial payment. [[File:xpc_parent_referenceid.png|500 px|border]] For card setup payments (authorizations made when saving a card in a customer's profile without placing an order) this shows as 'Card setup'. [[File:xpc_card_setup_referenceid.png|500 px|border]] 
* '''Description''' - Payment description.
* '''Customer info''' - Customer name, address, phone, email and IP address.
* '''3-D Secure''' - (If the payment was checked with 3-D Secure) 3-D Secure check result.

In the lower part of the page there is also the Transaction list section that displays all the transactions pertaining to this payment. You may be able to see the following types of transactions:
* ''Auth'': Transaction to place a pending charge or hold on the customer's payment account.
* ''Capture'': Transaction to capture a previously authorized payment amount - fully or partially. Transactions of this type are the result of the merchant using manual capture in a two-step payment flow (See [[X-Payments:User_manual#Auth and capture: Capturing funds|Auth and capture: Capturing funds]]).
* ''Sale'': Transaction to authorize and automatically capture a payment amount (authorization and capture actions are completed simultaneously).
* ''Void'': Transaction to void a previous authorization.
* ''Refund'' - Transaction to return a previously received payment amount from the merchant to the customer - fully or partially.
* ''Info'' - Transaction to obtain information about the current status of handling the payment from the payment gateway.

For example, the image below displays a list of transactions for a payment that was partially refunded. First the payment amount was charged, then a part of the amount was refunded:

: [[File:XP2.0_transaction_list.png|border]]

To see detailed information on a specific transaction:
# In the list of transactions, locate the transaction for which you would like to view detailed information.
# Click on the View details link provided at the far right of the line of this transaction in the transactions list. The transaction details will be displayed: [[File:xpc_view_transaction_details.png|740px|border]]. 

<noinclude>__NOTOC__</noinclude>

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Deleting a Payment

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Deleting a Payment to XP Cloud:Deleting a Payment: Test page move from API

#REDIRECT [[XP Cloud:Deleting a Payment]]

XP Cloud:Voiding an Authorization

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Voiding an Authorization to XP Cloud:Voiding an Authorization: Test page move from API

Depending on the payment gateway you use, you may be able to void authorizations.

'''To void an authorization''':
# In the list of payments on the Payments page, locate the payment for which you want to void an authorization and open its details for viewing.
# On the Payment details page, locate the section for Capture/Void actions: [[File:xpc_capture_auth_detailsview.png|740px|border]] 
# Click '''Void'''. [[File:xpc_void_auth_detailsview.png|740px|border]] The payment will be declined: [[File:xpc_void_auth_detailsview1.png|740px|border]] 

Note that once an authorization has been voided, you will no longer be able to capture the payment - it will be declined.

X-Payments Cloud:Viewing the Details of a Payment

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Viewing the Details of a Payment to XP Cloud:Viewing the Details of a Payment: Test page move from API

#REDIRECT [[XP Cloud:Viewing the Details of a Payment]]

X-Payments Cloud:Voiding an Authorization

2020-03-02T09:17:23Z

Mouse: Mouse moved page X-Payments Cloud:Voiding an Authorization to XP Cloud:Voiding an Authorization: Test page move from API

#REDIRECT [[XP Cloud:Voiding an Authorization]]

X-Payments Cloud:Payment Configurations

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Payment Configurations to XP Cloud:Payment Configurations: Test page move from API

#REDIRECT [[XP Cloud:Payment Configurations]]

XP Cloud:KOUNT Antifraud Screening

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:KOUNT Antifraud Screening to XP Cloud:KOUNT Antifraud Screening: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__

To help you protect your business against fraud, X-Payments Cloud provides integration with a powerful fraud detection and prevention solution by [http://www.kount.com/?utm_source=x-cart&utm_medium=home&utm_campaign=partner Kount]. Kount delivers an all-in-one, SaaS model fraud and risk management platform for merchants operating in card-not-present (CNP) environments and looking to root out fraudsters and increase revenue. For each transaction, Kount’s real-time "decisioning" engine analyzes hundreds of relevant variables and activity across the globe. Kount applies a multitude of proven and patented technologies including Multi-layered Device Fingerprinting®, Proxy Piercer® geolocation tools, statistical scoring, rules-based fraud detection, cross-merchant linking, and Persona behavioral modeling. This enables Kount to expose fraudsters and prevent fraudulent transactions in real time, before losses occur. Kount's proprietary technology has reviewed hundreds of millions of transactions and provides maximum protection for some of the world's best-known brands.
 
To start using Kount for online payment fraud screening in X-Payments Cloud, complete the following steps: 
# Sign up for a Merchant account with Kount at [http://www.kount.com/?utm_source=x-cart&utm_medium=home&utm_campaign=partner http://www.kount.com]. You will be provided with credentials that you will need to configure Kount fraud screening in X-Payments Cloud: your Merchant ID and your Site ID. Take note of this information. 
# In the Kount Agent Web Console (AWC), create your API Key(s). [[File:xpc_kount_apikeys.png|740px|border]] API Keys are required to authenticate to Kount. Note that Kount has separate environments for testing and production, and API Keys must be created and used for each of the environments separately. Kount's instructions for creating API Keys can be found here: [https://support.kount.com/s/article/Create-an-API-Key https://support.kount.com/s/article/Create-an-API-Key]. 
# In the Kount Agent Web Console (AWC), configure customized credit card validation rules for your online store to match the unique needs of your business.
# Log in to the X-Payments Cloud admin panel, go to the General settings page ('''Settings''' -> '''General''') and specify that you are going to use Kount as your Antifraud service:
## Scroll down the page to the Services section.
## In that section, use the '''Antifraud service''' box to select "KOUNT Antifraud screening". [[File:xpc_select_kount.png|740px|border]] 
## Click '''Save''' at the bottom of the page to save your changes.
# Now if you look again at the '''Antifraud service''' setting on the same page, you will see that KOUNT has been selected as your Antifraud service, and the page now provides a link to configure it. [[File:xpc_kount_selected.png|740px|border]] Click on the Configure link to access the page for KOUNT configuration and adjust the KOUNT settings: [[File:Xp_kount_configure_link.png|740px|border]] The page for KOUNT configuration opens: [[File:Xp_kount_settings_page.png|740px|border]] 
# Adjust the settings on the KOUNT configuration page. Be sure to click '''Save''' to save your settings.
#* '''Status''' (Not configured / Enable / Disable): This setting indicates whether KOUNT module is active. For now just leave it as is. After you provide the rest of the required settings (below) and save the changes, KOUNT module will be enabled automatically. You will then be able to use this setting to disable/re-enable KOUNT for your current payment configuration as you require.
#* '''Merchant ID''': Specify your Merchant ID as was provided to you by Kount.
#* '''Site ID''': Specify your Site ID.
#* '''API key''': Enter the API key you have created in the AWC. It will be used for authentication.
#* '''Test/Live mode''': Use this to set the operation mode for Kount fraud screening service - ''Test'' or ''Live''. For access to the Kount AWC in Live mode, use the address https://awc.kount.net, in Test mode - the address https://awc.test.kount.net.
#* '''Description of products''': Common name of the products sold by your store. 
#* '''Mode for RIS update request''': Choose one of the available options (''X: Update data and re-validate transaction against rules'' or ''U: Update transaction data only''). Mode X is recommended if rules are based on the AVS information returned from the payment gateway. Note that additional charges may apply for Mode X.
#* '''Configuration key''': This setting is only available in X-Payments Enterprise. Specify your Configuration key; this one needs to be obtained from Kount.
#* '''If Kount declines''': This setting determines what happens if Kount recommends that a transaction should be declined: should the transaction be declined at once, or should the merchant be given a chance to review the transaction manually and possibly accept it.
# Make sure Kount fraud screening is enabled: [[File:xpc_kount_enabled.png|740px|border]] 

Once Kount antifraud screening has been configured and enabled by following the steps above, any new payment transactions through X-Payments Cloud will be screened by Kount. 
What happens when a buyer submits their credit or debit card info to pay for an order in a store accepting payments via X-Payments Cloud and protected by Kount? 
Technically, the process involves three steps:
At the first step, X-Payments Cloud makes a call to Kount to invoke Kount’s risk check service. In this call, information about the payment transaction (including the IP address, email address, shipping address, card details, billing info, order details, etc.) is submitted to Kount. This happens for each new card prior to contacting the payment gateway. 
Kount’s risk check service checks the information submitted to it using Kount's proprietary algorithms and applies the custom rules configured for the merchant's account. Kount account settings provide substantial flexibility for configuring the rules, which means you can fine-tune the rules to your needs with precision - to the degree where you can specify that a transaction should be declined if initiated by a buyer of a certain name, or be declined if the risk score generated by Kount based on its internal algorithms exceeds a certain value. In practice, Kount will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, Kount's risk check service responds with a risk decision, which includes a risk score and a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined or suspended for manual review by the merchant). X-Payments Cloud will honor the risk decision returned by Kount’s service. If the decision is to process the transaction, X-Payments Cloud will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments Cloud will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen. The setting "If Kount Declines" determines whether a transaction recommended for blocking should be blocked at once or should be suspended for manual review by the merchant. (In the latter case, the merchant will be able to review the transaction details and decide whether they want to decline the transaction or accept the risks associated with processing the card). 
At the second step, X-Payments Cloud contacts the payment gateway for order processing. This, of course, does not happen for transactions that have been blocked.
At the third step, X-Payments Cloud once again contacts Kount to find out the transaction result, including the results of the CVV и AVS checks. Kount's risk check service also stores this information for future use.
 

For transactions suspended for manual review, X-Payments Cloud provides a warning so the merchant can decide whether they wish to accept or decline this transaction. Here's what it looks like on the payment details page in X-Payments Cloud:
::[[File:xpc_kount_authorized_with_warning.png|740px|border]] 
The results of screening by Kount can be viewed lower on the same page:
::[[File:xpc_kount_result.png|740px|border]]

The Kount screening results can as well be viewed from the order page in the store where the transaction originated. For example, in an X-Cart 5 based online store you can do it as follows:
# On the '''Orders''' > '''Orders list''' page, select the order and open its details for viewing: [[File:xpc_view_order_xc.png|740px|border]] 
# Scroll down the page till you see the box with the information on the card that was used to pay for the order and click on the 'View payment information' link. [[File:xpc_view_order_xc_payment_info.png|740px|border]] The Kount result will be shown along with the rest of the information regarding the payment: [[File:xpc_view_order_xc_payment_info1.png|740px|border]] 

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Adding a Payment Configuration

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Adding a Payment Configuration to XP Cloud:Adding a Payment Configuration: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__ 
New payment configurations can be added via the Payment processing page ('''Settings''' -> '''Payment processing'''). 
In X-Payments Cloud trial, you will find that this page already has one pre-added payment configuration: X-Payments Demo Pay.
:[[File:xpc_demo_pay_conf.png| 740px | border]]
The X-Payments Demo Pay payment configuration is purely for testing. You can play with its settings and run some test transactions using the respective payment method in your online store to see how payments via X-Payments Cloud work for your store without having to use your real payment card information. Just be sure to use the demo credit card numbers provided on the payment configuration details page:
:[[File:xpc_demo_pay_conf_numbers.png|740px| border]] 
To be able to accept real payments, you will need to add a new payment configuration enabling X-Payments Cloud to connect to your chosen payment processor. You can find out whether X-Payments Cloud is integrated with your chosen payment processor here: [[X-Payments_Cloud:Supported_payment_gateways | X-Payments Cloud:Supported Payment Gateways]]. Note that as soon as your first payment configuration is added and activated, the X-Payments Demo Pay payment configuration will be disabled automatically. (Should you require to use it again, you can re-enable it by deactivating all your other active payment configurations.)

To add a new payment configuration, select the name of the payment gateway integration you require from the '''New configuration''' drop-down box and click '''Add'''.
:[[File:xpc_add_payment_configuration.png| 740px | border]]

For the sake of example, we will add a payment configuration to accept payments in United States dollar (USD) via Authorize.Net.

We start by selecting the payment gateway integration "Authorize.Net":
:[[File:xpc_add_authorize.png| 740px | border]]

Once we click '''Add''', the 'Add new payment configuration' page for Authorize.Net opens:
:[[File:xpc_add_authorize1.png|740 px|border]]

Here we need to provide the information needed by X-Payments Cloud to access the payment gateway and to specify our payment configuration preferences.

Note that the information we are expected to provide will be different depending on the payment gateway selected. For example, specifically for Authorize.Net, the following details will be needed:
* '''API Login ID''' and '''Transaction key''' - These values will have to be obtained from Authorize.Net.
* '''CIM payment tokenization''' and '''Expanded Credit Capabilities''' - These values will have to be set in accordance with our Authorize.Net account settings.

The rest of the fields on the page will be common to most configurations:
* '''Name''': Name to identify the payment configuration in X-Payments Cloud admin panel and the admin panel of your online store. You can keep the proposed name or choose to change it. For example, if you are going to have more than one payment configurations based on the same payment module - like when you want to use more than one currency - it is best to change the name so you can see which payment configuration you are dealing with without having to open its details. For example, we can change the name to "Authorize.Net - USD" to reflect the name of the currency that is going to be used for payments via this configuration.
* '''Sandbox/Production account''' or '''Test/Live mode''': Whether you are using a development/sandbox environment or a production environment. A production environment is used for real payments (Live mode), whereas a development/sandbox environment is used for testing (Test mode).
* '''Initial transaction''': The mode in which you want the payment transaction to be conducted when someone buys something at your online store: ''Auth'' (authorize the payment amount but not capture the funds yet) or ''Auth and capture'' (authorize and capture the payment amount at once).
* '''Order prefix''': Your trading name or any other prefix that will help you to identify a payment transaction as originating from this specific online store.
* '''Accept currencies''': The currencies in which you will be able to accept payments via the payment method based on this payment configuration. By default, this setting is pre-set to ''All supported (N)'', which means all the currencies supported by the payment gateway - with the number N specifying the number of currencies. To limit the range of currencies that will be accepted, click on the ''All supported (N)'' button, uncheck the ''Select all'' box - this will unselect all the selected currencies - and check the boxes for the currencies that you will accept. For the sake of example, we are creating a configuration that will support only United States dollar; so here we need to disable all the currencies but USD:
:[[File:xpc_add_authorize_currencies.png|740 px|border]]
* '''Credit card types''': The credit card types you are going to accept.
* '''Cancel not captured''': Whether authorizations obtained for payments made in the "Auth" mode should be voided automatically within 30 days of payment if the capture of the funds has not been performed.

After adjusting the payment configuration settings as you require, be sure to click '''Save''' to save your changes.
:[[File:xpc_add_authorize_save.png|740 px|border]]

The payment configuration will be saved and enabled:
:[[File:xpc_add_authorize_success.png|740 px|border]]
(Note the success message at the top of the page and the green status button saying "Enabled".)

Once the payment configuration has been saved and enabled, scroll down the page, and you will find one more thing added to your payment configuration details - the status of your 3-D Secure service (Enabled/Disabled):
:[[File:xpc_payment_configuration_3dsecure_enabled.png|740 px|border]]
This setting determines whether the current payment configuration will be using the CardinalCommerce 3-D Secure service.
If you have configured and enabled CardinalCommerce 3-D Secure service while configuring your X-Payments Cloud General settings, you will find that the status of 3-D Secure service shows as ''Enabled'' for your payment configuration; in this case, nothing else needs to be done: 3-D Secure will work automatically for all your active payment configurations, including this one. If you have not yet configured and enabled CardinalCommerce 3-D Secure, you can do it now or any time later: simply click on the ''CardinalCommerce'' link to get to the page with CardinalCommerce 3-D Secure configuration details, adjust the required fields and update the 3-D Secure status to ''Enabled''. 

Of course, if you do not want the current payment configuration to use the 3-D Secure service by CardinalCommerce, you can disable it by switching the status to ''Disabled''.

After completing work on your payment configuration, you can go back to the Payment processing page ('''Settings''' -> '''Payment processing''') to view the list of your payment configurations.
:[[File:xpc_back2payment_configurations_list.png|740px|border]]

Here you will be able to add more payment configurations if required. For more information on the management of payment configurations, see [[X-Payments_Cloud:Payment_Configurations_List | Payment_Configurations_List]].

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Setting up an Additional/Alternative Method of User Authentication

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Setting up an Additional/Alternative Method of User Authentication to XP Cloud:Setting up an Additional/Alternative Method of User Authentication: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__ 
To be able to log in to X-Payments Cloud with 2-step user authentication, you are required to set up at least one user authentication method - via Google Authenticator or SMS/text messages. However, choosing one method does not mean you may not use the other one. It is possible to configure your X-Payments Cloud so you can use authentication via Google Authenticator or authentication via SMS/text messages based on what is more convenient to you at the moment. To do so, after configuring your primary authentication method (for example, Google Authenticator), you should configure the other authentication method (in our case, authentication with SMS/text messages via Twilio) as an additional method. To access the configuration page for your additional authentication method, use the "configure" link for the respective method on your profile details page ('''Profile''' > '''View details'''). For example, if you already have the method based on using the Google Authenticator app configured and want to configure the method using SMS/text messages, use this link:
:[[File:xpc_sms_auth_link.png|740 px|border]] 
Once both the authentication methods have been set up properly, you will be able to use any of them for the authentication of your user identity. The one-time passwords generated for your preferred and additional user authentication methods will be fully identical, which means you will be able to use a password generated by Google Authenticator when asked for a password from an SMS/text message, and vise versa.

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Setting up an Additional/Alternative Method of User Authentication

2020-03-02T09:14:04Z

#REDIRECT [[XP Cloud:Setting up an Additional/Alternative Method of User Authentication]]

X-Payments Cloud:Adding a Payment Configuration

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Adding a Payment Configuration to XP Cloud:Adding a Payment Configuration: Test page move from API

#REDIRECT [[XP Cloud:Adding a Payment Configuration]]

X-Payments Cloud:KOUNT Antifraud Screening

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:KOUNT Antifraud Screening to XP Cloud:KOUNT Antifraud Screening: Test page move from API

#REDIRECT [[XP Cloud:KOUNT Antifraud Screening]]

X-Payments Cloud:3D-Secure Settings

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:3D-Secure Settings to XP Cloud:3D-Secure Settings: Test page move from API

#REDIRECT [[XP Cloud:3D-Secure Settings]]

XP Cloud:Payment Configurations List

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Payment Configurations List to XP Cloud:Payment Configurations List: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__ 

Payment configurations that you have added in X-Payments Cloud can be viewed and managed on the Payment processing page ('''Settings''' -> '''Payment processing'''). On this page you can see the list of available payment configurations:

:[[File:xpc_payment_configurations_list.png|740px|border]]

For each payment configuration on the list you can see the name of the payment module employed, the number of submitted payments and the current status of the payment configuration (''Enabled'' or ''Disabled''). Payment configurations set to work in test mode are marked with the "test" icon.

Payment configurations that support 3-D Secure payer authentication are marked as such:
* The ones that use 3-D Secure via Cardinal Commerce have "3-D Secure: CardinalCommerce" next to their name. The CardinalCommerce link leads to the page with the settings for CardinalCommerce 3-D Secure configuration.
* The ones that rely on a 3D Secure solution provided by the payment gateway are marked with the words "3D Secure: Built in".
The icon ''Enabled'' or ''Disabled'' displayed next to the name of the 3-D Secure service provider shows the current status of 3-D Secure payer authentication service for the payment configuration.

On the Payment processing page you can:
* Open the details of a specific payment configuration for viewing/editing;
* Enable/disable payment configurations;
* Delete payment configurations;
* Access the CardinalCommerce 3D-Secure configuration settings page via any CardinalCommerce link.

[[Category:X-Payments Cloud User Manual]]

XP Cloud:Deleting a Payment Configuration

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Deleting a Payment Configuration to XP Cloud:Deleting a Payment Configuration: Test page move from API

<noinclude>{{XPC_manual_TOC}}</noinclude>

__NOTOC__ 

To delete a payment configuration, use one of the following methods:

''Method 1:''
# Find the payment configuration you wish to delete in the list of payment configurations on the Payment processing page.
# Click the button dropdown element opposite the payment configuration name.
# Select the required action (''Delete configuration'') from the menu. [[File:xpc_paymentconf_delete1.png|border|740px]] 
# Confirm the deletion. 

''Method 2:''
# While viewing the details of the payment configuration on the Payment configuration details page, click the button dropdown element on the Status line.
# Select the required action (''Delete configuration''). [[File:xpc_paymentconf_delete2.png|border|740px]] 
# Confirm the deletion. 

As a result, the payment configuration will be removed from the list of your payment configurations. After data synchronization between your online store and X-Payments Cloud, your store's list of available payment methods will be updated accordingly.

[[Category:X-Payments Cloud User Manual]]

X-Payments Cloud:Payment Configurations List

2020-03-02T09:14:04Z

Mouse: Mouse moved page X-Payments Cloud:Payment Configurations List to XP Cloud:Payment Configurations List: Test page move from API

#REDIRECT [[XP Cloud:Payment Configurations List]]