PATCH /registeredDevices/{deviceId}/associations

Completes an association between a user's registered SCA device and an Adyen resource. For example, you can associate an SCA device with additional business accounts or Adyen-issued cards.

To complete the association, this endpoint validates the authentication data of the registered device.

Servers

Path parameters

Name Type Required Description
deviceId String Yes

The unique identifier of the SCA device that you are associating with a resource.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
type String Yes

The type of resource that you are associating with the SCA device.

Possible value: PaymentInstrument

Valid values:

  • "PaymentInstrument"
ids[] Array Yes

The list of unique identifiers of the resources that you are associating with the SCA device.

Maximum: 5 strings.

strongCustomerAuthentication Object Yes

Contains authentication information required to associate the resource with the SCA device.

strongCustomerAuthentication.sdkOutput String Yes

A base64-encoded block with the data required to authenticate the request. You obtain this information by using our authentication SDK.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.