WebAPI/WebPayment: Difference between revisions

→‎In-app payment: add product ID
(→‎In-app payment: fixed camel case of productData in legend)
(→‎In-app payment: add product ID)
Line 88: Line 88:
       "name" : "Piece of Cake",
       "name" : "Piece of Cake",
       "description" : "Virtual chocolate cake to fill your virtual tummy",
       "description" : "Virtual chocolate cake to fill your virtual tummy",
      "id": "unique-id-for-product",
       "price" : [
       "price" : [
       {
       {
Line 117: Line 118:
*** '''name''' (mandatory): A short description of the product.
*** '''name''' (mandatory): A short description of the product.
*** '''description''' (mandatory): A long description of the product.
*** '''description''' (mandatory): A long description of the product.
*** '''id''' (mandatory): A unique identifier for the product you are selling. This only needs to be unique within your own catalog, not unique among all products from all apps.
*** '''productData''': A freeform string, no longer than 255 characters. This can be anything the app might need to identify the product with when a postback is sent back to the app.
*** '''productData''': A freeform string, no longer than 255 characters. This can be anything the app might need to identify the product with when a postback is sent back to the app.
*** '''postbackURL''': URL where the payment processor sends an HTTP POST message to whenever a purchase completes. The application server needs to acknowledge these POST messages, or else the transactions will be canceled. If the payment processor stores a different postback URL, this one should override the stored one. This way, application developer could choose different endpoints for different kind of digital goods.
*** '''postbackURL''': URL where the payment processor sends an HTTP POST message to whenever a purchase completes. The application server needs to acknowledge these POST messages, or else the transactions will be canceled. If the payment processor stores a different postback URL, this one should override the stored one. This way, application developer could choose different endpoints for different kind of digital goods.
Confirmed users
324

edits