Method and system for facilitating online payments based on an established payment agreement
US-9317841-B2 · Apr 19, 2016 · US
US9940622B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9940622-B2 |
| Application number | US-201615091199-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 5, 2016 |
| Priority date | Apr 13, 2004 |
| Publication date | Apr 10, 2018 |
| Grant date | Apr 10, 2018 |
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.
A method and system for facilitating online payments are disclosed. According to one aspect of the present invention, a payment agreement is established at a payment service provider that defines terms of a payment relationship between a merchant and a user. The establishing of the payment agreement includes linking the payment agreement with a payment account of the merchant or user stored at the payment service provider. After establishing the payment agreement, a payment request associated with a transaction is received, whereby the payment request includes a unique identifier to identify the payment agreement stored at the payment service provider. Based on a verification that the payment request complies with terms of the payment agreement, the payment request is processed.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, at an Application Programming Interface (API) module deployed in a payment service provider server of a payment service provider that is distinct from a merchant server of a merchant, an Application Programming Interface (API) call that includes a payment request associated with a transaction between a user and the merchant, the payment request including a unique identifier to identify a payment agreement previously established between the merchant and the user, the API call being received from the merchant server in response to the user making a particular user selection on a user interface of a merchant site provided by the merchant server; verifying, by a data verification module deployed in the payment service provider server, that the payment request complies with terms of the payment agreement identified by the unique identifier; and based on the verifying that the payment request complies with the terms of the payment agreement, automatically and without requiring user intervention, processing, by a payment processing module deployed in the payment service provider server, the payment request to cause transfer of funds to a merchant account, the receiving of the payment request, the verifying of the payment request, and the processing of the payment request all being in response to the particular user selection and being performed without directing the user to a service provider site of the payment service provider such that the payment request is received, verified, and processed by the payment service provider server based on user interaction with the merchant site instead of being based on user interaction with the service provider site. 2. The method of claim 1 , wherein the payment agreement defines terms including an authority granted by the user to a payment service provider associated with the payment service provider server to make payments to the merchant on behalf of the user. 3. The method of claim 2 , wherein the verifying that the payment request complies with terms of the payment agreement comprises verifying that processing the payment request does not exceed the authority granted by the user. 4. The method of claim 3 , wherein verifying that processing the payment request does not exceed the authority granted comprises verifying that processing the payment would not exceed a maximum payment amount set by the user. 5. The method of claim 3 , wherein verifying that processing the payment request does not exceed the authority granted comprises verifying that processing the payment would not exceed a maximum number of payment requests processed over a predetermined time period. 6. The method of claim 3 , wherein verifying that processing the payment request does not exceed the authority granted comprises verifying that the payment request is in connection with a product or service for which the payment service provider is authorized to make a payment. 7. The method of claim 1 , further comprising receiving, at the payment service provider server via a programmatic interface from the merchant server, an API call that includes a relationship request to establish, at the payment service provider server, the payment agreement between the merchant and the user prior to any transactions between the merchant and the user, the API call triggered in response to a selection by the user of a link to establish the payment agreement on an interface presented to a device of the user. 8. The method of claim 7 , further comprising establishing the payment agreement between the merchant and the user, the establishing of the payment agreement comprising linking the payment agreement with an account of the merchant or user maintained at the payment service provider, the payment service provider being a separate entity from the merchant. 9. A system comprising: a machine readable medium having instructions stored thereon; and one or more hardware processors configured to, in response to execution of the instructions, cause the system to perform operations comprising: receive, at an Application Programming Interface (API) module deployed in a payment service provider server of a payment service provider that is distinct from a merchant server of a merchant, an Application Programming Interface (API) call that includes a payment request associated with a transaction between a user and the merchant, the payment request including a unique identifier to identify a payment agreement previously established between the merchant and the user, the API call being received from the merchant server in response to the user making a particular user selection on a user interface of a merchant site provided by the merchant server; verify, by a data verification module deployed in the payment service provider server, that the payment request complies with terms of the payment agreement identified by the unique identifier; based on the payment request complying with the terms of the payment agreement, automatically and without requiring user intervention, initiate, by a payment processing module deployed in the payment service provider server, an attempt to process the payment request to cause transfer of funds to a merchant account, the receiving of the payment request, the verifying of the payment request, and the initiating of the attempt to process the payment request all being in response to the particular user selection and being performed without directing the user to a service provider site of the payment service provider such that the payment request is received, verified, and processed by the payment service provider server based on user interaction with the merchant site instead of being based on user interaction with the service provider site; and in response to the attempt being unsuccessful, send a notification to the merchant server indicating that the attempt was unsuccessful. 10. The system of claim 9 , wherein the payment agreement defines terms including an authority granted by the user to a payment service provider associated with the payment service provider server to make payments to the merchant on behalf of the user. 11. The system of claim 10 , wherein the operations include verify that the payment request complies with terms of the payment agreement by verifying that processing the payment request does not exceed the authority granted by the user. 12. The system of claim 11 , wherein the operations include verify that processing the payment request does not exceed the authority granted by performing at least one of: verifying that processing the payment would not exceed a maximum payment amount set by the user; verifying that processing the payment would not exceed a maximum number of payment requests processed over a predetermined time period; or verifying that the payment request is in connection with a product or service for which the payment service provider is authorized to make a payment. 13. The system of claim 9 , wherein the operations further include receive, via a programmatic interface from the merchant server, an API call that includes a relationship request to establish, at the payment service provider server, the payment agreement between the merchant and the user prior to any transactions between the merchant and the user, the API call triggered in response to a selection by the user of a link to establish the payment agreement on an interface presented to a device of the user. 14. The system of claim 13 , wherein the operations further include establish the payment agreement between the merchant and the user, wherein establishing the payment agreement includes li
involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] · CPC title
specially adapted for electronic shopping systems · CPC title
specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems · CPC title
Finance; Insurance; Tax strategies; Processing of corporate or income taxes · CPC title
Bill distribution or payments · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.