PayGuardian Pharmacy Specific Features

PayGuardian – Pharmacy-Specific Features

  • RxRelation Form – Prompts the customer for their relationship to the patient. Possible relationships are:
      1. Patient
        Power of Attorney


  • RxYesNo Form – Prompts the customer with the text provided (customizable) and allows the customer to select a YES or a NO. For example: Do you understand the side effects of this medication?

  • RxCounsel Form – Text will be displayed at the top of the screen, and the Customer will be presented with 5 check box options:
      1. How to Use
        Side Effects
        Common Uses
        Speak to Pharmacist
        Warnings and Precautions

    The customer will have 3 button options: Back, Next, and Skip Counsel. The customer can also select as many checkbox options as needed.

  • Line Display Screen – Customizable form that allows a scrolling list of items to be displayed (such as products), including two lines of header text.

  • Clear Line Display – Allows for the clearing of the data currently displayed on the device screen.

  • Set a Custom Screen – Allows a custom form to be displayed on the device. No events will be propagated back to the integrated POS; only a Success/Fail response will be returned indicating whether or not the screen was successfully displayed.

  • Healthcare Support – PayGuardian also provides support for healthcare industry transactions (FSA or HSA accounts) through use of the Extended Data fields. The additional healthcare specific fields and associated amounts will need to be specified. The only required parameter value is HealthCareAmt. Amounts for optional healthcare specific fields can be specified to the HealthCareAmt to indicate how much was spent on:
    1. Prescription
      Dental and Clinic
      Hospitalization Services


PayGuardian – Basic Core Features

  • Signature Capture – Available option with a PayGuardian integrated signature capture device. Can be prompted by the device or by the integrated POS.
  • Custom branding with Images – Available as an option but the custom forms must be created and built independently. The software can be obtained directly from the Hardware vendor (i.e. Ingenico, etc.).
  • Point-to-Point Encryption – Available
  • Tokenization – Tokens can be generated as a new transaction by passing a $0.00 amount with a Credit Card transaction using the transaction type of TOKENADD. After initial generation, tokens can be used to process a credit card transaction as Card not present.


General Questions

    1. Does PayGuardian allow for an accept RX Message of our choice to display with a product list?
    Yes, we have a form that displays a message such as a Hippa agreement and requires a YES or a NO selection, or you can request a signature.
    2. Does PayGuardian allow multiple languages of our choice? Can the POS supply the desired text for each possible prompt?
    This second option may allow for the POS to control multiple languages.
    You can submit any text you like as long as it is in ASCII format.
    3. Does PayGuardian allow for a previous request sent by the POS to be cancelled from the POS?
    Yes, the transaction process flow is POS driven and not device driven.
    4. Does PayGuardian give the POS the ability to listen for events initiated by the customer on the payment pad such as a card swipe, card insert, or other payment action?
    This is opposed to the POS sending a request and then waiting for the response.
    No it is all POS driven.
    5. Is PayGuardian using RBA or OPOS or JPOS?
    JPOS drivers for the UIA interface.
    6. Once PayGuardian is in a card collection mode (or any other mode) can the POS make a call to interrupt/reset the isc250’s state?
    7. When using the tokenization/vaulting do credit card charges use the token to charge, or would the POS pull the raw credit card data and pass it back through as a card not present transaction?
    The transaction is sent as card not present using a token.
    8. Does card vaulting ever return the raw card number if requested?
    Never, only the token will be returned.