add end-point to payment API for adding payments later in the process

[hsideback]

In order to allow payments from elixir, pay, samport, etc to be added to the payment service, even if the initial payment request wasn't made through the payment api, we need an additional method + end-point.

My suggestion is that we add POST /payments/{operation}, which similar to POST /payments/{id}/{operation}, would add an operation to a payment.

The difference is that we don't know when we add e.g. the acquisition operation if the parent payment object exist or not. The end-point would try to match the operation to an existing payment, and if it exist, would add it to that payment. If it does not exist, it would create a new parent object and add the operation to that object.

[bowens-bambora]

Can you give an example of an operation?

[hsideback]

Authorise (implicit in create)
Capture
Settle
Refund
Charge-back

Skickat från Outlook Mobilehttps://aka.ms/qtex0l
Henrik Sidebäck
Netlight Consulting
+46 (0)733-814104tel:+46%20733-814104

On Tue, Feb 23, 2016 at 10:06 AM -0800, "Brent Owens" <notifications@github.commailto:notifications@github.com> wrote:

Can you give an example of an operation?

Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-187820927.