US20230047545A1 - System and Method for Pre-Paid Services - Google Patents

System and Method for Pre-Paid Services Download PDF

Info

Publication number
US20230047545A1
US20230047545A1 US17/975,655 US202217975655A US2023047545A1 US 20230047545 A1 US20230047545 A1 US 20230047545A1 US 202217975655 A US202217975655 A US 202217975655A US 2023047545 A1 US2023047545 A1 US 2023047545A1
Authority
US
United States
Prior art keywords
card
service
service provider
user
manager
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US17/975,655
Inventor
Chandra Bondugula
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US17/975,655 priority Critical patent/US20230047545A1/en
Publication of US20230047545A1 publication Critical patent/US20230047545A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/22Payment schemes or models
    • G06Q20/28Pre-payment schemes, e.g. "pay before"
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/342Cards defining paid or billed services or quantities
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/04Payment circuits
    • G06Q20/06Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102Bill distribution or payments
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/10Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/105Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems involving programming of a portable memory device, e.g. IC cards, "electronic purses"
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/12Payment architectures specially adapted for electronic shopping systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/38Payment protocols; Details thereof
    • G06Q20/40Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

Definitions

  • This disclosure relates to software implemented methods and computer based systems for prepayment and tracking of specified services.
  • Variability in the pricing of the same service provided to different customers, the same service provided during different time intervals, and the same service provided by different service providers are undesirable for customers, especially as they relate to expensive services or services lacking price transparency.
  • consumers of health care services in the U.S. typically do not know the total cost of a service in advance and people without insurance are typically charged a higher rate than an insurance company for the same service. While these problems are particularly acute in the U.S. health care industry, they are not unique to health care or a particular country. These problems also exist to a lesser extent in industries including dental care, automotive sales and repair, air travel, train travel, and hotel accommodations.
  • Embodiments of the present invention preferably seek to mitigate, alleviate or eliminate one or more deficiencies, disadvantages or issues, such as the above-identified, singly or in any combination, by providing a system, a method, and a non-transitory computer-readable storage media described herein.
  • the system and method provide for setting prices for specific services in advance and offering the sale of the services directly by a provider or through a third party.
  • the system and method provide for linking services to real or virtual cards comprising unique identifiers linking specific service prices to specific service providers and specific users.
  • the system and method may provide for registration and verification protocols designed to ensure that only the registered user assigned to each service card will receive the service specified by that service card.
  • FIG. 1 is a diagram showing communications between functional components of a pre-paid service system
  • FIG. 2 is a diagram showing movement of funds by and between components of a pre-paid service system
  • FIG. 3 is a diagram showing control of medical information by and between components of a pre-paid medical service system
  • FIG. 4 illustrates an example of a card of a pre-paid service system
  • FIG. 5 is a flow chart showing an example of interactions between a user and user interface components of a pre-paid service system.
  • FIG. 6 is a flow chart showing an example of functional steps involved in a method for pre-payment of a service from the point of view of the card manager.
  • a “service card” or “card” specifies a service or group of services for which the card is accepted as payment by a service provider.
  • a service card may be a physical card made of plastic, laminate, or other material, such as those commonly used as gift cards sold at retail stores.
  • a service card may additionally or alternatively be a virtual card, or digital card, that does not have a physical form but exists as stored data in a computer system and comprising the same information found on a physical card.
  • a “card manager” or “manager” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to manage the production and tracking of service cards, receive payments from the sale of service cards, register users of cards and service providers, and release payments to service providers when services have been provided.
  • a “card vender” or “card seller” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to sell service cards and to communicate with the card manager to direct transfers of funds from the sales of service cards to the control of the card manager.
  • a “service provider” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to register service providers with the card manager and communicate with the card manager to confirm services provided for which service cards are accepted as payment.
  • the term “medical service provider” refers to a service provider associated with providing medical or health care services. Examples of medical services include diagnostic tests, medical exams, and medical treatments and may be provided by a medical service provider such as a primary care, urgent care, medical specialist, imaging, dental, surgical, or medical testing practice. Medical services provided by a medical service provider may consist of a single service specified on a card or may comprise a bundle of services specified on a service card.
  • Dental services provided by a dental service provider may consist of a single service specified on a card or may comprise a bundle of services specified on a card. Examples of dental services include dental cleaning, examinations, x-rays, providing fillings, root canals, crowns, implants, and bridges, and orthodontist procedures.
  • a customer is a person or legal entity that buys, or pays for, one or more service cards.
  • the customer may also be, but need not be, a user. If the service provided is a medical service or dental service, the user must be may be referred to as a patient.
  • a customer need not intend or choose to redeem a card and may give a card to a user to be registered and redeemed or used.
  • a system for pre-paid services involves interactions between different functional components, each of which may comprise a number of communicating modules configured to perform specific sets of tasks.
  • a solid double arrow line indicates that an interface for direct communication between components is required.
  • a solid double arrow line indicates that an interface for direct communication between components is optional.
  • a card manager component comprises modules that, together, direct or control the production, sale, and register service cards, card users, and service providers.
  • the manager component comprises a seller interface module for exchanging information including inventory and usage status, using the unique identification of each card, with the seller module.
  • Inventory information exchanged with a seller module may be associated with one or more physical locations of a retailer, one or more on-line retail sellers, and/or an in-house seller module of a provider.
  • Usage status information may include whether a card has been sold, an amount of a payment toward the purchase of a card, whether it has been registered, the user to whom the card has been registered, and whether the card has been redeemed.
  • the card manager component comprises a sales income interface configured to receive electronic funds transfer from the seller module based upon cards sold wholesale to the seller/vender and/or based upon the retail sales of cards.
  • the manager component comprises a holding module configured to transfer at least a portion of income from the sale of each card into a holding account and to release funds to providers as the delivery of services to registered users are confirmed.
  • the card manager comprises a card generation module that creates sets of cards in a card database and may be configured to direct the production of physical and/or virtual cards to be sold using the card seller component.
  • the card generation module comprises user interfaces for data entry by operators of the manager component and optionally interfaces with an order module accessible to providers for entering data on number of cards, price, service provided, provider information, and terms of service, for example.
  • the manager component comprises a provider interface module for exchanging information including registration status and usage status, using the unique identification of each card, with the provider component.
  • Usage status information exchanged with the provider module may include the identity of the person to whom a card is registered and whether the service has been delivered.
  • the provider interface module is configured to receive registration information regarding the provider. Provider information may include tax identification number (EIN), password(s), user name, business name, names and credentials of practitioners/employees associated with the provider, and lists of services provided.
  • the provider interface module is configured to receive confirmation information verifying that the service has been rendered by the provider and/or received by the user. Validation that the service has been provided may include written acknowledgement by the user, a declaration by the provider, and/or validation information provided by a third party.
  • the manager component may comprise an optional user interface module configured for communicating with a user to receive information from the user to register a card to that user.
  • the user interface module is configured to receive information establishing the identity of the user such as images of a driver's license or other identification card.
  • the user interface module may also be configured to receive data for establishing an account such as password, user name, and email address.
  • a customer may purchase one or more cards by interacting with the card vender component.
  • a customer may purchase a service card online using a smart phone, tablet, or computer via a user interface module of the card seller component that is directly linked to the card manager at the same physical location.
  • a customer may purchase a service card in a brick and mortar location remote from the card manager using a user interface that is operated by a person at the location to enter data required by the card manager.
  • a vender may enter user information for the customer into the user interface module using a touch screen or keyboard or a customer may enter user information into the user interface module using a touch screen or keyboard on a vending machine comprising the vender component. If the vender location is a service provider providing the service(s) specified on the card(s), the card seller component may interface directly or indirectly with the service provider component at the location to provide data required by the service provider component and optionally the card manager component.
  • the card vender component comprises a manager interface module for exchanging information including inventory and usage status, using the unique identification of each card, with the manager component.
  • Inventory information exchanged with the manager component may be associated with one or more physical locations of a retailer, one or more on-line retail sellers, and/or an in-house seller module of a provider.
  • Usage status information may include whether a card has been sold, an amount of a payment toward the purchase of a card, whether it has been registered, the user to whom the card has been registered, and whether the card has been redeemed.
  • the card seller component comprises a sales income interface configured to connect with the manager component for authorizing/directing electronic funds transfer to the manager component based upon cards sold wholesale to the seller/vender and/or based upon the retail sales of cards.
  • the card vender component may comprise a feature allowing the customer to print a receipt with a unique card identifier. Additionally or alternatively, the card vender/seller component at a remote location may comprise hardware and software for printing a physical card or physical card duplicate of an electronic service card.
  • the card seller component may comprise a module configured to interface with an existing commercial payment gateway for online sales.
  • the card vender component of the system comprises software that tracks the inventory and sales of service cards and reports information on inventory and sales to the card manager portion, for example, via a wired or wireless internet connection.
  • the card vender portion comprises a software module that causes funds from the sale of service cards to automatically be transferred into an account under the control of the card manager component. If the account is with a commercial bank separate from the card manager, the card manager and card seller components may each comprise a software module configured to interface with the commercial bank software.
  • the service provider component comprises a manager interface module for exchanging information including registration of the provider with the manager, registration status of and usage status cards, and verification of service delivery with the provider interface module of the manager component.
  • the service provider component also comprises user interface module for receiving user information to register cards and confirm the identity of each registered user associated with each service card.
  • User information may include images of a driver's license or other identification card and account information such as password, user name, and email address.
  • the manager interface module sends information from the service provider to the provider interface of the card manager component that the specific service associated with a card has been provided to the registered user.
  • the card manager component causes the release of funds associated with the service provided from the holding account to the control of the service provider portion which may, for example, transfer the funds into an account controlled by the service provider or direct the automated printing and mailing of physical checks.
  • a customer may be, but need not be, the user.
  • a service card may be purchased by one person or entity and given to a user.
  • a user For the card to be used, a user must register the card with the card manager so as to establish a connection between a specific, identified user and a specific card having a unique identifier, such as a unique number, bar code, or RFID chip code. Proof of identity may be, for example, by social security number, driver's license number, or image of photo ID.
  • the card is preferably registered directly with the manager by the user online but may be registered using a card vender component, a service provider component, or by manual data entry into the manager component. Alternatively, the card may be registered to a business entity that will receive service(s) specified by the card.
  • a user may take the service card or a receipt with the card's unique identifier to a either a remote service provider location or a remote card seller location and register the card with the aid of a person entering data for the user into a card seller component user interface at the remote location. This may be particularly useful for users with visual or cognitive impairments and users that are not literate. Additionally or alternatively, the user may register the card by interacting with a person, for example via telephone or e-mail, who enters data manually into the card manager component software to register the user.
  • the person entering the data may be associated with the card manager directly, may enter data indirectly into the card manager software through a card vender component interfaced with the card manager software component, or indirectly into the card manager software through a service provider component of the system interfaced with the card manager software component.
  • the double arrow between the customer/user is dashed because communication between the card manager component and the customer and/or the user can be indirect via the card seller component or the service provider component.
  • the card manager component receives funds from card seller component, which requires payment from a customer for the sale of a cards.
  • the hardware and software of the card seller component may be physically remote from the card manager component or may be embodied as one or more modules of the card manager component.
  • the service provider component receives funds after the card manager component receives confirmation that the service has been provided.
  • the service provider component may cause the transfer funds to an operator of the card manager, for example when the service provider location comprises a card seller component or if the operator of the service provider component pays a subscription and/or registration fee to the operator of the card manager.
  • the medical service provider component may comprise a software module preventing inadvertent transmission of patient medical information to any other component of the pre-paid service system. This is indicated in FIG. 3 by “X” on arrows between the components. Additionally or alternatively, any one or more of the other components may comprise a software module preventing receipt of medical information from the medical service provider software.
  • FIG. 4 illustrates an example of a medical service card comprising information that may be present on a physical card or a virtual, electronic card.
  • the example shown in the figure is not drawn to scale and it may have any suitable alternate shape or size and serves as a prepaid card which may be utilized for a specified medical service such as a medical consultation, diagnostic test, or medical treatment for a fixed price specified on the card. Additionally or alternatively, the card may specify different prices associated with different service providers listed on the card.
  • Information displayed on a physical and/or an electronic medical service card may include the specific service or bundled services to be provided, the purchase price of the card/service, the identity of service provider(s) where the card is accepted as full payment for the service, a unique identifier for that card, a date range within which the card must be used, an expiration date by which the card must be used, a geographical region within which the card is valid or invalid, terms of service, conditions that may apply to the use of the card, contact information for the service provider(s) and/or the card manager, and contact information for a help line.
  • the card may display a score, for example from a rating system, indicating the rating of the service provider or several service providers.
  • One or more logos may be present to indicate the identities of the card manager operator and/or the service provider(s).
  • One or more pictograms, photos, symbols, colors, and/or drawings may be displayed on the card to indicate the service(s) specified and/or the valid geographic location. These types of markings are useful for quick reference and to assist customers and users that are not literate or proficient in the language in which the card is written. From the point of view of a customer/user an example of steps for obtaining and using the card are illustrated in FIG. 5 .
  • FIG. 6 illustrates an example of steps involved a method of making and using a specific pre-paid service card via a user interface of the card manager component.
  • the price, service, and service provider(s) are entered into the card manager software.
  • the price may be taken from a request for card production by one or more service providers and/or one or more card venders, for example.
  • One or more cards of physical and/or electronic type are produced by or at the direction of the card generation module, each with a specific card identifier and optionally distributed to venders/sellers.
  • the card generation module may be configured to receive data required for card production and direct a machine or computer to produce physical and/or digital/electronic cards. Additionally or alternatively, the card generation module may configured to communicate with a separate card and/or digital card manufacturer to provide instructions regarding the production and distribution of cards.
  • the vender/seller interface receives data regarding the unique identity of the card and the holding module directs at least a portion of received funds from the sale to a holding account, for subsequent transfer to the service provider component when confirmation has been received that the service has been provided.
  • the funds are preferably received directly via electronic funds transfer into an account accessible to the card manager component.
  • the service provider component When a user presents a registered card to a registered service provider that accepts the card, the service provider component receives data regarding the user and registered card through the user interface and transmits this data to the provider interface module for verification with the provider interface of the manager component. Upon receipt of a positive verification message from the manager component, the service provider provides the service in the usual way, for example by scheduling an appointment or service date. When the service has been performed, evidence regarding the completion of the service is entered into the service provider component software and transmitted to the card manager component via the provider interface. The card manager component releases funds associated with the card from the holding account into the control of the service provider component, for example via interface with a bank to transmit payment of the funds to an account associated with the service provider business.
  • the card generation module may be configured to receive data to create a master configuration by selecting data for entry via a user interface into such as the name of the service being pre-purchased, geographical region(s) such as cities, counties, or states where the card is accepted as payment, date range(s) during which the card must be registered and/or service must be provided, and card appearance such as color scheme or template theme and to store the card configuration for ordering.
  • the manager component may comprise a sales module configured for creating sales orders for batches of cards, optionally using a stored card configuration.
  • Data is entered into the system through a user interface including data such as the service being provided, a quantity of cards to be produced, the form(s) of the cards with respect to physical and/or digital, the price of the cards, and the geographical region(s) and/or jurisdictions of validity and/or distribution.
  • a sales order is created, details such as sales order, test name, color scheme, price, quantity, valid time window and actions taken may be displayed for review and possible corrections or edits.
  • the card order module may be configured for purchase order generation by entry of data through a user interface regarding card vender identity(ies), commission rate(s), quantities of cards, and type(s) of cards.
  • the sales module may be configured for online sales, optionally with options for selecting a location of the customer/user and search engine for service cards available in the selected location.
  • the search engine may comprise a map search function, search by service function, and/or search by price and/or service provider rating function.
  • An online seller module may provide an option for registering a group funding linked to a service card with a pre-defined user.
  • An online seller module may provide discounted prices for bulk card sales.

