# US 2017/0255926 A1 · Stored value design and distribution portal

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0255926 A1
- Document ID: US20170255926A1
- Status: Published application
- Kind: A1
- Application number: 15/430,161
- Filed: 2017-02-10
- Published: 2017-09-07
- Earliest claimed: 2016-03-04
- Applicants: Gift Card Impressions, LLC
- Inventors: Brett Glass; Karl Geisler
- Web page: https://patentgrep.com/patent/US20170255926A1

## CPC

- G06Q 20/348: {Single-use cards, i.e. without possibility of recharging}
- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/349: {Rechargeable cards}
- G06Q 20/3567: {Software being in the reader}
- G06Q 20/3672: {initialising or reloading thereof}
- G06Q: INFORMATION 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

## Abstract

A stored value design and distribution portal includes a computer-executable service that exposes a sponsor portal interface for receiving user supplied information for customizing a stored value card from a sponsor of the stored value card, and generates a stored value card design using the user supplied information in which the stored value card design is stored in a repository. Once generated, the service then publishes, using one or more second portal interfaces, the stored value card design for purchase as a stored value card by a consumer from the repository, and transmits the stored value card to the consumer.

## Claims

### Claim 1

A stored value design and distribution portal comprising:
a computing system comprising at least one memory for storing instructions that, when executed by at least one processor, are executed to:
expose a sponsor portal interface for receiving user supplied information for customizing a stored value card from a sponsor of the stored value card;
generate a stored value card design using the user supplied information, the stored value card design being stored in a repository;
publish, using one or more second portal interfaces, the stored value card design for purchase as a stored value card by a consumer from the repository, wherein the stored value card is published from the repository that is the same repository used to customize the stored value card; and
transmit the stored value card to the consumer.

### Claim 2 (depends on 1)

The stored value design and distribution portal of claim 1, wherein the repository used to store the generated stored value card is the same repository that is used to publish the stored value card design for purchase by the consumer.

### Claim 3 (depends on 1)

The stored value design and distribution portal of claim 1, wherein the portal is managed by an entity that is separate and distinct from the sponsor of the stored value card.

### Claim 4 (depends on 1)

The stored value design and distribution portal of claim 1, further comprising a service portal interface, wherein the instructions are further executed to conduct a financial transaction for the stored value card by exposing the service portal interface to a financial account server associated with the consumer, wherein the stored value card is accessed from the repository that is the same repository used to customize the stored value card.

### Claim 5 (depends on 1)

The stored value design and distribution portal of claim 1, wherein at least one of the sponsor portal interface, the service portal interface, or the consumer portal interface comprises an application program interface (API).

### Claim 6 (depends on 1)

The stored value design and distribution portal of claim 1, wherein the instructions are further executed to store the stored value card in the repository according to one of a plurality of versions.

### Claim 7 (depends on 1)

The stored value design and distribution portal of claim 1, wherein the instructions are further executed to store the stored value card in the repository according to one of a plurality of development status indicators, the development status indicators comprising at least one of a pending status indicator, an in-review status indicator, an approved status indicator, ab active status indicator, a de-activated status indicator, and a market test status indicator.

### Claim 8

A stored value design and distribution portal method comprising:
exposing, using executable instructions stored in a non-transitory medium and executed on at least one processor, a sponsor portal interface for receiving user supplied information for customizing a stored value card from a sponsor of the stored value card;
generating, using the instructions, a stored value card design using the user supplied information, the stored value card design being stored in a repository;
publishing, using the instructions, using one or more second portal interfaces, the stored value card design for purchase as a stored value card by a consumer from the repository, wherein the stored value card is published from the repository that is the same repository used to customize the stored value card; and
transmitting, using the instructions, the stored value card to the consumer.

### Claim 9 (depends on 8)

The stored value design and distribution portal method of claim 8, further comprising storing the stored value card design in the same repository that is used to publish the stored value card design for purchase by the consumer.

### Claim 10 (depends on 8)

The stored value design and distribution portal method of claim 8, further comprising managing the portal by an entity that is separate and distinct from the sponsor of the stored value card.

### Claim 11 (depends on 8)

The stored value design and distribution portal method of claim 8, further comprising conducting a financial transaction for the stored value card by exposing a service portal interface to a financial account server associated with the consumer, wherein the stored value card is accessed from the repository that is the same repository used to customize the stored value card.

### Claim 12 (depends on 8)

The stored value design and distribution portal method of claim 8, wherein at least one of the sponsor portal interface, the service portal interface, or the consumer portal interface comprises an application program interface (API).

### Claim 13 (depends on 8)

The stored value design and distribution portal method of claim 8, further comprising storing the stored value card in the repository according to one of a plurality of versions.

### Claim 14 (depends on 8)

The stored value design and distribution portal method of claim 8, further comprising storing the stored value card in the repository according to one of a plurality of development status indicators, the development status indicators comprising at least one of a pending status indicator, an in-review status indicator, an approved status indicator, ab active status indicator, a de-activated status indicator, and a market test status indicator.

### Claim 15

Code implemented in a non-transitory, computer readable medium that when executed by at least one computing unit, is operable to perform at least the following:
exposing a sponsor portal interface for receiving user supplied information for customizing a stored value card from a sponsor of the stored value card;
generating a stored value card design using the user supplied information, the stored value card design being stored in a repository;
publishing, using one or more second portal interfaces, the stored value card design for purchase as a stored value card by a consumer from the repository, wherein the stored value card is published from the repository that is the same repository used to customize the stored value card; and
transmitting the stored value card to the consumer.

### Claim 16 (depends on 15)

The code of claim 15, further executed to store the stored value card design in the same repository that is used to publish the stored value card design for purchase by the consumer.

### Claim 17 (depends on 15)

The code of claim 15, further executed to manage the portal by an entity that is separate and distinct from the sponsor of the stored value card.

### Claim 18 (depends on 15)

The code of claim 15, further comprising conducting a financial transaction for the stored value card by exposing a service portal interface to a financial account server associated with the consumer, wherein the stored value card is accessed from the repository that is the same repository used to customize the stored value card.

### Claim 19 (depends on 15)

The code of claim 15, further executed to store the stored value card in the repository according to one of a plurality of versions.

### Claim 20 (depends on 15)

The code of claim 15, further executed to store the stored value card in the repository according to one of a plurality of development status indicators, the development status indicators comprising at least one of a pending status indicator, an in-review status indicator, an approved status indicator, ab active status indicator, a de-activated status indicator, and a market test status indicator.
