US2014164231A1PendingUtilityA1

Person-to-person payments: contextual spending

Assignee: EBAY INCPriority: Dec 19, 2007Filed: Feb 17, 2014Published: Jun 12, 2014
Est. expiryDec 19, 2027(~1.4 yrs left)· nominal 20-yr term from priority
G06Q 20/223G06Q 20/40G06Q 30/06G06Q 40/02G06Q 20/102G06Q 20/10
58
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Receiving at a payment system a request associated with a first party to make a payment to a second party. Recommendations for utilizing the payment are evaluated based on a profile of the second party. The payment and a recommendation for utilization of the payment are sent to the second party. The recommendation that is sent is based on a profile of the second party and may include shopping at a physical store, shopping at an online store, ordering from a catalog, saving in an account, ordering a credit card, ordering a debit card. A transaction fee associated with the payment, and a portion of the fee to be paid by each party is calculated.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A computerized method comprising:
 receiving, at a payment system, a request associated with a first party to make a payment to a second party;   evaluating, by one or more recommendation applications executed by at least one computer processor, recommendations for utilizing the payment, the recommendations based on a spending behavior of the second party, the spending behavior of the second party including at least one of a group of behaviors consisting of heavy shopping, preferring a certain shop, preferring a group of shops, preferring a method of payment, having applied for certain credit cards, and not having applied for certain credit cards; and   from the payment system, sending the payment and a recommendation for utilization of the payment to the second party.

Join the waitlist — get patent alerts

Track US2014164231A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.