The
release notes provided in V1 of this document serve as an initial preview of
the changes expected in the upcoming production release of the PocketPos
application
*** Summary ***
The PocketPos
release notes will contain information related to the new PocketPos application
release. The release notes will include the impact of software release to the
intended target audience.
*The
release notes will adopt the format outlined below, as applicable:*
*Compliance*
Refers to the adherence of the
software to specific industry standards, regulations, or internal policies.
This includes ensuring that the software meets legal and regulatory
requirements, follows best practices, and aligns with established security
and quality
*Optimisation*
The process of refining or
improving a software solution
*iVeri needs to:*
Provide 1st line support to the merchant. Provide support on the Back End Admin enquiries . Inform eCommerce 3rd Party on merchants to be onboarded. Onboard the merchant on the Admin Gateway & Cardinal for IYS. Provider merchant with credentials in order for them to add iVeri as their payment processor on their IYS Backend System.
* eCommerce 3rd Party needs to: *
Set up and Create the merchant on the IYS Platform (Store ID). Provide 2nd line support. Address technical queries that the merchant may have.
* Merchant needs to: *
Sign in and Set up their Online Store Configure and enable iVeri as the Payment processor using the iVeri provided store credentials Send iVeri their Store ID in order for iVeri to complete the onboarding
Below we will list the steps on how a merchant can view MauCas QR Transaction information:
Here are the sequential steps a merchant should follow on the device to designate MauCAS QR as the chosen payment method:
3D secure 2 is the latest standard released by EMVCo that allows merchants and payment service providers to send additional data elements to the issuing bank of the cardholder, which in turn, makes it possible for the issuer of the card to perform frictionless authentication and offer an improved, better, user experience to the cardholder. With the additional data elements relating to the cardholder, issuers can apply Frictionless Authentication flows or “Challenged” authentication flows.
Frictionless Authentication Flows: * issuers can apply risk-based decisions using the additional data received and trust that the real cardholder is making the purchase and auto authenticate the transaction in the background without requesting any additional information from the cardholder.
Challenged Aut
Transaction integrity can be seen as ensuring that all players within an individual iVeri transaction agree on its outcome. When a Card Holder gets his statement from his Issuer, it must correspond to his instruction to the merchant for a corresponding transaction. When transaction integrity is compromised either willfully (fraud) or unintentionally, it can result in a disputed transaction with legal impacts.
Individual transactions *** Void*
A Void of a previous transaction request is a command to ignore (i.e. cancel the effects of) a previous (recently submitted) transaction request. When a merchant receives a successful response for a transaction request, and thereafter “something goes wrong”, then the Merchant has the option to “void” the transaction.
Examples of “something goes wrong”