Additional Details
POST /payment/details
Test URL
The payment details request will be made to the following URL:
https://checkout-api.staging.straumur.is/api/v1/payment/details
This call will confirm the payment request with the necessary 3DS result.
On live, use the same path on https://greidslugatt.straumur.is. Headers, request and response are identical. See Live environment.
Redirect Result
You need to take the redirect result you receive appended to your returnUrl.
If the returnUrl provided was https://your-store.com/straumur_additional_details, then the user would be redirected to https://your-store.com/straumur_additional_details?redirectResult=Ab02b4c0....
If the user confirmed 3DS but was not redirected back to your returnUrl (e.g., the user closed the tab or there was a redirection issue), you will not receive the redirectResult parameter. In this case, the payment may still be completed. Wait for the webhook notification to confirm the payment status.
Request Example
{
"checkoutReference": "fp3afbpdtsw3jw1br7lxi0lcd4gnfq6wxdrueeq2cwlks5vahj",
"redirectResult": "Ab02b4c0...",
}
Request Body Fields
| Field | Type | Required | Description | Example | Min Length | Max Length |
|---|---|---|---|---|---|---|
| checkoutReference | String | Required | The reference to uniquely identify the checkout session. You receive this for the initial request. | fp3afbpdtsw3jw1br7lxi0lcd4gnfq6wxdrueeq2cwlks5vahj | ||
| redirectResult | String | Required | The result of the 3DS redirect. You will receive this as a query parameter on the redirect URL provided in the initial request. | Ab02b4c0... | - | - |
Example - Authorised Response
Status Authorised means that the transaction has gone through.
You will also receive a webhook regarding this transaction with additional details.
{
"payfacReference": "T3WJMB84TFCCJ875",
"reference": "9990QQAZ1221",
"resultCode": "Authorised",
"responseDateTime": "2025-01-04T09:50:14.343503Z",
"responseIdentifier": "e3605f81-6b09-4ce1-83ad-5a8d49f3cd44"
}
Response Fields
This table outlines the response fields with their corresponding types, descriptions and examples.
| Field | Type | Description | Example |
|---|---|---|---|
| payfacReference | String | Straumur reference to uniquely identify a payment. | T3WJMB84TFCCJ875 |
| reference | String | Merchant reference to uniquely identify a payment. | 9990QQAZ1221 |
| resultCode | String | The status of the payment. | Authorised |
| responseDateTime | String | The date and time when the response was generated. | 2024-09-04T09:50:14.343503Z |
| responseIdentifier | String | The unique identifier for the response. | 7be7111c-2e8e-4cd4-a5ba-f15bdfd177c1 |
Possible Result Code Values
| Result Code | Description |
|---|---|
| Authorised | The payment was successfully authorised. |
| Cancelled | The payment was cancelled (by either the shopper or your own system) before processing was completed. |
| Error | There was an error when the payment was being processed. |
| Refused | The payment was refused. |
Error Response
Our error responses are standardised. Please see Errors.
You can also find a detailed overview of our HTTP Status Codes.