Abstract

A system and method for payment of services, especially health care services, at fixed prices allows a user to purchase a service card that is accepted by a service provider for full payment of a service. A card manager holds funds from the sale of the card and releases the funds to a service provider when documentation that the service has been provided is received.

Description

    RELATED APPLICATIONS
  • This application is a divisional of U.S. application Ser. No. 17/087,584 filed Nov. 2, 2020, which claims priority to U.S. provisional application 62/929,773 filed Nov. 1, 2019. U.S. Ser. No. 17/087,584 will issue as U.S. Pat. No. 11,494,752 on Nov. 8, 2022.
  • BACKGROUND OF THE INVENTION Field of the Invention
  • This disclosure relates to software implemented methods and computer based systems for prepayment and tracking of specified services.
  • Description of Related Art
  • Variability in the pricing of the same service provided to different customers, the same service provided during different time intervals, and the same service provided by different service providers are undesirable for customers, especially as they relate to expensive services or services lacking price transparency. For example, consumers of health care services in the U.S. typically do not know the total cost of a service in advance and people without insurance are typically charged a higher rate than an insurance company for the same service. While these problems are particularly acute in the U.S. health care industry, they are not unique to health care or a particular country. These problems also exist to a lesser extent in industries including dental care, automotive sales and repair, air travel, train travel, and hotel accommodations.
  • In the case of government funding of services, ensuring that the services are provided only to intended recipients is a concern, as is potential fraud on the part of service providers who may receive payment for services not delivered. Group funding of medical bills for life saving procedures, such as a collection jars at businesses and online funding sites also suffer from the risk of fraud. For those with health insurance, insurers may deny prior authorization for a medically necessary procedure, causing additional health risks and prolonging discomfort for patients. Payment of bills by insurers are often denied or delayed and medical practices require staff dedicated only to navigating hundreds of different insurance plans with different benefits, copayments, deductables, provider networks, and filing procedures.
  • Alternatives to current systems and methods for purchasing and selling health care services are needed for the benefit of health care consumers and health care providers. The alternative systems and methods for purchasing and selling health care services should control or reduce the cost of purchasing services as well as costs associated with providing services.
  • BRIEF SUMMARY OF THE INVENTION
  • Embodiments of the present invention preferably seek to mitigate, alleviate or eliminate one or more deficiencies, disadvantages or issues, such as the above-identified, singly or in any combination, by providing a system, a method, and a non-transitory computer-readable storage media described herein. The system and method provide for setting prices for specific services in advance and offering the sale of the services directly by a provider or through a third party. The system and method provide for linking services to real or virtual cards comprising unique identifiers linking specific service prices to specific service providers and specific users. The system and method may provide for registration and verification protocols designed to ensure that only the registered user assigned to each service card will receive the service specified by that service card. These and other advantages of the system and method for pre-paid services will become apparent in view of the following description of the invention.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure in which:
  • FIG. 1 is a diagram showing communications between functional components of a pre-paid service system;
  • FIG. 2 is a diagram showing movement of funds by and between components of a pre-paid service system;
  • FIG. 3 is a diagram showing control of medical information by and between components of a pre-paid medical service system;
  • FIG. 4 illustrates an example of a card of a pre-paid service system;
  • FIG. 5 is a flow chart showing an example of interactions between a user and user interface components of a pre-paid service system; and
  • FIG. 6 is a flow chart showing an example of functional steps involved in a method for pre-payment of a service from the point of view of the card manager.
  • DETAILED DESCRIPTION OF EMBODIMENTS
  • Specific embodiments of the invention are described with reference to the accompanying drawings. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure is thorough and complete, and fully conveys the scope of the invention to those skilled in the art. The terminology used in the detailed description of embodiments and illustrated in the accompanying drawings is not intended to be limiting of the invention. In the drawings, like numbers refer to like elements.
  • As used herein, a “service card” or “card” specifies a service or group of services for which the card is accepted as payment by a service provider. A service card may be a physical card made of plastic, laminate, or other material, such as those commonly used as gift cards sold at retail stores. A service card may additionally or alternatively be a virtual card, or digital card, that does not have a physical form but exists as stored data in a computer system and comprising the same information found on a physical card.
  • As used herein, a “card manager” or “manager” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to manage the production and tracking of service cards, receive payments from the sale of service cards, register users of cards and service providers, and release payments to service providers when services have been provided.
  • As used herein, a “card vender” or “card seller” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to sell service cards and to communicate with the card manager to direct transfers of funds from the sales of service cards to the control of the card manager.
  • As used herein, a “service provider” refers to the software and hardware components of a pre-paid service system that, together, perform functions required to register service providers with the card manager and communicate with the card manager to confirm services provided for which service cards are accepted as payment. The term “medical service provider” refers to a service provider associated with providing medical or health care services. Examples of medical services include diagnostic tests, medical exams, and medical treatments and may be provided by a medical service provider such as a primary care, urgent care, medical specialist, imaging, dental, surgical, or medical testing practice. Medical services provided by a medical service provider may consist of a single service specified on a card or may comprise a bundle of services specified on a service card. Dental services provided by a dental service provider may consist of a single service specified on a card or may comprise a bundle of services specified on a card. Examples of dental services include dental cleaning, examinations, x-rays, providing fillings, root canals, crowns, implants, and bridges, and orthodontist procedures.
  • A customer is a person or legal entity that buys, or pays for, one or more service cards. The customer may also be, but need not be, a user. If the service provided is a medical service or dental service, the user must be may be referred to as a patient. A customer need not intend or choose to redeem a card and may give a card to a user to be registered and redeemed or used.
  • The following description includes embodiments involving medical and non-medical services. It is understood that the invention is applicable to other pre-paid services as well as medical and dental services.
  • With reference to FIG. 1 , a system for pre-paid services according to the invention involves interactions between different functional components, each of which may comprise a number of communicating modules configured to perform specific sets of tasks. A solid double arrow line indicates that an interface for direct communication between components is required. A solid double arrow line indicates that an interface for direct communication between components is optional.
  • A card manager component comprises modules that, together, direct or control the production, sale, and register service cards, card users, and service providers. The manager component comprises a seller interface module for exchanging information including inventory and usage status, using the unique identification of each card, with the seller module. Inventory information exchanged with a seller module may be associated with one or more physical locations of a retailer, one or more on-line retail sellers, and/or an in-house seller module of a provider. Usage status information may include whether a card has been sold, an amount of a payment toward the purchase of a card, whether it has been registered, the user to whom the card has been registered, and whether the card has been redeemed. The card manager component comprises a sales income interface configured to receive electronic funds transfer from the seller module based upon cards sold wholesale to the seller/vender and/or based upon the retail sales of cards. The manager component comprises a holding module configured to transfer at least a portion of income from the sale of each card into a holding account and to release funds to providers as the delivery of services to registered users are confirmed.
  • The card manager comprises a card generation module that creates sets of cards in a card database and may be configured to direct the production of physical and/or virtual cards to be sold using the card seller component. The card generation module comprises user interfaces for data entry by operators of the manager component and optionally interfaces with an order module accessible to providers for entering data on number of cards, price, service provided, provider information, and terms of service, for example.
  • The manager component comprises a provider interface module for exchanging information including registration status and usage status, using the unique identification of each card, with the provider component. Usage status information exchanged with the provider module may include the identity of the person to whom a card is registered and whether the service has been delivered. The provider interface module is configured to receive registration information regarding the provider. Provider information may include tax identification number (EIN), password(s), user name, business name, names and credentials of practitioners/employees associated with the provider, and lists of services provided. The provider interface module is configured to receive confirmation information verifying that the service has been rendered by the provider and/or received by the user. Validation that the service has been provided may include written acknowledgement by the user, a declaration by the provider, and/or validation information provided by a third party.
  • The manager component may comprise an optional user interface module configured for communicating with a user to receive information from the user to register a card to that user. The user interface module is configured to receive information establishing the identity of the user such as images of a driver's license or other identification card. The user interface module may also be configured to receive data for establishing an account such as password, user name, and email address.
  • A customer may purchase one or more cards by interacting with the card vender component. For example, a customer may purchase a service card online using a smart phone, tablet, or computer via a user interface module of the card seller component that is directly linked to the card manager at the same physical location. A customer may purchase a service card in a brick and mortar location remote from the card manager using a user interface that is operated by a person at the location to enter data required by the card manager. A vender may enter user information for the customer into the user interface module using a touch screen or keyboard or a customer may enter user information into the user interface module using a touch screen or keyboard on a vending machine comprising the vender component. If the vender location is a service provider providing the service(s) specified on the card(s), the card seller component may interface directly or indirectly with the service provider component at the location to provide data required by the service provider component and optionally the card manager component.
  • The card vender component comprises a manager interface module for exchanging information including inventory and usage status, using the unique identification of each card, with the manager component. Inventory information exchanged with the manager component may be associated with one or more physical locations of a retailer, one or more on-line retail sellers, and/or an in-house seller module of a provider. Usage status information may include whether a card has been sold, an amount of a payment toward the purchase of a card, whether it has been registered, the user to whom the card has been registered, and whether the card has been redeemed. The card seller component comprises a sales income interface configured to connect with the manager component for authorizing/directing electronic funds transfer to the manager component based upon cards sold wholesale to the seller/vender and/or based upon the retail sales of cards.
  • The card vender component may comprise a feature allowing the customer to print a receipt with a unique card identifier. Additionally or alternatively, the card vender/seller component at a remote location may comprise hardware and software for printing a physical card or physical card duplicate of an electronic service card. The card seller component may comprise a module configured to interface with an existing commercial payment gateway for online sales.
  • The card vender component of the system comprises software that tracks the inventory and sales of service cards and reports information on inventory and sales to the card manager portion, for example, via a wired or wireless internet connection. The card vender portion comprises a software module that causes funds from the sale of service cards to automatically be transferred into an account under the control of the card manager component. If the account is with a commercial bank separate from the card manager, the card manager and card seller components may each comprise a software module configured to interface with the commercial bank software.
  • The service provider component comprises a manager interface module for exchanging information including registration of the provider with the manager, registration status of and usage status cards, and verification of service delivery with the provider interface module of the manager component. The service provider component also comprises user interface module for receiving user information to register cards and confirm the identity of each registered user associated with each service card. User information may include images of a driver's license or other identification card and account information such as password, user name, and email address. When the service has been provided, the manager interface module sends information from the service provider to the provider interface of the card manager component that the specific service associated with a card has been provided to the registered user. The card manager component causes the release of funds associated with the service provided from the holding account to the control of the service provider portion which may, for example, transfer the funds into an account controlled by the service provider or direct the automated printing and mailing of physical checks.
  • A customer may be, but need not be, the user. A service card may be purchased by one person or entity and given to a user. For the card to be used, a user must register the card with the card manager so as to establish a connection between a specific, identified user and a specific card having a unique identifier, such as a unique number, bar code, or RFID chip code. Proof of identity may be, for example, by social security number, driver's license number, or image of photo ID. The card is preferably registered directly with the manager by the user online but may be registered using a card vender component, a service provider component, or by manual data entry into the manager component. Alternatively, the card may be registered to a business entity that will receive service(s) specified by the card. Additionally or alternatively, a user may take the service card or a receipt with the card's unique identifier to a either a remote service provider location or a remote card seller location and register the card with the aid of a person entering data for the user into a card seller component user interface at the remote location. This may be particularly useful for users with visual or cognitive impairments and users that are not literate. Additionally or alternatively, the user may register the card by interacting with a person, for example via telephone or e-mail, who enters data manually into the card manager component software to register the user. The person entering the data may be associated with the card manager directly, may enter data indirectly into the card manager software through a card vender component interfaced with the card manager software component, or indirectly into the card manager software through a service provider component of the system interfaced with the card manager software component. The double arrow between the customer/user is dashed because communication between the card manager component and the customer and/or the user can be indirect via the card seller component or the service provider component.
  • With respect to FIG. 2 , the flow of funds directed by the system is shown using solid arrows for required flow and a dashed arrow for optional flow. The card manager component receives funds from card seller component, which requires payment from a customer for the sale of a cards. The hardware and software of the card seller component may be physically remote from the card manager component or may be embodied as one or more modules of the card manager component. The service provider component receives funds after the card manager component receives confirmation that the service has been provided. The service provider component may cause the transfer funds to an operator of the card manager, for example when the service provider location comprises a card seller component or if the operator of the service provider component pays a subscription and/or registration fee to the operator of the card manager.
  • With respect to FIG. 3 , an example of confidential patient data flow for an embodiment involving medical services is shown. The medical service provider component may comprise a software module preventing inadvertent transmission of patient medical information to any other component of the pre-paid service system. This is indicated in FIG. 3 by “X” on arrows between the components. Additionally or alternatively, any one or more of the other components may comprise a software module preventing receipt of medical information from the medical service provider software.
  • FIG. 4 illustrates an example of a medical service card comprising information that may be present on a physical card or a virtual, electronic card. The example shown in the figure is not drawn to scale and it may have any suitable alternate shape or size and serves as a prepaid card which may be utilized for a specified medical service such as a medical consultation, diagnostic test, or medical treatment for a fixed price specified on the card. Additionally or alternatively, the card may specify different prices associated with different service providers listed on the card. Information displayed on a physical and/or an electronic medical service card may include the specific service or bundled services to be provided, the purchase price of the card/service, the identity of service provider(s) where the card is accepted as full payment for the service, a unique identifier for that card, a date range within which the card must be used, an expiration date by which the card must be used, a geographical region within which the card is valid or invalid, terms of service, conditions that may apply to the use of the card, contact information for the service provider(s) and/or the card manager, and contact information for a help line. The card may display a score, for example from a rating system, indicating the rating of the service provider or several service providers.
  • One or more logos may be present to indicate the identities of the card manager operator and/or the service provider(s). One or more pictograms, photos, symbols, colors, and/or drawings may be displayed on the card to indicate the service(s) specified and/or the valid geographic location. These types of markings are useful for quick reference and to assist customers and users that are not literate or proficient in the language in which the card is written. From the point of view of a customer/user an example of steps for obtaining and using the card are illustrated in FIG. 5 .
  • FIG. 6 illustrates an example of steps involved a method of making and using a specific pre-paid service card via a user interface of the card manager component. For a given card for a given service, and associated price, the price, service, and service provider(s) are entered into the card manager software. The price may be taken from a request for card production by one or more service providers and/or one or more card venders, for example. One or more cards of physical and/or electronic type are produced by or at the direction of the card generation module, each with a specific card identifier and optionally distributed to venders/sellers. The card generation module may be configured to receive data required for card production and direct a machine or computer to produce physical and/or digital/electronic cards. Additionally or alternatively, the card generation module may configured to communicate with a separate card and/or digital card manufacturer to provide instructions regarding the production and distribution of cards.
  • When cards are sold, the vender/seller interface receives data regarding the unique identity of the card and the holding module directs at least a portion of received funds from the sale to a holding account, for subsequent transfer to the service provider component when confirmation has been received that the service has been provided. The funds are preferably received directly via electronic funds transfer into an account accessible to the card manager component.
  • When a user presents a registered card to a registered service provider that accepts the card, the service provider component receives data regarding the user and registered card through the user interface and transmits this data to the provider interface module for verification with the provider interface of the manager component. Upon receipt of a positive verification message from the manager component, the service provider provides the service in the usual way, for example by scheduling an appointment or service date. When the service has been performed, evidence regarding the completion of the service is entered into the service provider component software and transmitted to the card manager component via the provider interface. The card manager component releases funds associated with the card from the holding account into the control of the service provider component, for example via interface with a bank to transmit payment of the funds to an account associated with the service provider business.
  • The card generation module may be configured to receive data to create a master configuration by selecting data for entry via a user interface into such as the name of the service being pre-purchased, geographical region(s) such as cities, counties, or states where the card is accepted as payment, date range(s) during which the card must be registered and/or service must be provided, and card appearance such as color scheme or template theme and to store the card configuration for ordering.
  • The manager component may comprise a sales module configured for creating sales orders for batches of cards, optionally using a stored card configuration. Data is entered into the system through a user interface including data such as the service being provided, a quantity of cards to be produced, the form(s) of the cards with respect to physical and/or digital, the price of the cards, and the geographical region(s) and/or jurisdictions of validity and/or distribution. Once a sales order is created, details such as sales order, test name, color scheme, price, quantity, valid time window and actions taken may be displayed for review and possible corrections or edits. Additionally or alternatively, the card order module may be configured for purchase order generation by entry of data through a user interface regarding card vender identity(ies), commission rate(s), quantities of cards, and type(s) of cards.
  • The sales module may be configured for online sales, optionally with options for selecting a location of the customer/user and search engine for service cards available in the selected location. The search engine may comprise a map search function, search by service function, and/or search by price and/or service provider rating function. An online seller module may provide an option for registering a group funding linked to a service card with a pre-defined user. An online seller module may provide discounted prices for bulk card sales.

