Create a communication session
Establishes a secure communication session between the Mobile SDK and the Adyen payments platform, through mutual authentication. The request sends a setup token that identifies the SDK and the device. The response returns a session token that the SDK can use to authenticate responses received from the Adyen payments platform.
The API key to authenticate API requests.
The unique identifier of your merchant account.
The setup token provided by the SDK in a Mobile solution for in-person payments.
- When using the Android SDK, obtain the token through the
MerchantAuthenticationService.authenticate(setupToken)callback ofAuthenticationService. - When using the iOS SDK, obtain the token through the
PaymentServiceDelegate.register(with:)callback ofPaymentServiceDelegate.
The reference of the store that you want to process transactions for. Do not include this parameter if your account structure uses merchant accounts as stores, or if you are a registered payment facilitator.
The details of the sub-merchant that you want to process transactions for.Required if you are a registered payment facilitator. Do not include this parameter if you are not a payment facilitator.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
201 - OK
The request has succeeded.
400 - Bad request
Validation failed.
401 - Unauthorized
Authentication required.
422 - Unprocessable entity
Session request could not be processed.
500
Internal server error.