| PUT | /eCommerce/Orders/Payments | ||
|---|---|---|---|
| PUT | /eCommerce/Orders/{OrderId}/Payments/{PaymentUnid} |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| OrderId | path | int | No | |
| PaymentUnid | path | Guid | No | |
| PaymentType | body | byte | No | |
| Amount | body | decimal | No | |
| OrderAmount | body | decimal? | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No | |
| PaymentId | form | int? | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
PUT /eCommerce/Orders/Payments HTTP/1.1
Host: 10.10.0.107
Accept: application/json
Content-Type: application/json
Content-Length: length
{"OrderId":0,"PaymentUnid":"00000000000000000000000000000000","PaymentType":0,"Amount":0,"OrderAmount":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length
{"ResponseStatus":{"ErrorCode":"String","Message":"String","StackTrace":"String","Errors":[{"ErrorCode":"String","FieldName":"String","Message":"String","Meta":{"String":"String"}}],"Meta":{"String":"String"}},"PaymentId":0}