Pay by Device allows you your customer to pay a Posted Sales Invoice in-person using a regular Credit or Debit card using an EMV Payment Terminal or Pin-Pad.  This topic documents the following items:

Pay a Posted Sales Invoice (Fortis)

Pay a Posted Sales Invoice (Sensepass)

Review Device Transactions

Retry a Transaction

Print a Customer Receipt

Pay a Posted Sales Invoice (Fortis)

To Pay a Posted Sales Invoice, follow these steps:

  1. Open the relevant Posted Sales Invoice
  2. Navigate to Actions > Pay By Device
  3. This opens the Card Payment form:

A screenshot of a computer??Description automatically generated

  1. Select the Device you wish to use, from the Device Id dropdown.
  2. Select OK

Note if you wish to pay a lesser amount, you can override the Amount textbox.

  1. The Payment Providers Card Payment form will be displayed and confirm the Device, the Amount and indicate the real-time status of the Transaction.
    A screenshot of a computer??Description automatically generated

Pay a Posted Sales Invoice (Sensepass)

To Pay a Posted Sales Invoice, follow these steps:

  1. Open the relevant Posted Sales Invoice
  2. Navigate to Actions > Pay By Device
  3. This opens the Card Payment form:

A screenshot of a computer??Description automatically generated

  1. Select the Sensepass Device you wish to use, from the Device Id dropdown.
  2. Select OK

Note if you wish to pay a lesser amount, you can override the Amount textbox.

  1. The Sensepass Card Payment form will be displayed and confirm the Device, the Amount and indicate the real-time status of the Transaction.
    A screenshot of a computer screen??Description automatically generated


Pay using Fortis and a Credit Card 

Pay using Sensepass and a NFC Tag or QR Code


Review Device Transactions

You can review all transactions that have been conducted via the Payment Device whether they have approved, declined or failed.

Navigate to Device Transactions

A screenshot of a computer??Description automatically generated

Transaction Id

The Transaction number for the Payment

Transaction Date

The Date the Transaction occurred

Device Id

The Device Id where the payment was carried out.

Connector Type

The Payment Provider used

Connector Account

The name of the Connector Account used

Payment Method Code

The Type of Payment Method, e.g. Card

Account Type

e.g. Customer

Account No.

The Number of the Account, e.g. Customer Account.

Document Type

The type of Document the Payment was made against, e.g. an Invoice

Document No.

The relevant Document number, e.g. the Posted Sales Invoice Number.

Document No.

The Ledger Entry Document Number

External Document No.

Reserved

Amount

The Amount of the transaction

Auth Code

The Provider’s Authorization Code for the Transaction

Last 4

Where a credit or debit card was used, the last four digits of the Primary Account Number

Card Type

Where are Card was used, the Type or Brand of Card, e.g. VISA

Ref. Transaction Date

The Provider’s Transaction Reference Date

Ref. Transaction Id

The Provider’s Transaction Reference Id, e.g. 11eef32bccabc8009a87c1e9

Transaction Status

The Status of the Transaction, 
e.g. Failed, Complete

Payment Status

The Provider’s Status of the Transaction

e.g. 

Approved

Declined

None (Where the transaction Failed)

Status Check Code

An internal value. Reserved for support purposes.

Status Check Link

An internal value. Reserved for support purposes.

Reason Code

The Reason code from the Provider.  See the Topic on Testing

Status code

101 =  Approved

301 =  Declined

Posted

A Boolean field to indicate if the Payment has been Posted or not

EMV Fields

The Table includes additional fields that are only populated when the card transaction is and EMV Transaction, e.g. by Inserting or Tapping a card.   These fields may be useful to the Merchant when proving the customer was present and defending a chargeback.

TVR

The TVR Number, e.g. 0800008000

AID

The Application ID – this relates to the Card Brand, e.g. MASTERCARD is a0000000041010

TSI

E800

APPLAB

The Application Label, e.g. MASTERCARD

CVM

The Cardholder Verification Method (Swipe, Insert, Tap etc) , e.g. Pin Verified

PAN

The Primary Account Number (Masked), e.g. ************0011

IAD

The IAD of the transaction e.g. 0210a00000000000000000000000000000ff

ARC

e.g. 00

CURR

The reported Currency, e.g. USD$

MODE

e.g. Issuer

AC

e.g. dcbe109f99657262

AIDNAME

The full name of the Application Identifier, e.g. MasterCard Credit/Debit (Global)        

Transaction Type

The EMV type of Transaction, e.g. Sale, Refund

Account Holder

The Name of the Card or Account Holder, if this is present and returned from the Device/Payment Provider, e.g. LASTNAME/FIRSTNAME


Entry Mode

The entry mode of the Transaction

e.g. C =  Chip

S =  Swipe

M = Manually Entered

Payment Method Type

The code representing the Payment Method, e.g. cc



Retrying a Transaction

MAX Pay Global provides reliable connectivity from Business Central to the Payment Provider’s Payment Device or Terminal (Pin Pad) which will ultimately rely on communications between Microsoft’s Business Central Cloud Servers, across the internet to the Payment Provider’s Gateway, and out again via the Internet and the Merchant’s internal network to the Payment Provider Device.  

A diagram of a computer??Description automatically generated

It is possible for the two to become disconnected, for instance if there is an interruption to the connectivity or for instance if the Store Associate closes the BC session.  Poor communications may lead to a Time-Out which MPG will attempt to recover from in real time leading to a reliable system as possible.  In the rare chance that the Payment Session in Business Central terminates, for instance when the Store Associate closes the Payment Dialog to return to other operations, it may be possible for the Payment to have been approved (or declined) on the Payment Provider’s side.  Normally in day to day use, the Store Associate, customer and Payment Terminal will be co-sited so the status of the transaction can normally be ascertained using messaging on the device. However, MAX Pay Global provides the advanced capability to recover from this situation to minimize the number of duplicate should there be a disconnection in connectivity of if the Store Associate inadvertently closes the session.  To check the status of a transaction and recover from it, follow these simple steps:

  1. Navigate to Device Transactions
  2. Locate the Transaction in question
  3. Select Actions > Re-try
  4. The Provider’s Card Payment Dialog will appear and it will contact the Provider to query the status of the transaction.

A screenshot of a computer??Description automatically generated

  1. If the Payment Status was Approved, it will update the Device Payment record accordingly and Post the payment against the document.

Note – the final check is to check the transaction in the Payment Provider’s Portal.


Printing a Customer Receipt

You can print a receipt to give to your Customer to offer them Proof of Payment, or if the payment has failed, prove that the payment has not gone through.  To access the receipts, follow these steps:

  1. Navigate to Device Transactions
  2. Locate the Customer’s Transaction
  3. From the Actions menu, select Print Receipt

A screenshot of a computer screen??Description automatically generated

  1. Select the Printer, and Report Layout if necessary.
  2. Filter the Transaction Id and add any other Filters as necessary.
  3. You can Send the receipt (Send to..) to a destination, Print or just Preview & Close.


Examples

Swiped Card

A screenshot of a computer screen??Description automatically generated

EMV Example (Dipped or Entered)

A screenshot of a computer program??Description automatically generated



Next topic