Difference between revisions of "XP Cloud:Managing Payments"

From X-Payments Help
Jump to: navigation, search
m
m (Mouse moved page X-Payments Cloud:Managing Payments to XP Cloud:Managing Payments: Test page move from API)
(12 intermediate revisions by one other user not shown)
Line 3: Line 3:
 
Payments made in your online store via X-Payments Cloud can be viewed and managed using the Payments page.
 
Payments made in your online store via X-Payments Cloud can be viewed and managed using the Payments page.
  
[[X-Payments_Cloud:Payments_List | Payments List]]
+
For more information on the specific features and user actions related to payments see the following articles:
[[X-Payments_Cloud:Payment_Statuses | Payment Statuses]]
 
[[X-Payments_Cloud:Searching_for_Payments | Searching for Payments]]
 
  
==Viewing Payment Details==
+
* [[X-Payments_Cloud:Payments_List | Payments List]]<br />
 +
* [[X-Payments_Cloud:Payment_Statuses | Payment Statuses]]<br />
 +
* [[X-Payments_Cloud:Searching_for_Payments | Searching for Payments]]<br />
 +
* [[X-Payments_Cloud:Viewing_the_Details_of_a_Payment | Viewing the Details of a Payment]]<br />
 +
* [[X-Payments_Cloud:Deleting_a_Payment | Deleting a Payment]]<br />
 +
* [[X-Payments_Cloud:Auth_and_Capture_(Capturing_Funds)|Auth and Capture (Capturing Funds)]]<br />
 +
* [[X-Payments_Cloud:Voiding_an_Authorization | Voiding an Authorization]]<br />
 +
* [[X-Payments_Cloud:Issuing_a_Refund | Issuing a Refund]]<br />
 +
* [[X-Payments_Cloud:Managing_High_Risk_Transactions_(Accept/Decline) | Managing High Risk Transactions (Accept/Decline)]]<br />
 +
* [[X-Payments_Cloud:Emulating_Transactions | Emulating Transactions]]<br />
 +
* [[X-Payments_Cloud:Clearing_Cardholder_Data | Clearing Cardholder Data]]<br />
 +
* [[X-Payments_Cloud:Tokenization_and_Re-Use_of_Saved_Credit_Cards | Tokenization and Re-Use of Saved Credit Cards ]]<br />
  
To view the details of a specific payment, locate the payment in the 'Payments' table and click on its Reference ID, or click on the 'Details' link pertaining to the payment in the last table column on the right. The 'Payment details' page opens:
 
 
: [[File:XP2.0_payment_details.png|border]]
 
 
The main section of the 'Payment details' page contains general information about the payment.
 
 
Below there is the 'Transaction list' section that displays all the transactions pertaining to this payment.
 
 
You may 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:
 
