| POST | /mobile/payments/details | Sends a request to provide payment details to the integrated payment provider. |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PaymentId | query | string | Yes | Payment Id (GUID). |
| Body | body | DetailsRequestBody | Yes | Contains body data in regard with the payment method selected from the client. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Version | form | integer | No | Api version |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| PaymentData | form | string | Yes | Contains encrypted payment data in regard with the payment method selected from the client. |
| Details | form | Dictionary<string, string> | Yes | Additional details. |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| Data | form | string | No |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| ResponseStatus | form | ResponseStatus | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .jsv suffix or ?format=jsv
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /mobile/payments/details HTTP/1.1
Host: api.4spaces.io
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length
{
paymentId: 00000000000000000000000000000000,
body:
{
paymentData: String,
details:
{
String: String
}
},
version: 0
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length
{
data: String,
responseStatus:
{
errorCode: String,
message: String,
stackTrace: String,
errors:
[
{
errorCode: String,
fieldName: String,
message: String,
meta:
{
String: String
}
}
],
meta:
{
String: String
}
}
}