1 Papagena Format

The following section describes the setup, usage of Credit Card Transfer for PAPAGENA Handling.

Prerequisites, Supported Systems, and Compatibilty

Prerequisites, Supported Systems, and Compatibility

This section describes the minimum requirements for PAPAGENA Credit Card handling and supported peripherals.

Prerequisites
  • Credit Card Transfer.exe

  • Tools.exe

  • SPMS Parameters

  • SPMS DLL

    • MTIPADLIB.dll

    • IPADLIB.dll

Compatibility

SPMS version 20.1 or later. For customer operating on version below 20.1, database upgrade to the recommended or latest version is required.

SPMS Parameters

This section describes the Parameters available to the Credit Card Transfer module and they are accessible from Administration module, System Setup, Parameter function.

Table 1-1 PAR _GROUP General

PAR Name PAR Value Description

Enable Signature Capture for Credit Card

0 or 1

Prevent the credit card registration without a signature when enabled.

0 - Disable Signature Capture for Credit Card

1 - Enable Signature Capture for Credit Card

Disable C/Card and Posting when auth is decline

0 or 1

0 - No credit card deactivation and no posting disable

1 - Deactivate the credit card then the posting if there is no other credit card is active.

2 - Deactivate the credit card. Posting remains enabled.

Top Up Percentage

<value>

Specify top up percentage to be calculated with the total authorized amount.

For example, Total Auth Amount=1000 * 15% = 1150 as New Auth Amount.

Test Auth Amount

<value>

Specify PAPAGENA test authorization amount for both online and offline mode.

Card Track Data not Stored

<BLANK>

List of card types that should not store track data in the database. Format (‘Card Type 1’,’Card Type 2’).

For example, ('DS','DI','JC','DC').

Allow Manual Card Entry for Papagena

0 or 1

0 - Do not allow manual entry when card swipe fail

1 – Allow Manual Entry when card swipe fails.

Table 1-2 PAR_GROUP Interfaces

PAR Name PAR Value Description

Batch CCard Processing Format

PAPAGENA

Specify the message format to be generated by Credit Card Transfer program.

Merchant ID

<character>

Defines the Merchant ID for the authorization file.

CC Auth/Settlement Folder

Folder path

Repository location for authorization/settlement files generated by OHC Credit Card Interface

Note: To avoid adverse impact on your system, please abstain from using the following folder path:

  • System Directory

  • “\Users\Public\Documents\Oracle Hospitality Cruise”

System Configuration

This section describes the setup of various system codes required by PAPAGENA handling and these codes are setup in Administration module, Financial Setup, Department setup.

Department Setup

For charging and posting, a debit and credit department code of each credit card type accepted by the ship must be configured in SPMS.

Credit/Debit Card Department Code Setup
  1. Login to Administration module and select Financial Setup, Department setup from the drop-down list.

  2. Click New to create a Sub-Department cod

  3. Under the Main Department section, enter the credit/debit card information such as Payment Type, Department Code, and Description.

  4. In the Payment Type Details section,

    1. Enter the first two digits of the first set of the credit card number in Credit Card digit.

    2. Enter the Credit Card ID. For example, MC - MasterCard, VI - Visa, and others.

    3. Select the corresponding Credit Card Internal ID from the drop-down box.

    4. Enter the Credit Card Merchant Number provided by the Service Provider.

    5. Set the Minimum Authorized Value to 0.

    6. Select the Commission department from the drop-down list and update the commission rate in percentage.

    7. Check the Debit Card No Commission charge if the commission is not applicable to debit card.

  5. In the Department Security access, select the appropriate security level from the drop-down box.

  6. Select the Payment Type in Payment Department Type, either Both Credit and Debit card, Credit card or Debit card.

  7. Click OK to save.

Receipt Setup

A receipt can be generated upon payment and this requires a report template to be set up. A Standard Credit Card receipt template is available in Administration module, System Setup, Report setup, _Receipts group. Please contact Oracle Hospitality Cruise Support if you would like to configure a customized receipt format.

Registration of Credit Card

The SPMS program does not allow credit card registration without a signature if the parameter ‘Enable Signature Capture for Credit Card’ is Enable, and a signature device is configured in hardware option setup.

Registering Credit Card in Management Module
  1. Login to the Management module and select Guest from the Cashier Menu.

  2. Select a checked-in guest and click Get Credit Card button.

  3. The system prompts for a card to be swipe.

  4. After you swiped the credit card, the credit card details, validity and status of the card populates onto the Guest Handling, Credit Card Entry screen. If the card is valid, the card status is shown as ‘Credit Card Accepted’.

    Figure 1-1 Credit Card Entry Screen


    This figure shows the Credit Card Entry Screen
  5. Click OK to proceed with payment card registration or click Cancel to terminate the payment card registration process.

  6. When you click OK, the system prompts a signature screen for card holder to sign and activates when the parameter ‘Enable Signature Capture for Credit Card’ is enabled and Signotec LCD Signature Pad Omega is installed.

  7. Allow the cardholder to place the signature on the Signotec Signature pad and press the green check mark to complete the credit card registration. To capture a new signature, press the Refresh icon to clear the screen.

  8. After the registration is successful, this set off a confirmation prompt. Click OK to confirm. If the ‘X’ is clicked, this cancel the token request.

    Figure 1-2 Credit Card Screen — Credit Card Registration is Complete


    This figure shows the Credit Card Screen — Credit Card registration is Complete

    Figure 1-3 Signature Screen — User Cancel Signature Action


    This figure shows the Signature Screen — User Cancel Signature Action
  9. The credit card information and signature captured are stored in Guest Handling Credit Card tab.

This figure shows the Guest Handling, Credit Card Tab

Registering Credit Card in Advance Quick Check-In (AQCI)

  1. Start the AQCI program and select a checked-in passenger.

  2. Click the Get Credit Card button at the ribbon bar. Both the devices prompt ‘Please Swipe card’. At the Request Token prompt, swipe the credit card through a card reader device.

  3. The swiped credit card details populate under Credit Card Details field. Click Save at the ribbon bar to save the information and this activates the signature screen on Signotec Signature pad if the device is installed.

    Figure 1-4 Advance QCI Credit Card Section


    This figure shows the Advance QCI Credit Card Section
  4. Click Save to proceed with the registration process. The signature screen prompts when parameter ‘Enable Signature Capture for Credit Card’ is enable and Signotec Signature Pad is installed

  5. The registered credit card details are stored in Guest Handling, Credit Card tab.

Credit Card Transfer Interface

The Credit Card Interface has several functions enabled for PAPAGENA handling through the Credit Card Batch Authorization and they are listed below.

Table 1-3 Credit Card Transfer Interface Functions

Authorization Settlement
  • Test File

  • New Authorization File

  • Read Authorization File

  • Manual Authorization File

  • New Settlement File

  • Read Settlement File

Creating Test Authorization File
  1. Start the Credit Card Transfer Interface and selectthe Authorization menu.

  2. Select the Test File option from the drop-down menu.

  3. All payment card requiring authorization are listed in the Test Authorization screen, with the exception of credit card registered with a token.

    Figure 1-5 Credit Card Transfer — Test Authorization Screen


    This figure shows the Credit Card Transfer — Test Authorization Screen
  4. Click the Process to generate the Test Authorization. The amount shown in the Test Authorization is the value set within parameter ‘Test Auth Amount’.

Creating Initial Authorization File
  1. Repeat step 1 of Creating Test Authorization File and then select New Authorization File from the drop-down menu.

  2. All payment cards requiring an incremental authorization are listed in the PAPAGENA Credit Card Authorization Write screen.

    Figure 1-6 Credit Card Transfer — New Authorization Screen


    This figure shows the Credit Card Transfer — New Authorization Screen
  3. The initial authorization can only be generated when the Test Authorization is APPROVED. Below are the validation prompt during the Test Authorization when generating an initial authorization for:

    1. Credit Card registered without Test Authorization or No Test Authorization - The system prompts ‘There is Test Authorization not created yet’.

    2. Credit Card registered with Test Authorization has status Outstanding or Declined - The system prompts ‘‘There is Test Authorization without response or declined response’

  4. Click the Process button to generate the Initial Authorization file. After the incremental authorization file is created, the location of the saved file is displayed on the screen. A sample of the incremental file is illustrated in Figure 1‑10 - Sample Authorization File

    Figure 1-7 Sample Authorization File


    This figure shows the Sample Authorization File
  5. The authorization status of the card is shown as Outstanding in Management module, Guest Handling, Credit Card tab, View Authorization function.

Reading Authorization File

After the authorization request is processed by the Merchant/Service Provider, a response file with authorization codes is returned. These authorization codes are updated in the guest account using the Read Authorization function.
  1. Repeat step 1 of Creating Test Authorization File and select Read Authorization File from the drop-down menu.

  2. On PAPAGENA Credit Card Authorization Read screen, select Open to locate the response file returned by the merchant.

  3. Click the Process button to process the information on file. A progress status is shown on the screen.

    Figure 1-8 Credit Card Transfer — PAPAGENA Credit Card Authorization Read


    This figure shows the Credit Card Transfer — PAPAGENA Credit Card Authorization Read
  4. At the end of the process, the system updates the payment card status to Authorized. This can be verified by logging into Management module, Guest Handling, Credit Card tab, View Authorization function.

Figure 1-9 Management - Authorization Screen


This figure shows the Management Authorization Screen.

The above process also updates the CRD_TOKEN field followed by CCT_TOKEN field in the database, if the settlement record is created before running the Read Authorization.

Creating Incremental File

When an account balance exceeds the initial authorization amount, an additional authorization value must be obtained to allow postings to flow through the account.

The process to obtain additional authorization is the same as the steps in Creating Initial Authorization File and Reading Authorization File.

Obtaining Manual Authorization

A manual authorization is obtain able on ad hoc basis and this is performed within the guest account.
  1. In Management module, Guest Handling function, select the guest account.

  2. Navigate to the Credit Card tab and click View Authorization.

  3. In the Authorization screen, select Add Authorization.

  4. Enter the value including the initial authorized value in the Credit Card Autorization screen when prompt, and click OK to save.

    Figure 1-10 Management — Add Authorization Screen


    This figure shows the Management — Add Authorization Screen
  5. An additional authorization is added to the Authorization grid with its status shown as Outstanding. Select the line item from the grid and enter the code and value obtained, then click Authorized. This process overwrites the existing value and changes the authorization status to Forced, and writes the authorization code into the Settlement file as last authorization code.

Figure 1-11 Management — Manual Authorization


This figure shows the Management — Manual Authorization

Creating Settlement File

At the end of an invoice settlement, the system writes the settlement into the Settlement file, to be processed in batch.
  1. At the Credit Card Transfer Interface, select Settlement menu, then New Settlement File from the drop-down menu.

  2. The settlement file can only be generated when the Test Authorization is APPROVED. Below is the validation prompt during the Test Authorization when generating an initial authorization for:

    1. Credit Card registered without Test Authorization or No Test Authorization - the system prompts ‘There is Test Authorization not created yet’.

    2. Credit Card registered with Test Authorization has status as Outstanding or Declined - the system prompts ‘There is Test Authorization without response or declined response.

      If the Settlement has Test Authorization as Outstanding or Declined, this settlement only shows in the Settlement Write screen and it does not write into the Settlement File

      If the Settlement does not an authorization and CCT_TOKEN the settlement is then written into the Settlement File with CC|ORDER

  3. Click the Processbutton to generate the Settlement File. After the Settlement file is created, the location of the saved file is displayed on the screen.

Figure 1-12 Credit Card Transfer — Settlement Write Screen


This figure shows the Credit Card Transfer — Settlement Write Screen

Reading Settlement File

A response file is sent back by the merchant or service provider after the settlement is processed at their end. You are required to upload the file and update the Settlement transactions status.
  1. From the Settlement drop-down menu, select Read Settlement File.

  2. On the PAPAGENA Credit Card Settlement Read screen, click the Open File button to locate the Settlement Response file.

  3. The status of the process is displayed on the Settlement Read screen. Click the Process button to read and update the Settlement record.

Figure 1-13 Credit Card Transfer — Settlement Read Screen (Ready to Process)


This figure shows the Credit Card Transfer — Settlement Read Screen (Ready to Process)

Troubleshooting

This section describes the troubleshooting steps in resolving some known issues encountered in PAPAGENA Handling across various modules.

Tools

Table 1-4 Tool Known Issue and Solution

Known Issue Solution

Error — ‘Key unable to upload’

Register PGPBBox7.dll with regsvr32.exe again.

Error — ‘License Key has not been set’

Register PGPBBox7.dll with regsvr32.exe again.

Credit Card Transfer Interface

Table 1-5 Credit Card Transfer Interface Known Issue and Solution

Known Issue Solution
Credit Card Transfer doesn’t reflect correct desired credit card format Check the credit card format setup in Administration Module, System Setup, Database Parameter, ‘Interfaces’, ’Batch CCard Processing Format’.

PAPAGENA Mapping Fields

This section describes the mapping fields used in PAPAGENA Credit Card format.

File name format

The file naming format for PAPAGENA is explained in below table. For example: GuestTransfer071020161138.pci

Table 1-6 PAPAGENA File Format

Name Description

Guest

The first word of the file name represents the Account Type base on the filter used to generate the authorization file.

Guest - GuestTransfer#######.pci

Crew - CrewTransfer#######.pci

Group - GroupTransfer#######.pci

Staff - StaffTransfer#######.pci

All filter - <Blank>Transfer#######.pci

Transfer

The second word of the file name represents the type of transfer.

TestTransfer = test authorization file

Transfer = Authorization transaction file

Settle = Settlement transaction file

071020161138

The date/time format of the authorization file

DDMMYYYYHHMM

pci or pcr

The file format extension of the authorization file

pci = request file

pcr = response file

Request File Format

The following tables describes the field definitions for a Request File for Authorization and Settlement.

Table 1-7 Request File Format

Field Type Size Definition

Header

Head

Varchar

4

Fixed value: “HEAD”

data-source

Varchar

30

File sender name, example “MV SHIP”

Date

Int

12

Format: YYMMDDHHMMSS, 111019130712

file-number

Int

12

Counter for the file, example 42

Version

Varchar

4

The version string of our batch file, example 1.0

Batch Record

MerchantID

Varchar

20

Merchant ID. For example HOTEL

Paytype

Varchar

10

“CC” - for VI, MC

“EDD” - for EC

“TO” - for if token with value

Trxtype

Varchar

12

|tstauth|incauth|capture|refund

tstauth: Test authorization, it is a mandatory authorization prior to generating an initial authorization.

incauth: Incremental authorization increases amount of an existing authorization. Input has to be the total amount (initial+additional amount).

capture: Book a pre-authorization. Capture amount has to be less than or equal to the authorized amount.

refund: Refund an amount only valid for an existing order.

TransID

Varchar

50

Unique transaction identification number in ASCII. Does not support special characters.

TransID reference

Varchar

50

Reference to the original unique transaction where necessary. For example, capture, refund, incauth for an already existing transaction.

Amount

Int

9

Always in the smallest currency unit (in cent for Euro and so on, example 100 for 1 Euro), empty if Trxtype=register

Currency

Varchar

3

Currency code according to ISO 4217 for this transaction, for example, EUR,USD, or follow the Ship’s currency.

Description

Varchar

27

Note to Payee in text for Employment Development Department (EDD) Debit Card or other Payment Method.

AppCodeTel

Int

6

Special authorization code obtained manually through telephone for an authorization from an acquirer.

Customer

Varchar

27

Customer name

CD_customerid

Varchar

16

Customer ID in Customer Relationship Management System.

CD_customertype

Varchar

12

Type of customer, for example crew, passenger, staff, and others.

CD_orderid

Varchar

16

Unique order-id

CD_paxid

Varchar

16

Customer unique id

CD_cruiseid

Varchar

10

Travel number

CD_accountid

Varchar

12

On-board account number

CD_roomid

Varchar

6

Cabin number

CD_invoiceid

Varchar

12

Account number

Reference

Varchar

30

Additional reference.

Token

Varchar

30-40

UUID, ex. ed4bdf30-4ac4-102f-991a-000bcd838e00. Reference for a payment account, either from pre-registration (manifest) or earlier batch reply. Token usage is mandatory.

CC_brand Varchar

Varchar

10

Credit card brand MasterCard, VISA, AMEX, DC, JCB.

CC_cardowner

Varchar

27

Card owner.

EDD_accountowner

Varchar

27

Bank account owner.

Track1enc

Varchar

256

For future use.

Track2enc

Varchar

256

For future use.

Track3enc

Varchar

256

For future use.

KSN

Varchar

32

For future use.

TransID reference

Varchar

50

Reference to the original unique transaction where necessary. For example, capture, refund, incauth for an already existing transaction.

Amount

Int

9

Always in the smallest currency unit (in cent for Euro and so on, example 100 for 1 Euro), empty if Trxtype=register

Currency

Varchar

3

Currency code according to ISO 4217 for this transaction, for example, EUR,USD, or follow the Ship’s currency.

Description

Varchar

27

Note to Payee in text for Employment Development Department (EDD) Debit Card or other Payment Method.

AppCodeTel

Int

6

Special authorization code obtained manually through telephone for an authorization from an acquirer.

Customer

Varchar

27

Customer name

CD_customerid

Varchar

16

Customer ID in Customer Relationship Management System.

CD_customertype

Varchar

12

Type of customer, for example crew, passenger, staff, and others.

CD_orderid

Varchar

16

Unique order-id

CD_paxid

Varchar

16

Customer unique id

CD_cruiseid

Varchar

10

Travel number

CD_accountid

Varchar

12

On-board account number

CD_roomid

Varchar

6

Cabin number

CD_invoiceid

Varchar

12

Account number

Reference

Varchar

30

Additional reference.

Token

Varchar

30-40

UUID, ex. ed4bdf30-4ac4-102f-991a-000bcd838e00. Reference for a payment account, either from pre-registration (manifest) or earlier batch reply. Token usage is mandatory.

CC_brand Varchar

Varchar

10

Credit card brand MasterCard, VISA, AMEX, DC, JCB.

CC_cardowner

Varchar

27

Card owner.

EDD_accountowner

Varchar

27

Bank account owner.

Track1enc

Varchar

256

For future use.

Track2enc

Varchar

256

For future use.

Track3enc

Varchar

256

For future use.

KSN

Varchar

32

For future use.

Response File Format

The following table describes the field definition for a Response File for Authorization and Settlement.

Table 1-8 Response Field Format

Field Type Size Definition

Head

Varchar

4

Fixed value: “HEAD”

data-source

Varchar

30

File sender name, example “MV SHIP”

Date

Int

12

Format: YYMMDDHHMMSS, 111019130712

file-number

Int

12

Counter for the file, for example 42

Version

Varchar

4

The version string of our batch file, example 1.0

Response Record

TransID

Varchar

50

unique transaction id

Token

Varchar

40

token, UUID for this payment account. Only if the payment account (credit card or EDD) is valid.

Return-code

Varchar

10

00000000 (8 zeros for OK)

NNNNNN (for Error. For example. 23055310)

Status

Varchar

10

The textual representation of return code, “OK“, “Error“

Description

Varchar

255

Description for Status

Reference

Varchar

30

Additional reference (same as input parameter)

CD_customerid

Varchar

16

Customer number from CRM

Approvalcode

Int

6

Approval-code for this transaction

EPAref

Int

9

EPA-Reference for this transaction, only used for Accounting

auth_time

Varchar

20

Server time stamp for the single transaction,

format YYYY-MM-DDTHH:MM:SS as UTC Time

Footer

Foot

Varchar

4

Fixed value: “FOOT“

Counter

Int

9

Total number of records