: X-Payments 2.0 and later: Click [[File:XP2.0_view_transaction_details.png]]. You will see something like the following:<br />[[File:XP2.0_transaction_details.png|border]].<br />If there is [[X-Payments:General_settings#Cardholder Data|stored cardholder data]] associated with the payment, users who have the [[X-Payments:Managing_users|permission]] to view cardholder data can see it in a separate section on the right-hand side of the screen. If no stored cardholder data is available, the section is displayed like so:<br />[[File:XP2.0_cardholder_data_not_available.png]]<br />
 
: X-Payments 1.0: Click [[File:Xp-26_additional_info.gif]]. You will see something like the following:<br />[[File:Xp-additional_info.gif|378px]]
 
 
==Deleting payments==
 
 
To delete a payment, do one of the following:
 
* '''On the 'Payments' page''':<br />Select the payment(s) you wish to delete and click the '''Delete''' button.
 
* '''On the 'Payment details' page''':<br />X-Payments 2.0 and later: Click the [[File:XP2.0_delete_this_payment.png]] link. Confirm the deletion.<br />X-Payments 1.0: Click the [[File:Xp-28_delete_payment_link.gif]] link. Confirm the deletion.
 
 
==Clearing cardholder data==
 
 
Stored cardholder data for some or all payments can be removed via the 'Payments' page:
 
To remove cardholder data for specific payments, select the check boxes next to them and click the '''Clear cardholder data''' button.
 
To remove all stored cardholder data, click the '''Clear all cardholder data''' button.
 
 
It is also possible to remove stored cardholder data for a specific payment via the 'Payment details' page of that payment: click the '''Clear cardholder data''' link in the section that displays stored cardholder data.
 
 
==Auth and capture: Capturing funds==
 
{{X-Payments:Auth_and_Capture}}
 
 
==Voiding authorizations==
 
Depending on the payment gateway you use, you may be able to void authorizations.
 
 
'''To void an authorization''':
 
# On the 'Payments' page, locate the payment for which you want to void an authorization and open its details for viewing. The 'Payment details' page opens.
 
# On the 'Payment details' page, locate the section for Capture/Void actions:<br />X-Payments 2.0 and later:<br />[[File:XP2.0_capture_void.png]]
 
# Click '''Void'''.<br />X-Payments 1.0:<br />[[File:Auth_capture2.gif|border]]
 
 
Note that once an authorization has been voided, you will no longer be able to capture the payment - it will be declined.
 
 
==Issuing refunds==
 
Depending on the payment gateway you use, you may be able to refund payments received from your customers - fully or partially.
 
 
'''To issue a refund''':
 
# On the 'Payments' page, locate the payment for which you want to make a refund and open its details for viewing. The 'Payment details' page opens.
 
# On the 'Payment details' page, locate the section for Refund actions:<br />X-Payments 2.0 and later:<br />[[File:XP2.0_refund.png]]
 
# Click '''Refund'''.
 
 
'''ATTN users of Authorize.Net CIM''':
 
# Users of X-Payments versions prior to X-Payments 2.2.0 may find that they are unable to issue refunds for some Authorize.Net CIM transactions. This is typically the case for transactions that have not yet been submitted for settlement. It is normal because for Authorize.Net CIM transactions funding takes place after settlement; before settlement no money can be returned to the buyer since no money has yet been captured. After settlement, the issue resolves on its own. In X-Payments 2.2.0 we implemented "smart refunds": if a refund transaction cannot be completed successfully, we automatically attempt to void the initial transaction.
 
# To ensure the correct processing of Authorize.Net CIM refunds, you need to make sure that the option selected in the "Expanded Credit Capabilities" setting in the payment configuration for Authorize.Net CIM in X-Payments matches the respective setting in your merchant account. More information on Expanded Credit Capabilities (ECC) is available here: https://www.authorize.net/support/CP/helpfiles/Miscellaneous/Pop-up_Terms/Expanded_Credit_Capabilities.htm
 
 
==Accept/Decline: Managing High Risk Transactions==
 
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: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:
 
:[[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''.
 
 
==Emulating transactions==
 
{{X-Payments:Emulating_transactions}}
 
 
==Tokenization and Re-Use of Saved Credit Cards (X-Payments 2.x and later)==
 
{{X-Payments:Tokenization_and_Re-Use_of_Saved_Credit_Cards_(X-Payments_2.x_and_later)}}
 
  
 
<noinclude>__NOTOC__</noinclude>
 
<noinclude>__NOTOC__</noinclude>
  
 
[[Category:X-Payments Cloud User Manual]]
 
[[Category:X-Payments Cloud User Manual]]

Revision as of 13:17, 2 March 2020

X-Payments Cloud User Manual
  1. X-Payments Cloud: General information
  2. Get Started with X-Payments Cloud
  3. Two-factor User Authentication
  4. General Settings
  5. Payment Configurations
  6. Services
  7. Users
  8. User Interface
  9. Payments
  10. Supported Payment Gateways
  11. What's New in X-Payments Cloud

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: