Establishing an organization data structure to include multiple entities

Patent metadata

Field	Value
Publication number	US-2025384441-A1
Application number	US-202418747409-A
Country	US
Kind code	A1
Filing date	Jun 18, 2024
Priority date	Jun 18, 2024
Publication date	Dec 18, 2025
Grant date	—

Abstract

An entity can be associated to another entity through an association with an organization. An authorized user in a first entity can request via an interface associated with the organization that an identifier of another entity be added to an organization data structure of the organization. The organization can verify the request and submit a request to the other entity. The other entity may become associated with the first entity. Aggregated functions may then be performed across all entities in the organization according to the organization data structure.

First claim

What is claimed is:

1 . A method comprising:
receiving, at a server, a request to add a second entity to an organization data structure, wherein the organization data structure includes an association with a first entity comprising first resources and second resources; sending, by the server to a device associated with the second entity, a request to associate the second entity with the organization data structure; receiving, by the server, a response from the device associated with the second entity indicating to associate the second entity with the organization data structure; associating, by the server, the second entity with the organization data structure by:
providing, from the server to the device associated with the second entity, an organization identifier to be stored in association with the second entity, and
storing, by the server, a second entity identifier associated with the second entity, wherein upon associating the second entity with the organization data structure, the second entity gains access to the first resources and not the second resources.

2 . The method of claim 1 , further comprising:
providing, by the server, a billing event reflecting a preferred rate between the first entity and the second entity to both the first entity and the second entity.

3 . The method of claim 1 , further comprising:
providing, by the server, an identifier of a customer object created at the first entity to a device associated with the second entity, wherein the second entity stores a set of access rules for accessing the customer object by the second entity, wherein the set of access rules is more restricted than a corresponding set of access rules associated with the customer object for the first entity.

4 . The method of claim 3 , further comprising:
providing, by the server, an identifier of a funding authorization associated with the customer object at the first entity to the second entity, wherein the second entity stores a second set of access rules in association with the identifier of the funding authorization.

5 . The method of claim 3 , further comprising:
when a device associated with the second entity receives a customer update command at the second entity for the customer object, wherein the first entity has primary authority over the customer object, the primary authority restricting at least some update access to the customer object, receiving, by the server, a request from the second entity to reassign the primary authority to the second entity; based on an authorization by the first entity, reassigning the primary authority to the second entity; and after the primary authority is reassigned to the second entity, processing, by the server, the update command for the customer object.

6 . The method of claim 1 , wherein:
a terminal processor in association with the organization data structure processes both a first event request associated with the first entity and a second event request associated with the second entity.

7 . The method of claim 1 , further comprising:
in response to a request for a search for data related to the organization data structure, providing, by the server, search results including an aggregation of search results from the first entity and the second entity.

8 . The method of claim 1 , further comprising:
in response to a report request for the organization data structure, providing, by the server, a report including report records from both the first entity and the second entity, and metrics derived from both the first entity and second entity.

9 . A device comprising:
a non-transitory computer-readable medium; one or more processors, configured to:
receive, at a server, a request to add a second entity to an organization data structure, wherein the organization data structure includes an association with a first entity comprising first resources and second resources;
send, by the server to a device associated with the second entity, a request to associate the second entity with the organization data structure;
receive, by the server, a response from the device associated with the second entity indicating to associate the second entity with the organization data structure;
associate, by the server, the second entity with the organization data structure by:
providing, from the server to the device associated with the second entity, an organization identifier to be stored in association with the second entity, and
storing, by the server, a second entity identifier associated with the second entity, wherein upon associating the second entity with the organization data structure, the second entity gains access to the first resources and not the second resources.

10 . The device of claim 9 , wherein the one or more processors are further configured to:
provide, by the server, an identifier of a customer object created at the first entity to a device associated with the second entity, wherein the second entity stores a set of access rules for accessing the customer object by the second entity, wherein the set of access rules is more restricted than a corresponding set of access rules associated with the customer object for the first entity.

11 . The device of claim 9 , wherein the one or more processors are further configured to:
in response to a request for a search for data related to the organization data structure, provide, by the server, search results including an aggregation of search results from the first entity and the second entity.

12 . The device of claim 9 , wherein the one or more processors are further configured to:
in response to a report request for the organization data structure, provide, by the server, a report including report records from both the first entity and the second entity, and metrics derived from both the first entity and second entity.

13 . A non-transitory computer-readable medium storing a set of instructions which when executed cause one or more processors to:
receive, at a server, a request to add a second entity to an organization data structure, wherein the organization data structure includes an association with a first entity comprising first resources and second resources; send, by the server to a device associated with the second entity, a request to associate the second entity with the organization data structure; receive, by the server, a response from the device associated with the second entity indicating to associate the second entity with the organization data structure; associate, by the server, the second entity with the organization data structure by: providing, from the server to the device associated with the second entity, an organization identifier to be stored in association with the second entity, and storing, by the server, a second entity identifier associated with the second entity, wherein upon associating the second entity with the organization data structure, the second entity gains access to the first resources and not the second resources.

14 . The non-transitory computer-readable medium of claim 13 , wherein the one or more instructions further cause the one or more processors to:
provide, by the server, a billing event reflecting a preferred rate between the first entity and the second entity to both the first entity and the second entity.

15 . The non-transitory computer-readable medium of claim 13 , wherein the one or more instructions further cause the one or more processors to:
provide, by the server, an identifier of a customer object created at the first entity to a device associated with

Assignees

• Stripe Inc

Inventors

• Wood Daniel
• Shields Patrick

Classifications

• G06Q30/04 Primary

  Billing or invoicing · CPC title

• G06Q20/401 Primary

  Transaction verification · CPC title