Marketplace/TransactionNumbers: Difference between revisions
No edit summary |
|||
| Line 9: | Line 9: | ||
App payments start in the marketplace. A contribution record is created. These records are created when a user hits purchase. They might not complete the transaction and it might not be completed. | App payments start in the marketplace. A contribution record is created. These records are created when a user hits purchase. They might not complete the transaction and it might not be completed. | ||
{| | == Marketplace (zamboni) == | ||
App payments start in the marketplace. A contribution record is created. These records are created when a user hits purchase. They might not complete the transaction and it might not be completed. | |||
{|border="1" cellpadding="2" | |||
|- | |- | ||
! id ||uuid || transaction_id | |||
|- | |- | ||
|The internal primary key on the table|The externally available transaction id. This is given in receipts and used in the lookup. The marketplace knows this number, solitude does not.|The internally available transaction id. Used to communicate between the marketplace and the backend (eg: solitude). Should not be shared externally (but its not a big deal if it is) | |The internal primary key on the table || The externally available transaction id. This is given in receipts and used in the lookup. The marketplace knows this number, solitude does not. || The internally available transaction id. Used to communicate between the marketplace and the backend (eg: solitude). Should not be shared externally (but its not a big deal if it is) | ||
|} | |} | ||
In app payments do not currently go through the marketplace. No receipt is sent, no transaction is recorded in the marketplace. There is no transaction number from the marketplace point of view. There is however transaction information in solitude. | In app payments do not currently go through the marketplace. No receipt is sent, no transaction is recorded in the marketplace. There is no transaction number from the marketplace point of view. There is however transaction information in solitude. | ||
Revision as of 01:53, 3 February 2013
This refers to transaction numbers for payments on the Marketplace and the PaymentServer.
Overview
There are a mind boggling number of transaction numbers on the Marketplace payments system. It can confusing. This hopefully clarifies it.
Marketplace (zamboni)
App payments start in the marketplace. A contribution record is created. These records are created when a user hits purchase. They might not complete the transaction and it might not be completed.
Marketplace (zamboni)
App payments start in the marketplace. A contribution record is created. These records are created when a user hits purchase. They might not complete the transaction and it might not be completed.
| id | uuid | transaction_id |
|---|---|---|
| The internal primary key on the table | The externally available transaction id. This is given in receipts and used in the lookup. The marketplace knows this number, solitude does not. | The internally available transaction id. Used to communicate between the marketplace and the backend (eg: solitude). Should not be shared externally (but its not a big deal if it is) |
In app payments do not currently go through the marketplace. No receipt is sent, no transaction is recorded in the marketplace. There is no transaction number from the marketplace point of view. There is however transaction information in solitude.