Confirmed users
1,158
edits
No edit summary |
|||
| Line 32: | Line 32: | ||
== Payment Server (solitude) == | == Payment Server (solitude) == | ||
The solitude transaction is | The solitude transaction is created 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. | ||
Transactions have at least two phases: authorization and payment. | |||
{|border="1" cellpadding="2" | {|border="1" cellpadding="2" | ||
| Line 38: | Line 40: | ||
| '''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 | | '''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. The Marketplace stores it in tracking_id on the contribution. So zamboni.tracking_id equals solitude.uuid. | ||
|- | |- | ||
| '''uid_pay''' || An id from the provider that relates to | | '''uid_pay''' || An id from the provider that relates to the authorization of transaction. In Bango, this is the result of billingConfigurationId. In Paypal, it is the paykey. | ||
|- | |- | ||
| '''uid_support''' || When Bango completes the transaction, this is set bango_trans_id. This is the id used for refunds | | '''uid_support''' || An id from the provider that relates to the payment. When Bango completes the transaction, this is set to the values of bango_trans_id. This is the id used for refunds. If the transaction isn't completed, this won't be set. | ||
|} | |} | ||