Ationet Fleet Mobile Payment Fully Integrated

Document Information
File:	ATIONet - Dynamic QR Code Payments
Doc Version:	1.0
Release Date:	26, August 2021
Author:	ATIONet LLC

Change Log
Ver.	Date	Change Summary
1.0	26/August/2021	Initial version.

Contents

• Overview
  • Introduction
  • Entities
  • Sequence diagram Pay at Pump with Above Site Payment Authorization
• Site System configuration
  • STEP 1 Site Mobile Configuration
  • STEP 2 Host Mobile Configuation
  • Values descriptions
• Status Codes and Messages </br>

IMPORTANT: The following document is only valid for the COMMANDER configuration.

</br>

For API documentation please visit here.

</br>

Overview

Introduction

This Implementation Guide is intended to guide petroleum convenience retailers and their associated vendors when implementing mobile payment solutions consistent with ISO 12812. </br>

Note: ISO 12812 is document that will provide requirements, guidance and use cases for all stakeholders in the mobile payments arena.

Entities

This section outlines the logical entities, including location options, for Mobile Payment and identifies possible physical architectures. The term “entity” is used in this document to differentiate logical processing functionality without regard to its physical location in an implementation.

Mobile Payment Application (MPA): This entity is a software application embedded in a Mobile Device or downloaded by a consumer onto a Mobile Device, such as a smart phone or tablet, which enables mobile payments for in-store and forecourt transactions.

Mobile Payment Processing Application (MPPA): This entity is an application provided by the Mobile Payment Processor (MPP) not on the Mobile Device that is responsible for interfacing between the Token Vault or Token/Trusted Service Provider, the MPA, the Site System, the Payment Front End Processor (PFEP), and the Loyalty Front End Processor (LFEP) in order to authorize transactions.

Payment Front End Processor (PFEP): This entity is a host that facilitates the authorization of payment transactions between the MPPA or the Site System and the Issuer networks. The standard does not dictate the processing that is performed by the PFEP for each payment method. This entity is sometimes referred to as the Front End Processor (FEP).

Site System: This entity encompasses the site equipment and components (hardware and software) and may perform the function of local card processing business rules, such as consumer prompting, local velocity checking and receipt formatting and printing. Examples of site systems include Point of Sale (POS), Outside Sales Processor (OSP), Electronic Payment Server (EPS) and Forecourt Device Controller (FDC). </br>

Note: MOBILE PAYMENT API is the common interface through which the MPA sends and receives requests from the MPPA. The description, the methods and how to consume this interface is not part of the scope of this document. You can read more about this here.

Sequence diagram Pay at Pump with Above Site Payment Authorization

1. Mobile Payment Application (MPA) is activated by consumer.
2. MPA determines location and fueling point.
3. MPA sends information to MPPA as an Authorization Request.
4. MPPA optionally sends a Mobile Pump Reserve Request to the Site System to reserve the fueling point.
5. Site System responds to the Mobile Pump Reserve Request.
6. The MPPA sends a Mobile Auth Request to the Site System. If generated, the validation code in the payload.
7. The PFEP (through the site system) sends the Mobile Auth Response to the MPPA.
8. The MPPA sends a Mobile Auth Request to Site Systen.
9. The Site Systen response to MPPA with a Mobile Auth Response.
10. MPPA sends an Authorizacion Response to MPA
11. Mobile Begin Fueling Response is sent from MPPA to Site System.
12. Site System sends a Mobile Loyalty Award Request message to give the MPPA the opportunity to adjust the rewards. This message is always sent after fueling as the final amount is not determined until fueling is complete.
13. The MPPA sends a response to the Site System with the additional rewards information.
14. Site System sends Mobile Finalize Request to MPPA with completion information.
15. MPPA sends Completion Request to PFEP.
16. PFEP send Completion Response message to MPPA.
17. MPPA sends Mobile Finalize Response to Site System. Note: If additional or updated receipt information is included in this response, the Site System may need to regenerate the receipt information.
18. Site System sends receipt information to the MPPA.
19. MPPA sends receipt information to MPA.
20. Site System prints the receipt (if applicable).
21. MPPA sends a receipt response back to the Site System.

Site System configuration

Commander will provide a ConfigClient screen for configuration of Mobile Payments. These details will be provided by MPPA to commander. The screen will provide for configuration options for Site Details, and host configurations and connectivity parameters. The image below is an example. Some Mobile Payments Processing Applications might require more information than others. </br>

You have to request de configuration’s values to ATIONet

STEP 1 Site Mobile Configuration

</br>

Note: The values in the image are for example. You must request the corresponding values from ATIONet.

</br>

STEP 2 Host Mobile Configuation

</br>

Note: The values in the image are for example. You must request the corresponding values from ATIONet.

</br>

Values descriptions

</br>

Site configuration Information	Description
Enable Host	Enable/Disable messaging to this particular host. If the box is not checked messages will not be sent to this particular host.
Adapter	Mobile payment APIs used by commander for communication with MPPA.
Program Name	Program name as defined by MPPA.
Authentication Type	Authentication mode supported by MPPA for that adapter.
Host IP address	IP address will be used by commander for communication with MPPA.
Port	Service Port will be used by commander for communication with MPPA.
SSL Enabled	Commander uses this Boolean for SSL communication or no-SSL communication between commander and MPPA.
Site Terminal ID	This number is supplied by MPPA as terminal identification number.
Merchant ID	Merchant Id given to the store by the MPPA.
Location ID	Location ID is given by the MPPA which identifies a site of a merchant during on boarding process.
Settlement Employee Number	Number used by commander for settlement with MPPA.
Settlement Passcode	Password used during settlement assigned by MPPA.

</br>

Site Initiated Loyalty	Description
Never Allow Site Entered Loyalty	If this option is selected, the site will be restricted to accepting loyalty only from the site or only from the MPPA. If a transaction already contains loyalty (i.e. the consumer has swiped a loyalty card prior to starting the mobile transaction) the MobileReserve / Auth will be rejected. This enforces that mobile loyalty and site entered loyalty cannot co-exist.
Allow Site Entry i.e., Swiped Loyalty Card	Both Mobile loyalty and site card swipe loyalty are allowed and Mobile payments can be tendered at DCR.
Allow Site Entered Loyalty if no Mobile Loyalty	If Mobile Loyalty is not present, loyalty card swipe at DCR will be accepted. If Mobile Loyalty is present and Loyalty Card is swiped at DCR, MobileReserve/Auth will be rejected.

Status Codes and Messages

The first two digits of the response code identify the message pair type. The last 3 digits is the error identifier for the status. A ‘good’ status is always represented as 00000 regardless of the message type.

Message Type	Response Code	Message Code	Overall Result	Description
All	00000	Success	Success	Message was successfully processed.
All	00001	Generic Error	Failure	An unexpected error has occurred while processing the request message.
All	00001	Generic Error	MissingMandatoryData	Mandatory data is missing from the request header.
MobileAuth	02001	Generic Error	Failure	Unexpected error while processing the MobileAuthRequest data.
MobileAuth	02001	Generic Error	MissingMandatoryData	Mandatory data is missing from the MobileAuthRequest
MobileAuth	02002	Invalid info in MobileTxnInfo element	Failure	The header info matches an already processed transaction.
MobileAuth	02002	Invalid info in MobileTxnInfo element	MissingMandatoryData	The header is missing mandatory data to complete Auth processing.
MobileAuth	02003	POS or Fueling Position in use	Failure	The targeted fueling position is already in use. (Unused)
MobileAuth	02004	POS or Fueling Position in use	Failure	The Commander was unable to process the authorization request. Communication with the POS or fueling position has been lost.
MobileAuth	02005	Unknown POS or Fueling Position	Failure	The targeted fueling position is not configured.(Unused)
MobileCancel	04001	Generic Error	Failure	Unexpected error while trying to cancel the transaction. It is likely too late in the transaction to honor.
MobileCancel	04003	04003	Failure	The Commander is beyond the point to honor a cancel request.
MobileCancel	04004	Invalid state - dispenser is fueling	Failure	Cancel occurred while dispensing fuel.
MobileCancel	04005	Invalid Dispenser number	Failure	The targeted fueling position does not match the original authorized fueling position.
MobileCancel	04006	Invalid payment/auth information	Failure	The payment info does not match the original payment info.
MobileCancel	04007	Unknown transaction or authorization	Failure	There is no active transaction to cancel matching the provided header.
MobileCancel	04008	04008	Failure	Unexpectedly failed to cancel
MobilePumpReserve	06001	Generic Error	Failure	Unexpected pump reserve failure
MobilePumpReserve	06001	Generic Error	MissingMandatoryData	Data mandatory to handling the pump reserve request is not present.
MobilePumpReserve	06002	Invalid info in MobileTxnInfo element	Failure	The header information(UMTI) was present in an already processed transaction.
MobilePumpReserve	06002	Invalid info in MobileTxnInfo element	MissingMandatoryData	Data required to reserve a fueling position is missing from the request message.
MobilePumpReserve	06003	Fueling Position in use	Failure	The dispenser is not ready to reserve for a mobile transaction. It is in use or handling configuration updates.
MobilePumpReserve	06004	Fueling Position inaccessible/offline	Failure	The targeted dispenser is configured, but offline.
MobilePumpReserve	06005	Unknown POS or Fueling Position	Failure	The targeted dispenser is not configured.
MobileTransactionData	13001	Generic Error	MissingMandatoryData	The transaction data request is missing data required for processing.
MobileTransactionData	13002	Invalid Transaction Data Header	Failure	This is a duplicate transaction for an already processed transaction, or the transaction does not exist on the system.