Claims (16)

1. A method for operating a pre-paid service providing system that provides a service to a user by a service provider, said method comprising:
providing a card, said card comprising information specifying the service to be performed, a fixed price for the service, and a unique identifier;
registering the service provider with a card manager, said registering comprising establishment of means for transferring funds from a holding account controlled by the card manager to an account controlled by the service provider;
receiving information on a sale of the card to the user by the card manager, said information comprising the unique identifier;
receiving funds from the sale of the card by the card manager and placing at least a portion of the funds in the holding account;
registering the user of the card with the card manager, said registering comprising the receiving the identity of the user and the unique identifier by the card manager;
registering the user with the service provider, said registering comprising confirming the identity of the user by the service provider;
confirming to the card manager that the service has been provided to the user by the service provider; and
causing the transfer of funds from the holding account to the account controlled by the service provider by the card manager.
2. The method of claim 1, further comprising confirming to the card manager that the service provider has confirmed the identity of the user.
3. The method of claim 1, wherein said providing the card comprises the sale of the card by a vendor, said vendor communicating the sale of the card to the card manager.
4. The method of claim 1, wherein the card comprises information specifying a price of the card.
5. The method of claim 1, wherein said service provider is a medical service provider and the service is a medical service or a dental service.
6. The method of claim 5, and further comprising preventing medical information of the user from being transmitted to, or being received by, the card manager.
7. The method of claim 1, further comprising producing the card at the direction of the card manager as a part of a plurality of the cards.
8. The method of claim 1, wherein the card is a virtual card.
9. The method of claim 8, and further comprising printing a corresponding physical card or a physical card duplicate of the virtual card.
10. The method of claim 1, and further comprising entering data into the card manager, said data comprising a number of the cards to produce, a price of the card, the service to be provided, provider information, and terms of service.
11. The method of claim 1, and further comprising receiving information by the card manager from the service provider, said information comprising services provided by the service provider and credentials of employees associated with the service provider.
12. The method of claim 1, wherein said confirming the identity of the user by the service provider comprises using an image of an identification card of the user.
13. The method of claim 1, and further comprising the receipt of data into the card manager from the service provider for establishing an account of the service provider with the card manger.
14. The method of claim 12, wherein said data comprises an account password and an account name.
15. The method of claim 1, and further comprising exchange of information between the card manger and a card vendor, said information comprising an inventory of cards to which the card belongs and a usage status of cards in the inventory.
16. The method of claim 1, and further comprising printing a receipt upon the sale of the card, said receipt comprising the unique identifier of the card.
US17/975,655 2019-11-01 2022-10-28 System and Method for Pre-Paid Services Pending US20230047545A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/975,655 US20230047545A1 (en) 2019-11-01 2022-10-28 System and Method for Pre-Paid Services

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201962929773P 2019-11-01 2019-11-01
US17/087,584 US11494752B1 (en) 2019-11-01 2020-11-02 System and method for pre-paid services
US17/975,655 US20230047545A1 (en) 2019-11-01 2022-10-28 System and Method for Pre-Paid Services

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US17/087,584 Division US11494752B1 (en) 2019-11-01 2020-11-02 System and method for pre-paid services

