{"title":"Secure communication for agentic payments","category":"default","creationDate":1786704993,"content":"

To improve the security of your API request for agentic commerce, add message-level encryption (MLE). For the request to share the shopper's payment credentials with Adyen, you sign the JSON payload with JSON Web Signature (JWS)<\/a> and encrypt the payload with JSON Web Encryption (JWE)<\/a>.<\/p>\n

\n

If your integration uses the Agentic Commerce Protocol (ACP), we recommend that you use HMAC-SHA256 signatures<\/a> (sign the Timestamp<\/code> and the payload) instead. ACP supports this natively.

If you do this, the instructions for JWS and JWE do not apply to you.<\/p>\n<\/div>\n

Requirements<\/h2>\n\n\n\n\n\n\n\n\n
Requirement<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Integration type<\/strong><\/td>\nMake sure that you have one of the following agent platform integrations with Adyen:
User role<\/strong><\/td>\nMake sure that your Adyen credential (API key) has the following user role:
  • Agentic Commerce<\/strong><\/li><\/ul><\/td>\n<\/tr>\n
Key pairs<\/strong><\/td>\nAn RSA key pair for JWS signing (PS512<\/code>). Keep the private key secure on your platform. Adyen provides the encryption certificate (X.509). Do not reuse keys across integrations.<\/td>\n<\/tr>\n
Setup steps<\/strong><\/td>\nBefore you begin, reach out to your Adyen Account Manager or our Support Team<\/a> for the following: