MQTT Requirements
- Channel ID - Retrieve your channel ID by following the guide here .
- EPI - Retrieve your EPI by following this guide here .
- Cert Files (ca.crt , client.crt, client.key) - Retrieve Sandbox Cert Files here . Please Note , the ISV Team is responsible for issuing Production Cert Keys upon completion of our certification process. More information about this can be found here.
MQTT Terms to Know
Publish Calls
A publish call is a request made by a client to send a message to a specific topic on an MQTT broker. This allows other clients subscribed to the topic to receive the message. You can utilize our sample code for assistance with implementation of this call here.
Subscribe Calls
A subscribe call is a request made by a client to listen for messages on a specific topic. Whenever a message is published to that topic, the subscribing client receives it. You can utilize our sample code for assistance with implementation of this call here
Channel ID
A Channel ID is a unique identifier used to define a communication channel within a messaging system. It helps categorize messages and direct them to the appropriate destination. You will be issued one unique channel ID for use during all Valor Connect integration operations.
Configuration
- Store the channel ID, certificates, and private key in a secure location as part of the configuration setup to ensure secure communication between your application and the VC server.
- Create a function for securely retrieving file paths for the CA certificate, client certificate, and private key.
- Configure TLS encryption with the CA cert , client cert & private key to ensure secure communication.
Settings Page
- Implement functionality to enter and manage multiple EPIs.
- Provide an option to add a single or multiple EPIs on the settings page as required.
- Enable the ability to assign labels to EPIs within the merchant-facing configuration for better organization and identification.
- Include fields alongside each EPI, such as APP ID and APP Key, to facilitate seamless authentication and integration with our other APIs
Checkout Page
EPI Selection
- Include a dropdown list to select a device / EPI for payment processing.
- Display the device status (online/offline) using our device status API when selecting a device / EPI with.
- Ensure that a transaction request can only be initiated if the selected device is confirmed to be online.
Transaction Handling
- Prevent further transaction requests from being sent until the current transaction is confirmed as complete once the response from the transaction request is picked up from the subscribe call
- Parse the response sent back from the terminal and display/store the information you believe the merchant will find useful such as transaction amount , Approval Code , transaction status etc.