Publications (1)

Publication Number Publication Date
US20230047545A1 true US20230047545A1 (en) 2023-02-16

Family

ID=83902482

Family Applications (2)

Application Number Title Priority Date Filing Date
US17/087,584 Active 2041-02-12 US11494752B1 (en) 2019-11-01 2020-11-02 System and method for pre-paid services
US17/975,655 Pending US20230047545A1 (en) 2019-11-01 2022-10-28 System and Method for Pre-Paid Services

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US17/087,584 Active 2041-02-12 US11494752B1 (en) 2019-11-01 2020-11-02 System and method for pre-paid services

Country Status (1)

Country Link
US (2) US11494752B1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7792686B2 (en) * 2006-12-05 2010-09-07 Stoneeagle Services, Inc. Medical benefits payment system
US20120054102A1 (en) * 2010-08-26 2012-03-01 Obopay, Inc. Method & System for Providing Payments Over A Wireless Connection
WO2012097310A1 (en) * 2011-01-14 2012-07-19 Visa International Service Association Healthcare prepaid payment platform apparatuses, methods and systems
US8249893B1 (en) * 2012-04-05 2012-08-21 Stoneeagle Services, Inc. Automated service provider payment method
WO2012122065A1 (en) * 2011-03-04 2012-09-13 Visa International Service Association Healthcare wallet payment processing apparatuses, methods and systems
US9760871B1 (en) * 2011-04-01 2017-09-12 Visa International Service Association Event-triggered business-to-business electronic payment processing apparatuses, methods and systems

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7792686B2 (en) * 2006-12-05 2010-09-07 Stoneeagle Services, Inc. Medical benefits payment system
US20120054102A1 (en) * 2010-08-26 2012-03-01 Obopay, Inc. Method & System for Providing Payments Over A Wireless Connection
WO2012097310A1 (en) * 2011-01-14 2012-07-19 Visa International Service Association Healthcare prepaid payment platform apparatuses, methods and systems
WO2012122065A1 (en) * 2011-03-04 2012-09-13 Visa International Service Association Healthcare wallet payment processing apparatuses, methods and systems
US20120239417A1 (en) * 2011-03-04 2012-09-20 Pourfallah Stacy S Healthcare wallet payment processing apparatuses, methods and systems
US9760871B1 (en) * 2011-04-01 2017-09-12 Visa International Service Association Event-triggered business-to-business electronic payment processing apparatuses, methods and systems
US8249893B1 (en) * 2012-04-05 2012-08-21 Stoneeagle Services, Inc. Automated service provider payment method

