Marketplace/TransactionNumbers: Difference between revisions

Marketplace/TransactionNumbers (view source)

5 bytes added , 3 February 2013

Confirmed users

1,158

edits

@@ Line 33: / Line 33: @@
 The solitude transaction is started for both app and in-app payments at the entrance to the trusted ui flow. The solitude transaction tracks more information than the marketplace knows, it shouldn't be the case that the marketplace needs to know much more, but if it does, it can query solitude.
 {|border="1" cellpadding="2"
 |-
-| id || The internal primary key on the table
+| '''id''' || The internal primary key on the table
 |-
-| '''uuid''' || An internal uuid generated when you start the transaction. When the transaction is completed in solitude we send a post back to the marketplace which stores it in tracking_id. So marketplace:tracking_id == solitude:uuid.
+| '''uuid''' || An internal uuid generated when you start the transaction. When the transaction is completed in solitude we send a post back to the marketplace which stores it in tracking_id. So zamboni.tracking_id equals solitude.uuid.
 |-
 | '''uid_pay''' || An id from the provider that relates to this transaction. For Bango this is the billingConfigurationId. This is id for the start of the Bango transaction. In Paypal it is the paykey.