Basic Session Request

info

The Embedded Checkout Flow is a simple and secure way to accept payments directly on your website.
It allows you to integrate Adyen's checkout component, which securely handles all sensitive payment information.
This way, you can offer a seamless payment experience without needing to manage PCI compliance yourself.

After the flow, you can find the basic request example below.
This example includes all of the required fields for a basic checkout request.

Flow

Test URL

Your initial request will be made to the following URL:

https://checkout-api.staging.straumur.is/api/v1/sessioncheckout

This call will create the session and return the client key and session data that you will pass to your frontend component.

Request Example

{
  "terminalIdentifier": "1adfe4a1",
  "amount": "48900",
  "currency": "ISK",
  "reference": "9990QQAZ1221",
  "channel": "Web",
  "origin": "https://www.your-ecommerce-website.com",
  "threeDsReturnUrl": "https://your-ecommerce-website.com/straumur_redirect"
}

info

Amount in request should be specified in minor units.

For more information on minor units, please see Currencies and Minor Units.

Request Required Fields

This table outlines the request required fields with their corresponding types, descriptions, examples, and any length constraints.

Field	Type	Required	Description	Example	Min Length	Max Length
terminalIdentifier	String	Required	The terminal identifier to uniquely identify the terminal. You can find your Terminal Identifier in the Merchant Portal. Open Section "Terminals" > Select Terminal to open Details panel > Copy Terminal Identifier	1adfe4a1	12	12
amount	Integer	Required	The amount to be charged in minor units. Must end in 00 for ISK.	48900	-	-
currency	String	Required	The three-character ISO currency code.	ISK	3	3
reference	String	Required	The reference to uniquely identify a payment.	9990QQAZ1221	-	-
channel	String	Required	Location where the payment originates from. Accepted Values: Web, Android, IOS	Web	-	-
origin	String	Required	Location where the payment originates from. This must be in line with the channel provided.	https://www.your-ecommerce-website.com	-	-
threeDsReturnUrl	String	Required	Location where the shopper should be redirected back to if 3DS occurs as a redirect. This must be in line with the channel provided.	https://www.your-ecommerce-website.com/straumur_additional_details	-	-

Response

{
  "checkoutReference": "92v76ahtugvewe1cewijsfrsygazatjki6a5z7lskcfoxb3w9o",
  "clientKey": "test_BR7ZXH7DGJENFMVENRXFFHNWSEYCDNA6",
  "responseDateTime": "2024-09-04T10:35:18.343503Z",
  "responseIdentifier": "e4ce3367-4d2b-4398-ad4e-06bcee650104",
  "session": {
    "id": "CSBB1CFEEFAFE4D4AD",
    "sessionData": "Ab02b4c0!BQAB...Dssg=="
  }
}

info

After a Checkout Request has been made it is possible to check the status of the payment process by sending a Checkout Status Request.

Response Fields

This table outlines the response fields with their corresponding types, descriptions, examples, and any length constraints.

Field	Type	Description	Example
checkoutReference	String	The reference to uniquely identify the hosted checkout session.	faf984ad76db792v76ahtugvewe1cewijsfrsygaz
clientKey	String	The client key you need to pass to your frontend component	test_BR7ZXH7ABEHHR11FAZSG21GYG1A6
responseDateTime	String	The date and time when the response was generated.	2025-01-04T09:50:14.343503Z
responseIdentifier	String	The unique identifier for the response.	7be7111c-2e8e-4cd4-a5ba-f15bdfd177c1
session	Object	Object containing the session data used in the checkout component.

Session Fields

Field	Required	Description	Example
id	Required	The unique identifier of the created session. You can use this value to query session status.	CSBB1CFEEFAFE4D4AD
sessionData	Required	The payment session data you need to pass to your frontend component.	Ab02b4c0!BQAB...

Error Response

Our error responses are standardised. Please see Errors.

You can also find a detailed overview of our HTTP Status Codes.