Transaction ID API needs.

[that1guy]

Here's what we need to complete online payment workflow correctly and securely.

When two users (buyer and seller) agree to meet, (AKA a posting object has an offer on it with an "acceptedAt" property on it) we need to generate a unique transactionID for that possible future transaction.

If a GET request is performed to lookup a transactionID we should get back the following information.

• The entire posting associated with that transaction ID
• The accepted offer associated with the transaction ID
• The Seller's user profile information (currently this is looked up within htsApp only.. which is okay for now).
• The Buyer's user profile information (currently this is looked up within htsApp only.. which is okay for now).

The transactionID should have an PUT request that accepts and stores the following information.

• braintree payment receipt
• buyers review of seller
• sellers review of buyer

Also the transactionID should have different states.

• pending (this is the state the transaction sits at before the scheduled meeting time to exchange the item).
• closed (this is the state the transaction will flip to when a Braintree payment receipt has been submitted OR both users have provided a review of each other and verified they exchanged the item (probably used cash)).
• expired (this is the state the transaction will roll over to if the transaction lacks payment receipt OR both reviews form buyer and seller and the meeting date has passed).

It makes sense that the transaction ID is what governs if the item should continue to show up in results or if has been sold and should no longer show up in results. We should consider storing the item for sale in database and changing it's owner the new buyer to maintain an inventory of what each user has bought and sold.

[brozeph]

Schema for transactions:

{
  "transactionId" : "abc123",
  "buyer" : {
    /* open schema - any details submitted by client about buyer */
  },
  "buyerUsername" : "joshua@hashtagsell.com",
  "createdAt" : "2015-05-08T09:24.000Z", // system managed
  "modifiedAt" : "2015-05-08T09:24.000Z", // system managed
  "offer" : {
    /* open schema - should be the `offer` model from `/v1/postings/:postingId/offers/:offerId` resource */
  },
  "offerId" : "123abc",
  "paymentConfirmation" : {
    /* open schema - not required (empty when transaction is pending) - intended to store results from BrainTree */
  },
  "posting" : {
    /* open schema - should be the `posting` model from `/v1/postings/:postingId` resource */
  },
  "postingId" : "987zxy",
  "seller" : {
    /* open schema - any details submitted by client about seller */
  },
  "sellerUsername" : "brad@hashtagsell.com",
  "status" : "pending | completed | expired"
}

[that1guy]

This looks perfect. Next time I open request like this I'll submit suggested schema too. Easier to convey needs.

[brozeph]

Schema for reviews:

{
  "reviewId" : "def456",
  "createdAt" : "2015-05-08T09:24.000Z", // system managed
  "modifiedAt" : "2015-05-08T09:24.000Z", // system managed
  "isBuyer" : true,
  "transactionId" : "abc123",
  "username" : "that1guy",
  "value" : "A++ would buy again!"
}

[brozeph]

Routes and models are now available in the API. Here is high level guide:

To create a transaction in pending state, submit a POST to /v1/transactions with the following fields:

• buyerUsername
• buyer - whatever is supplied will be saved and returned without modification - it is opaque
• sellerUsername
• seller - whatever is supplied will be saved and returned without modification - it is opaque
• offerId - value is validated by looking up offer
• postingId - value is validated by looking up posting

Once the item is sold and transaction details are received, submit a PUT to /v1/transactions/:transactionId with the following fields:

• paymentConfirmation - this will be details from BrainTree

note: The API will automatically change the status to completed when a PUT is performed and the paymentConfirmation body is populated with any data

Once the transaction is completed, complete reviews by performing a POST to /v1/reviews

[that1guy]

Fantastic! Implementation today with Braintree marketplace begins today. Thanks josh!

[that1guy]

Got distracted with million other things. Lets keep this open for a little longer so it stands out. Thanks Josh.

[that1guy]

Okay, tested this and seems to be working as expected.

We've Implemented Venmo for MVP release, so this wont be used heavily until braintree rollout.