carrier_billing_checkout_1-step_model_and_purchases_list

[PedroDiez]

PR

PR to include 1-step payment and List of Purchases:

• NEW Endpoint to manage 1-step payment -> POST /purchases/{purchase_id}/payment
• NEW Endpoint to fetch a list of purchases -> GET /purchases

Additionally, related Issues
Issue 54

• Indication of phone number in Payment Request, as optional input. This does not preclude to always indicate it, if preferred by an specific implementation

Issue 56

• payment_creation_date and payment_date added in GET endpoints and also notification endpoint

Issue 58

• Removing pattern from "status" field as being an integer and pattern applies for string fields.

Comm PR 171

• Input/Output parameters aligned to camelCase

Comm Guidelines

• Aligment for pagination and indication of x-correlator (Not a MUST to indicate however we want to do so, as a guidance for devs)

Documentation will be updated after yaml agreement.

NOT HANDLED IN THIS PR

Points out of scope of this PR: (To manage in a future PR, just to align at the same level with carrier billing payment)

• Notifications thread:

camaraproject/WorkingGroups#156
camaraproject/WorkingGroups#173

[PedroDiez]

NOTE: I will take advantage of guidelines update about format used for API input/output params.
To align the proposal with them regarding the use of camelCase: camaraproject/WorkingGroups#171

[PedroDiez]

Now Ready for review. Aligned at functionality level with Carrier Billing Payment v0.7.0

NOTE that notificationAuthToken is only manage in createPurchase. Reason for that is to ensure its confidentiality as much as possible, so no need to return in GET endpoints as the ONLY use for it is in the notifications callback endpoint

[bigludo7]

Look good for me !