Easy creation of mobile payment code

Abstract

A user is presented with a first display with parties to a payment transaction and a second display on the same screen, where the user can drag and drop the parties on the first screen to the second screen to create a desired payment flow. A service provider, such as a payment provider, builds code based on the payment flow and zips it into a downloadable file. The user can then easily implement the zipped code into a mobile app that will allow a customer to make a purchase through the app using the payment provider. The zipped code uses a library of payment options offered by the payment provider and allows the user to input custom variables into these options. Code is automatically generated for the user to use based on the user input.

What is claimed is: 
     
         1 . A method for implementing a payment system, comprising:
 receiving, by a processor of a payment provider, a first actor in a payment flow, wherein the first actor is received by a user dragging and dropping the first actor from a first portion of an interface on a user device to a second portion of the interface;   determining, by the processor, whether the first actor is acceptable;   notifying the user if the first actor is not acceptable;   receiving, by the processor, a second actor in the payment flow, wherein the second actor is received by a user dragging and dropping the second actor from the first portion of the interface to the second portion of the interface;   determining, by the processor, whether the second actor is acceptable;   notifying the user if the second actor is not acceptable;   determining whether the user is finished with the payment flow;   receiving, by the processor, one or more additional actors from the user until a determination is made the user is finished with the payment flow or a maximum number of actors has been reached;   receiving, by the processor from the user via the interface, a type of code to be generated for the payment flow;   generating code according to the type; and   providing the code in a zip file to the user, wherein the code enables the user to implement the payment flow on a mobile app.   
     
     
         2 . The method of  claim 1 , wherein the first actor is a sender of funds and the second actor is a recipient of funds. 
     
     
         3 . The method of  claim 2 , wherein the recipient is a primary recipient of funds and the one or more additional actors are secondary recipient of funds. 
     
     
         4 . The method of  claim 1 , wherein the payment flow comprises one of a simple payment flow, a parallel payment flow, or a chained payment flow. 
     
     
         5 . The method of  claim 1 , wherein the one or more additional actors are of a different type than that of the first actor or the second actor. 
     
     
         6 . The method of  claim 1 , wherein the type of code is received from a user selection on the interface. 
     
     
         7 . The method of  claim 1 , wherein the type of code is one of iOS, Android, or Blackberry code. 
     
     
         8 . The method of  claim 1 , wherein the code is downloadable by the user. 
     
     
         9 . An apparatus comprising a non-transitory, tangible computer readable storage medium storing a computer program, wherein the computer program contains instructions that when executed, perform:
 receiving, by a payment provider, a first actor in a payment flow, wherein the first actor is received by a user dragging and dropping the first actor from a first portion of an interface on a user device to a second portion of the interface;   determining whether the first actor is acceptable;   notifying the user if the first actor is not acceptable;   receiving a second actor in the payment flow, wherein the second actor is received by a user dragging and dropping the second actor from the first portion of the interface to the second portion of the interface;   determining whether the second actor is acceptable;   notifying the user if the second actor is not acceptable;   determining whether the user is finished with the payment flow;   receiving one or more additional actors from the user until a determination is made the user is finished with the payment flow or a maximum number of actors has been reached;   receiving, from the user via the interface, a type of code to be generated for the payment flow;   generating code according to the type; and   providing the code in a zip file to the user, wherein the code enables the user to implement the payment flow on a mobile app.   
     
     
         10 . The apparatus of  claim 9 , wherein the first actor is a sender of funds and the second actor is a recipient of funds. 
     
     
         11 . The apparatus of  claim 10 , wherein the recipient is a primary recipient of funds and the one or more additional actors are secondary recipient of funds. 
     
     
         12 . The apparatus of  claim 9 , wherein the payment flow comprises one of a simple payment flow, a parallel payment flow, or a chained payment flow. 
     
     
         13 . The apparatus of  claim 9 , wherein the one or more additional actors are of a different type than that of the first actor or the second actor. 
     
     
         14 . The apparatus of  claim 9 , wherein the type of code is received from a user selection on the interface. 
     
     
         15 . The apparatus of  claim 9 , wherein the type of code is one of iOS, Android, or Blackberry code. 
     
     
         16 . The apparatus of  claim 9 , wherein the code is downloadable by the user. 
     
     
         17 . A system, comprising:
 a computer storage that stores an electronic item;   an electronic communications interface that is operable to:
 receive at least a first type of actor and a second type of actor from a user, wherein the first type of actor and the second type of actor are received by a user dragging and dropping the first type of actor and the second type of actor from a first portion of a user interface on a user device to a second portion of the user interface; 
 receive an indication that the user is finished with a payment flow or a maximum number of actors has been reached; 
 receive one or more additional types of actors from the user until a determination is made the user is finished with the payment flow or the maximum number of actors has been reached; and 
 receiving a type of code to be generated for the payment flow; 
   a computer processor that is operable to:
 determine whether the first type of actor is acceptable; 
 notify the user if the first type of actor is not acceptable; 
 determine whether the second type of actor is acceptable; 
 notifying the user if the second type of actor is not acceptable; 
 generate code according to the type; and 
 provide the code in a zip file to the user, wherein the code enables the user to implement the payment flow on a mobile app. 
   
     
     
         18 . The system of  claim 17 , wherein the payment flow comprises one of a simple payment flow, a parallel payment flow, or a chained payment flow. 
     
     
         19 . The system of  claim 17 , wherein the one or more additional types of actors are of a different type than that of the first type of actor or the second type of actor. 
     
     
         20 . The system of  claim 17 , wherein the first type is a sender of funds, the second type is a primary recipient of funds, and the one or more additional types are secondary recipient of funds.