Credit card transactions

• Payment processor (field PAYPRC)

You can select Sage Exchange or Sage Pay. The Processor type cannot be changed if any credit cards have been assigned to the Processing code.

• Original doc (field VCRNUMORI)

Enter the original document number.

• Customer (field BPCNUM)

Enter a customer code or leave the field empty to make a query on all customers that use the Payment gateway to process credit card transactions.

• Response (field RESP)

Select this check box to view all logged calls made from the payment gateway.

 At least one of the following two boxes must be selected.

• Start date (field TXNDATDEB)

Enter the date range in which the transaction was created. The date range is used to filter the documents with dates that are included within the range.

• End date (field TXNDATFIN)

• VAN reference (field VANREF)

Enter the VAN reference number supplied by the payment processor.

• Request (field REQ)

Select this check box to view all logged calls made from the payment gateway.

 At least one of the two boxes must be selected.

• Payment processor (field PAYPRC)

You can select Sage Exchange or Sage Pay. The Processor type cannot be changed if any credit cards have been assigned to the Processing code.

• Original document no. (field REF2)

This field displays the transaction's original document number.

• Entry (field REF1)

This field displays the current document number the transactions was processed against.

• Customer (field BPCNUM)

This field is used to enter the code used to identify the customer. It can be entered directly or selected from the Customer table.
 This customer list is not exhaustive, any customer not present in this list can still order the product.

• Name (field ACCNAM)

This field displays the customer's name from the transaction.

• Transaction date (field TXNDAT)

This field displays the transaction date used to process the transaction.

• Transaction code (field TXNTYP)

WIP type.

• Transaction type (field TXNTYPDES)

This field displays the transaction type. The choices are Authorization, Entry, Cancellation, Credit, Vault creation, and Batch settlement.

• Request code (field REQRSP)

This field displays whether the transaction is a Request or Response.

• Response code (field RESP)

This field displays the response code associated to the Response column.

• Response (field RESPDES)

This field displays the response message from Sage Exchange when the Response check box is selected. It provides the information whether the transaction was approved, declined, unable to process, and others.

• Amount (field AMT)

This field displays the total amount, excluding tax, for the transaction.

• Tax amount (field TAXAMT)

This field displays the tax amount for the transaction.

• Payment code (field CRDTYP)

This field displays the payment type code used during the transaction.

• Payment type (field CRDTYPDES)

This field displays the payment type used during the transaction.

• Payment description (field PAYDES)

For Sage Pay, this field displays the last four digits of the credit card.

For Sage Exchange, this field displays the first six digits and the last four.

• Expiration date (field EXPDAT)

This field displays the expiration date of the payment card.

• Creation date (field CREDAT)

This field displays the date the transaction log file was created in the system.

• Address (field ADDLIG)

This table lists the various address lines. The formats of the title and of the entry are defined in the country table.

• City (field CTY)

The city automatically suggested is the one associated with the postal code previously indicated. It is also possible to manually enter the name of a town/city:
- If the town/city is already defined, the associated postal code is automatically displayed,
- If it does not exist and the postal code control has been set up in the Country record, a warning message is displayed but the continuation of the entry is authorized (in order for this control to be applied, the CTY - Nonexistent city alert parameter - SUP chapter, INT group - must also be set 'Yes'),
- If it does not exist and the postal code is set up as mandatory for the country, a blocking message is displayed in case the fields Postal code or City/Town are entered or in case of modification of information in the address window of the BP. However, this control is not carried out in document creation.

Notes.

• Its format is defined in the Country record setup.
• Depending on this setup, the entered town/city can automatically be converted into uppercase after it has been entered.
• In order to make selections easier without taking into account the format (accented characters/uppercase letters/lowercase letters), the selection window available on this field proposes a column dedicated to the search, where the names of the towns/cities are displayed in uppercase.

• Region (field SAT)

This field contains the geographical SDL TEST subdivision corresponding to definition of the postal address. For example, a 'department' for France, and a state for the United-States.

The description of the geographic subdivision, as well as the control on the information entry, are defined in theCountries setup.

This field is automatically loaded after the postal code and town/city have been entered, based on the Postal codes setup.
If the field is controlled, the control is carried out according to the Geographical subdivision table.

• Postal code (field POSCOD)

The postal code, which entry format is defined in the Country table, is used to define the town/city, state/region and the geographical subdivision, if defined for the country.
If you modify the postal code, the city/town and state/region corresponding to this new code are automatically displayed. The principle is the same for the geographical subdivision if it is present for the country.
You can also directly enter a town/city name or state/province. If the city/town, state/region are defined, the associated postal codes are displayed automatically.
The control of this information and its mandatory nature depend on the setup carried out in the country management. For the control to be applied, the POSCOD - Warning nonexistent postal code parameter (SUP chapter, INT group) must also be set to 'Yes'.

Particular cases:

- for ANDORRA, indicate 99130,
- for MONACO, indicate 99138,
- for the other foreign countries, indicate the national identifier of the country or 99999 if not known.

When the postal code is defined as mandatory for the country, it must be entered if the Postal Code or City/town fields are entered, or if information is modified in the BP address window. However, this control is not applied in document creation.

• Country (field CRY)

This code is used to identify amongst other things, the Country of a BP.
This is important information, associated with a number of characteristics useful for performing controls on other linked information, in particular:

• the telephone number format,
• the format of the number used to identify a company or activity (SIRET, SIC) and whether the entry is mandatory,
• the postal code format of the town and also the code of the geographic subdivision, and whether their entry is mandatory,
• whether the VAT number of this community is mandatory,
• the Bank ID code format.

• Email address (field EMAIL)

This field displays the contact e-mail address of the customer from the transaction.

• Authorization code (field RSPCOD)

This field displays the response code specific to the transaction.

• VAN reference (field VANREF)

Enter the VAN reference number supplied by the payment processor.

• Response message (field RSPMSG)

This field displays the message given by the server. It displays a detailed description based on the response code.

• Transaction ID (field TXNID)

This field displays the transaction ID.

• Transaction (field SPTXNID)

• User (field CREUSR)

This field displays the user who created (entered) the record.