Also Published As

Publication number Publication date
US11494752B1 (en) 2022-11-08

Similar Documents

Publication Publication Date Title
US10311207B2 (en) Healthcare system and method for right-time claims adjudication and payment
US20130332199A1 (en) Systems and methods for consumer-driven mobile healthcare payments
US7689444B2 (en) Electronic insurance application fulfillment system and method
US8849683B2 (en) Receipt insurance systems and methods
US20140304010A1 (en) Healthcare system and method for real-time claims adjudication and payment
US20050080649A1 (en) Systems and methods for automating the capture, organization, and transmission of data
US20070198407A1 (en) Self-pay management system and process for the healthcare industry
US20050182660A1 (en) Business method and system for providing an on-line healthcare market exchange for procuring and financing medical services and products
US20070033070A1 (en) System and method for collecting payments from service recipients
CN107016533B (en) Electronic bill management device and electronic bill management method
US20010034621A1 (en) System and method for standardized and automated appeals process
US20080033771A1 (en) Ticket upgrade self-serve kiosk
US20070192144A1 (en) Health care analysis system and methods
CN103339645A (en) Method for activating an insurance policy online and device for carrying out said method
US20050256737A1 (en) System and method for facilitating meetings between pharmaceutical sales representatives and physicians
US20170351824A1 (en) Advance payment processing system computer for medical service provider bills
US10719581B2 (en) System and method for securing the remuneration of patient responsibilities for healthcare services in a revenue management cycle
US20090319294A1 (en) Managed distribution solution and methods thereof
US7774210B1 (en) Method and system for recording and maintaining patient history data as well as generating concurrent billing records
US11494752B1 (en) System and method for pre-paid services
CN103337030A (en) Systems and methods for transactions processing
US20150100342A1 (en) Mobile app for contact lenses
US20140288949A1 (en) Telephonic Device Payment Processing
JP2001028026A (en) Transaction support system
US20110099028A1 (en) Systems and methods for verifying medical program eligibility and payment data

Legal Events

Date Code Title Description
STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED