Frequently Asked Questions

Authorization amounts cannot be modified as per payment card industry standards. If the transaction has not been submitted for settlement, the authorization can be canceled and then a new authorization obtained for the correct amount. If the transaction has been submitted for Settlement, then a credit must be issued for the difference.

Yes, in most scenarios.

It is best to call the Issuing bank because they ultimately control whether the funds are released. A Cancel Auth in XiPay WebGUI marks the transaction as "Voided" to ensure no Settlement activities occur for the transaction, but does not guarantee the funds are released. If you do not contact the Issuing bank, the funds will be released once the set authorization horizon has passed.

No. You are unable to set limits on the server, but you can access the Test Guidelines for the processor to be able to simulate certain scenarios. We do not have control over this data or the processor's simulators.

The digit of the card number indicates the card type. For example, Visa begins with 4, MasterCard begins with 5 or 2 Amex begins with 3, and Discover begins with 6.

Access the Batches Report. Change Batch Status to [All], change new Page Size option to '50'.

Note that the Error Count field is only available when the Batch Status is set to [Last 10]. This is by design as currently it would greatly impact performance to add this option for the other Batch Statuses.

An authorization that has not been submitted for settlement. You cannot edit the authorization amount. This is a payment card industry best practice. The funds are reserved via the authorization for a given amount. You can then choose to settle for a lesser amount if for example, there was a partial shipment.

You can create a credit amount for a transaction that has already been submitted for settlement or you can cancel.

Cancelling an authorization does not always immediately release the authorized funds, it is up to the issuing bank; the funds will automatically be released once the authorization horizon has passed.

You should not attempt to settle for more than the authorized amount. For example, if you have a partial shipment, a new, separate authorization should be obtained. In some scenarios, the Merchant may have an agreement with the processor in which they would allow the merchant to settle for more than the authorized amount. You will need to verify if your processor supports this type of exception.

Yes. Access menu path: Reports > Audit Logs for a complete report of all actions in the GUI for a given XIID. See Audit Logs topic in the Online Help for more details.

No, you cannot modify a settlement amount in XiPay since settlements are done in SAP.

Refer to the Settlement (Advanced) topic in Online Help for further information. For printing receipts, refer to Generating Receipt.

Yes, the end result is the same. You should use the settlement process that is relevant for your business.

When you run settlement, SAP performs your account postings before attempting to make a call to the external system. If that call fails, it does not go back to reverse the accounting entries that were made, this is why the transactions appear to have settled in SAP even though outbound communication may have failed.

This is typically indicative of a connectivity problem but could be a data problem as well. The two transactions were not transmitted to the XiPay on-demand system even though they were transmitted from SAP.

Check out the processor reports. If you do not have a processor report, you will have to contact the processor directly.

If the processor indicates they did not receive the batch, then contact Paymetric to receive instructions on submitting such batches.

An administrator or authorized user who has access to the PAS server can see the log on the PAS server.

You cannot settle a transaction that is in an error status. It is standard payment card workflow. Such credit card transactions should be resubmitted before attempting to settle again.

That depends on the processor, not Paymetric.

Typically banks provide reports that detail what was submitted to the bank compared to what was deposited.

Unpaid invoices will not be opened automatically. SAP supplies transaction FBRC to manually open items so that you first review and confirm that an item should be opened to prevent accidental reversals.

Currently this is dictated by SAP. The majority of the automation is done in the Order-to-Cash workflow, particularly during the posting of an invoice to accounting. However, automated posting if deposits is not available at this time.

Paymetric rotates the encryption key (not algorithm) annually per PCI Compliance.

The tokens stored in your system will not be affected by a key rotation so will continue to be viable.

Our customers have to take NO action, this is an internal Paymetric key rotation process. This is one of the many benefits of our Tokenization service. http://www.paymetric.com/solutions/XiSecure-on-demand/features

Paymetric has no plans to rotate or change the algorithms as that would affect all customers.

The layout features are saved in cookies within the browser which means the settings are saved across all XIIDs to which you have access. To reset the default settings, clear your browser cookies.

Yes, the Column Order is saved across all XIIDs to which you have access if you log in within 90-days.

