Multi-service business platform system having payments systems and methods

Patent metadata

Field	Value
Publication number	US-12211014-B2
Application number	US-202217654542-A
Country	US
Kind code	B2
Filing date	Mar 11, 2022
Priority date	Mar 12, 2021
Publication date	Jan 28, 2025
Grant date	Jan 28, 2025

Abstract

The disclosure is directed to various ways of improving the functioning of computer systems, information networks, data stores, search engine systems and methods, and other advantages. Among other things, provided herein are methods, systems, components, processes, modules, blocks, circuits, sub-systems, articles, and other elements (collectively referred to in some cases as the “platform” or the “system”) that collectively enable, in one or more datastores (e.g., where each datastore may include one or more databases) and systems. A system and method for providing payment-related services that may utilize checkout parameters, a link generation service, a payment processing service, and a post-payment service. The link generation service may serve a checkout page using a set of the checkout parameters. The payment processing service may receive a transaction notification indicating whether a payment was successful or unsuccessful. The post-payment service may initiate a post-transaction workflow corresponding to an outcome indicated by the transaction notification.

First claim

What is claimed is:

1. A multi-service platform comprising memory and a processor that executes instructions stored within the memory to perform operations comprising:
generating a checkout link corresponding to an offering, wherein the checkout link includes a uniform resource identifier (URI), and wherein the checkout link is integrated into a messaging workflow of a customer relationship management (CRM) system for tracking event data relating to the checkout link;
storing sets of checkout parameters, relating to offerings provided by a set of different clients, in a checkout database that indexes the sets of checkout parameters using a portion of the URI;
receiving a request for a checkout page from a customer user device, wherein the request indicates the portion of the URI;
display the checkout page to the customer user device, wherein the checkout page is parameterized using the sets of checkout parameters retrieved using the portion of the URI;
updating a payments database based on a transaction notification indicating whether a payment, initiated through a payment session on behalf of a client, was successful or unsuccessful; and
executing the messaging workflow of the CRM system to track an outcome indicated by the transaction notification for generating an multi-object custom report on an effectiveness of the checkout link.

2. The multi-service platform of claim 1 , wherein the operations comprise:
analyzing an ontology that defines custom objects to identify a set of items that the client offers to customers.

3. The multi-service platform of claim 2 , wherein the operations comprise:
populating a checkout configuration graphical user interface (GUI) that is provided at a client user device with the set of items, such that the checkout configuration GUI allows a user to configure the offering by selecting a product offered by the client.

4. The multi-service platform of claim 1 , wherein the operations comprise:
exposing a webhook to a payment processor.

5. The multi-service platform of claim 4 , wherein the payment processor provides the transaction notification to the multi-service platform via the webhook.

6. The multi-service platform of claim 4 , wherein the—operations comprise:
adding the payment session to a listening thread that listens for the transaction notification via the webhook.

7. The multi-service platform of claim 1 , wherein the operations comprise:
retrieving client-provided content corresponding to the offering, wherein the client-provided content is served with the checkout page.

8. The multi-service platform of claim 7 , wherein the client-provided content includes client-provided media content.

9. The multi-service platform of claim 1 , wherein the operations comprise:
generating a payment event indicating that the offering was successfully transacted in response to receiving the transaction notification indicating that the transaction was successful.

10. The multi-service platform of claim 9 , further comprising a reporting system that generates custom reports on behalf of the client, wherein the reporting system generates reports based on payment events associated with the client.

11. The multi-service platform of claim 1 , further comprising:
a customer relationship management system that receives the checkout link and embeds the checkout link in an electronic medium that is transmitted to a contact of the client.

12. The multi-service platform of claim 1 , the sets of checkout parameters further include requirements that respectively define conditions to be satisfied before a customer can complete the transaction.

13. The multi-service platform of claim 12 , wherein the condition is that the customer electronically sign an electronic contract relating to the offering.

14. The multi-service platform of claim 1 , wherein the sets of checkout parameters further define that the payment is a one-time payment.

15. The multi-service platform of claim 1 , wherein the sets of checkout parameters further define that the payment is a recurring payment.

16. The multi-service platform of claim 15 , wherein the recurring payment is a subscription payment and the sets of checkout parameters further define a schedule on which future payments are processed.

17. The multi-service platform of claim 15 , wherein the recurring payment is a subscription payment and the sets of checkout parameters further define a number of payment installments and a schedule on which future installment payments are processed.

18. A computer-implemented method comprising:
generating a checkout link corresponding to an offering, wherein the checkout link includes a uniform resource identifier (URI), and wherein the checkout link is integrated into a messaging workflow of a customer relationship management (CRM) system for tracking event data relating to the checkout link;
storing sets of checkout parameters, relating to offerings provided by a set of different clients, in a checkout database that indexes the sets of checkout parameters using a portion of the URI;
receiving a request for a checkout page from a customer user device, wherein the request indicates the portion of the URI;
displaying the checkout page to the customer user device, wherein the checkout page is parameterized using the sets of checkout parameters retrieved using the portion of the URI;
updating a payments database based on a transaction notification indicating whether a payment, initiated through a payment session on behalf of a client, was successful or unsuccessful; and
executing the messaging workflow of the CRM system to track an outcome indicated by the transaction notification for generating an multi-object custom report on an effectiveness of the checkout link.

19. The method of claim 18 , comprising exposing a webhook to a payment processor, wherein the payment processor provides the transaction notification to a multi-service platform via the webhook.

20. The method of claim 19 , comprising adding the payment session to a listening thread that listens for the transaction notification via the webhook.

21. A non-transitory computer readable storage medium storing that when executed by a processor cause the processor to perform operations comprising:
generating a checkout link corresponding to an offering, wherein the checkout link includes a uniform resource identifier (URI), and wherein the checkout link is integrated into a messaging workflow of a customer relationship management (CRM) system for tracking event data relating to the checkout link;
storing sets of checkout parameters, relating to offerings provided by a set of different clients, in a checkout database that indexes the sets of checkout parameters using a portion of the URI;
receiving a request for a checkout page from a customer user device, wherein the request indicates the portion of the URI;
displaying the checkout page to the customer user device, wherein the checkout page is parameterized using the sets of checkout parameters retrieved using the portion of the URI;
updating a payments database based on a transaction notification indicating whether a payment, initiated through a payment session on behalf of a client, was successful or unsuccessful; and
executing the messaging workflow of the CRM system to track an outcome indicated by the transaction notification for generating an multi-object custom report on an effectiveness of the checkout link.

22. The computer readable storage medium of claim

Assignees

• Hubspot Inc

Inventors

• Schnitt Matt
• Parkin Christopher
• Rucci Daniel
• Wong Chris

Classifications

• G06N3/09

  Supervised learning · CPC title

• G06N3/0499

  Feedforward networks · CPC title

• G06Q30/01

  Customer relationship services · CPC title

• G06Q30/0271

  Personalized advertisement · CPC title

• G06Q30/0255

  based on user history · CPC title