Method to Manage Pending Transactions, and a System Thereof
US-2024394718-A1 · Nov 28, 2024 · US
US10339505B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10339505-B2 |
| Application number | US-201213586763-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 15, 2012 |
| Priority date | Jul 11, 2008 |
| Publication date | Jul 2, 2019 |
| Grant date | Jul 2, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Provided is a method and a web-site integration system to integrate payment mechanisms into a commercial website that offers online merchants a flexible, user-friendly and customizable wizard to integrate payment mechanisms into their online commercial websites without having to understand the detailed intricacies of an API or other computer code. The wizard steps the merchant through creating an account to obtain credentials and educates the merchant on the page flows of the payment mechanism that the merchant wishes to integrate. Then, the wizard generates code snippets and files to be downloaded by the merchant and to be easily inserted into key pages of the merchant's online commercial website. The merchant can then test the completely integrated code in a developer's sandbox or go live with the completely integrated code.
Opening claim text (preview).
We claim: 1. A system, comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: receiving a request to integrate an application programming interface (API)-based mechanism with an online website based at least on a first input received from a user interface of a device; accepting a plurality of credentials and parameters based at least on a second input received from the user interface; generating a plurality of code snippets and files based at least on the plurality of credentials and parameters, wherein the plurality of code snippets and files are configured to be tested in a sandbox environment or integrated live with the online website; transferring the plurality of code snippets and files to the device for display of an indication of the transferred plurality of code snippets and files on the user interface; communicating integration instructions to the device configured to integrate the plurality of code snippets and files with the online website to offer the API-based mechanism to visitors of the online website; and communicating test instructions to the device configured to test the the plurality of code snippets and files in the sandbox environment. 2. The system of claim 1 , wherein the operations further comprise: transferring page flow information to the device that causes the user interface to display a graphical representation comprising instructions to a given visitor to proceed from a shopping cart to a check out with the API-based mechanism. 3. The system of claim 1 , wherein the integration instructions are presented to the user interface with page flows of the API-based mechanism. 4. The system of claim 1 , wherein the operations further comprise receiving the second input from the user interface, wherein receiving the second input further comprises: receiving a selected plurality of credentials from the plurality of credentials and parameters, wherein the selected plurality of credentials is received based at least on a plurality of credential fields provided by the user interface; receiving a selection of a shopping cart programming language, wherein the selection is received from the user interface; receiving an input of a return URL, wherein the input of the return URL is received from the user interface; receiving an input of a cancel URL, wherein the input of the cancel URL is received from the user interface; and receiving a selection of a payment type, wherein the selection of the payment type is received from the user interface. 5. The system of claim 1 , wherein the operations further comprise: determining the API-based mechanism requires a visitor to leave the online website to make a payment; communicating a first set of the integration instructions to the user interface to integrate the API-based mechanism into a shopping cart page of the online website based at least on the API-based mechanism requiring the visitor to leave the online website to make the payment communicating a second set of the integration instructions to the user interface to integrate the API-based mechanism into a billing page of the online website based at least on the API-based mechanism requiring the visitor to leave the online website to make the payment; communicating a third set of the integration instructions to the user interface to integrate the API-based mechanism into an order review page of the online website based at least on the API-based mechanism requiring the visitor to leave the online website to make the payment; and communicating a fourth set of the integration instructions to the user interface to integrate the API-based mechanism into an order confirmation page of the online website based at least on the API-based mechanism requiring the visitor to leave the online website to make the payment. 6. The system of claim 5 , wherein the operations further comprise: retrieving a code snippet associated with the shopping cart page from the plurality of code snippets and files; inserting the code snippet into a code section of the online website where the shopping cart page is located; placing files from the plurality of code snippets and files into a shopping cart web directory of the online website; and saving a total payment amount associated with the shopping cart page in a session variable. 7. The system of claim 5 , wherein the operations further comprise: retrieving a code snippet associated with the billing page from the plurality of code snippets and files; inserting the code snippet into a code section of the online website where the billing page is located; replacing a shipping address placeholder in the billing page with variables representing a shipping address; and saving a total payment amount associated with the billing page in a session variable. 8. The system of claim 5 , wherein the operations further comprise: retrieving a code snippet associated with the order review page from the plurality of code snippets and files; inserting the code snippet into a code section of the online website where the order review page is located; causing the order review page to display a shipping address; and saving a total payment amount associated with the order review page in a session variable. 9. The system of claim 5 , wherein the operations further comprise: retrieving a code snippet associated with the order confirmation page from the plurality of code snippets and files; inserting the code snippet into a code section of the online website where the order confirmation page is located; saving a total payment amount associated with the order confirmation page in a session variable; processing information returned by the code snippet; and completing order backend processing for the online website associated with the order confirmation page. 10. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising: receiving a request to integrate an application programming interface (API)-based mechanism with an online website based at least on a first input received from a user interface of a device; accepting a plurality of credentials and parameters based at least on a second input received from the user interface; generating a plurality of code snippets and files based at least on the plurality of credentials and parameters, wherein the plurality of code snippets and files are configured to be tested in a sandbox environment or integrated live with the online website; transferring the plurality of code snippets and files to the device for display of an indication of the transferred plurality of code snippets and files on the user interface; and communicating integration instructions to the device configured to integrate the plurality of code snippets and files with the online website to offer the API-based mechanism to visitors of the online website; and communicating test instructions to the device configured to test the plurality of code snippets and files in the sandbox environment. 11. The non-transitory machine-readable medium of claim 10 , wherein the operations further comprise: transferring page flow information to the device that causes the user interface to display a graphical representation comprising instructions to a visitor to proceed from a shopping cart to a check out with the API-based mechanism. 12. The non-transitory machine-readable medium of claim 10 , wherein the integration instructions are presented to the use
Establishing or using transaction specific rules · CPC title
Payment circuits · CPC title
specially adapted for electronic shopping systems · CPC title
Buying, selling or leasing transactions · CPC title
Electronic shopping [e-shopping] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.