This parameter is a reference for the merchant.

This parameter is the amount of the financial transaction.
The value also contains the decimal part of the transaction. Left (0) padding.

The batch number identifies the batch used by the terminal when the transaction has been processed. It can be used when creating the client receipt.

The value is justified on the left for manual entry (inputType “M” or “I”) and must be completed with spaces (“ ”)

In the case of a transaction with a pinpad or a terminal (inputType “N”), the merchant must use an empty card number (40 spaces characters).

ApplePay and GooglePay use a “device ID” rather than the actual card number.

The card type depends on the card used by the customer.

If the inputType is Internet (type “I”) and the merchant's site allows to specify a credit card type, for example “Visa”, the merchant can specify it with this field in the transaction.

This parameter is the address of the cardholder used in the address verification transaction (AVS).

This parameter is the Verify by Visa authentication token.

This parameter is the postal code used in the Address verification transaction (AVS).
Right (space) padding.

This number identifies the merchant on PayFacto's network. This number is provided by PayFacto.

The currency is the currency used for the financial transaction.

The value sent for this parameter does not defined in what currency the client will be charged, it is only an indicative information.

USD value should only be used when a merchant is setup with a US merchant number.

This number identifies the customer with the merchant.

If a merchant maintains a database of his clients, he can use this field to associate one of his clients with the financial transaction.

This parameter represent the CVV2/CVC2 number on the back on the card.
The value can be 3 (Visa, MasterCard) or 4 (Amex) digits long. It can also be 3 spaces to make it optional.

The message to display when requesting a signature capture.

This parameter is a reference for the merchant to identify the subscription.
The value can be URI encoded to accept special characters.

This parameter is the email address of the cardholder.

End date of the subscription.

The expiration date is the one that is found on client credit card.

The card issuer is responsible for the expiration date validation.

The format is “MMYY” (2 numbers for the month and 2 numbers for the year).

In the case of a transaction with a pinpad or a terminal (inputType “N”), the merchant must use an empty expiration date (4 spaces characters).

When requesting a redirection session, the merchant must provide a URL address to the payment solution.

This URL will be used to redirect the client if the transaction is a failure.

Frequency code for the subscription.

For a recurring amount

For a Total Payable Amount

The ID defines the subscription unique number.
Left (0) padding.

The input type defines the method used by the merchant to execute the transaction.

This value shows which type of transaction the merchant wants to process.

This number associated the merchant's invoice number with the financial transaction.

The invoice number is generated by the merchant and may be unique or not, as per merchant's needs.

Issuer Confirmation Number from online banking (Acxsys), to be displayed on the merchant's confirmation page.

• is not present if payment was not guaranteed.

Merchant must display this confirmation number on their confirmation screen.

Issuer’s name, to be displayed on the Merchant’s confirmation page.

Should be in the language the customer was using for online banking.

The IOP transaction id must be extracted from the IDEBIT_TRACK2.

The IDEBIT_TRACK2 is assigned by Issuer.

Contains PAN, Expiry Date, and Transaction ID. PAN and Transaction ID together must uniquely identify a Transaction. PAN begins with an IIN assigned to the Issuer for use with INTERAC Online Transactions only.

PAN (variable length up to 19 digits) + "=" + 4 digit Expiry Date (YYMM) + Transaction ID (13 alphanumeric chars) + zero padding up to 37 characters 

Last digit of PAN is a mod10 check digit Expiry Date >= current system date.

• Is not present if payment was not guaranteed.

Must match BM35 in the 200 Message (at least enough of it to uniquely identify the Transaction). The PAN must match BM2 in the 200 Message (except that BM2 is blank padded up to 19 characters). The definition of characters 21-24 as an “Expiry Date” is included for backward compatibility only; how it is used is up to the Issuer.

The language code specifies the language in which the merchant wants the PayFacto to send the response to the customer.

In redirection mode, the language code will be used to display the payment page in the appropriate language.

This number identifies the merchant to PayFacto's network. This number is provided by the PayFacto's integration team. Please contact PayFacto to obtain your merchant number.

The merchant terminal number identifies the terminal on PayFacto's network, which is used to process the transaction.

This parameter is the name of the cardholder.
The value can be URI encoded to allow special characters.
The value must be at least 3 characters long.

Number of payments to make or 3 spaces.

The OEM Wallet data is generated by the mobile device authorized wallet.

For ApplePay, you must send the Apple payment token as received by the passkit.
For Google PayTM, you must send the payment token (paymentData.paymentMethodData.tokenizationData.token) as received by Google Pay API

The OEM Wallet type is used to indicate which wallet was used to generate the OEMWalletData

The data returned by the OEM wallet is in various format. The data should be sent as is.

Examples:

The operator id is useful for identifying the cashier's name in the case of a point-of-sale terminal or a user in the case of a call center.

It is usually not used for Internet transactions. It allows the merchant to identify the employee, who generated the transaction on PayFacto's network.

It is always preferable to identify where the transaction originated from within the merchant's system.

This parameter is the original amount of a financial transaction. Normally used in a Pre-Authorization and Completion scenario.
The value also contains the decimal part of the transaction. Left (0) padding.

The value comes from the authorization number obtained in the response of the initial transaction.

This number associated the merchant's invoice number with the initial financial transaction.

The original invoice number is generated by the merchant in the initial request. It will also be returned in the response of the initial transaction.

This parameter is the original terminal invoice number of the financial transaction. Mainly used in the standaloneCompletion transaction
Left (0) padding.

The value comes from the transaction number obtained in the response of the initial transaction.

When the new session creation has been successful, PayFacto returns a session identifier for the entire process of the transaction.

The session identifier is used when requesting the result of the transaction.

Beginning date of the subscription.

This parameter is the status of either client, invoice or subscription.

Client Status

Invoice Status

Subscription Status

When requesting a redirection session, the merchant must provide a URL address to the payment solution.

This URL will be used to redirect the client if the transaction is a success.

Security token linked to the client credit card used for client’s operations or subscriptions.

PayFacto switch (EPOS) unique transaction number.

The value comes from the transaction number obtained in the response of the transaction for which an acknowledgment is wanted.

This parameter is to add some option on a financial transaction.

This parameter is the Mastercard SecureCode data.

This parameter is a special field to pass information to be printed on the terminal receipt using our Semi-Integrated solution. Please contact our integration team before using this field.

<FS>LineNumber(1 CHAR)FieldValue(Variable length-(27 CHAR)<FS>LineNumber (1 CHAR)FieldValue<FS>
Ex:

|1Lable Line 1: Value1|2Label Line 2:Value2|3Label Line 3: value3|4Label Line 4: 1234567890|5Label Line 5: 12345|6Label Line 6: value 6|

This parameter is the transaction identifier returned by Verify by Visa sucessful login.