It also remembers if you Add/Remove columns and Grouping. See the Navigation topic for more details.

Graphical User Interface

The latest features are currently available in both QA and Production environments in OD3 and depending upon your User permissions. OD3 means you use the following URL for production:

https://prd02.XiPaynet.com/XiPayweb

B2B Payment's data retention is 365 days. Transactions are automatically deleted once they are 366 days old.

To print reports, you can now filter and modify the data layout as desired, then it is recommended that you export to Excel to print.

This feature is currently not supported.

Yes.

Yes with the appropriate Admin role and permission.

For a description of the transaction Status Codes, such as -101, you can view the long text for it in the "Status" column. For example, -101 = Authorization Failed. If the Status column is missing, you can use the Add/Remove Columns feature to add it. Also refer to Transaction and Batch Statuses Defined.

This is currently not available, but is a requirement for a future release.

This is currently not available, but is a requirement for a future release.

InfoItems are not currently supported in the grids/list.

To print reports, you can now filter and modify the data layout as desired, then it is recommended that you export to Excel to print.

Not at this time.

For printing receipts, refer to Generating Receipt.

See SAP and Paymetric Integration Points for more information on the client software components.

Refer to the Announcements and Memorandums topic.

Paymetric Adapter for SAP (PAS)

• From the PAS Configuration GUI check the About button in the top right corner.

• If on a prior version, identify the file version of the XiSecureNetRFC.exe file on your PAS server:

• Navigate to the Program directory on the PAS server (usually Program Files\Paymetric\Paymetric Adapters for SAP) and look for the version Tab in the file properties (right click on the file -> Properties).

XiPay Integration - PCMA

• SAP ERP - Review the PCMA IMG for the Release Number.

• Execute T-Code /n/PMPAY/PIMG and view Release number under the Build Information Section.

• If you would like to Paymetric review, hit F9 and send the file that is created.

XiSecure Integration - XiSecure SAP Integration Kit

• SAP ERP and CRM - Review the XiSecure IMG for the Release Number

• Execute T-Code /n/PMENC/BIMG and view Release number under the Build Information Section.

• If you would like Paymetric review, hit F9 and send the file that is created.

You will be required to upgrade to the latest version of applicable components prior to troubleshooting component-specific problems. Otherwise, batch and transactional data related support requests are not affected.

Technically no, PAS can be updated first and then the SAP transports can be updated and tested.

However, from a testing standpoint, it would be best to test all of the workflows through all upgraded systems.

Depending on the versions of your client side software components, some of the significant enhancements that have been made are:

• Security updates: Additional Authority checks for credits, for Paymetric Reports, and for SAP Call Transactions.

• Numerous code fixes throughout the functionality.

• Support for XiSecure FlexTokens.

• Web Service Retry Logic in PAS (requires configuration of parameters), etc.

Please review the Paymetric Releases section for details of each release. You will find high-level release overview information and detailed release notes. The See Also section has a link to Prior Release information where applicable.

A full round of testing of the authorization, settlement and tokenization workflows from and through SAP ECC/CRM should be completed including the Receivables Management programs and the ability to perform Credits.

Paymetric Support will provide the code base update, integration documentation, and release notes, but cannot provide hands-on assistance in an upgrade. Please discuss with your Paymetric Account Manager if you would like to procure consulting assistance and an estimate can be given.

If your PCMA version is 1.2.x and below, Consulting assistance is highly recommended as several significant changes have occurred.

No matter how many releases behind you are, only the latest FULL release and additional patches need to be implemented, not any releases in between. (E.g., if latest Release of PCMA is 1.6.1, and you are on 1.4.0.1, you only need install 1.6.0 and 1.6.1 transports.)

The SAP transports and PAS upgrade files can be obtained through a support request by your designated internal support contact.

Please send Paymetric the PSF Downloads before and after an upgrade is completed for our records.

PCMA versions prior to 1.6.0 are NOT compatible with SAP ECC 6.0 Ehp 5 or greater. You must upgrade to the latest version of PCMA. Please refer to the Announcements and Notifications topic for a link to the latest supported client-component versions notification and plan your upgrades accordingly. You should plan to upgrade the XiSecure SAP Integration Kit as well if applicable.