Paytrail is automatable through its payment API

Paytrail is automatable today through the Payment API at services.paytrail.com. The API reference says every call is signed with HMAC using SHA-256 or SHA-512. The signature header is built from the lowercase checkout- headers in alphabetical order, plus the JSON body. The merchant ID goes in checkout-account. The reference publishes test merchant ID and secret key values used to calculate the signature. POST /payments creates a payment and returns a JSON object with a transaction ID and payment providers. GET /payments/{transactionId} returns the payment. POST /payments/{transactionId}/refund refunds a payment. If the merchant sets callback URLs, Paytrail calls them with HTTP GET, and the merchant must check the signature. Paytrail also documents an official MCP server at https://mcp.paytrail.com/mcp with Streamable HTTP and OAuth 2.0 PKCE against AWS Cognito. The setup page says MCP access is turned on under Users in the merchant panel, and that the assistant does not see the merchant password. A session lasts 14 days from the latest request. The technical reference names list_merchants, create_payment, get_payment, and list_payment_providers. Amounts are integers in cents. The MCP docs site name in the page source includes a BETA tag. The English agentic-commerce page also describes creating many payments from an Excel file. That action is not named in the technical reference. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 7. The MCP server scores 5 because the docs label it beta and the named tools are a narrow slice of the Payment API. The API is the best path because it documents refunds and signed callbacks that those four tools do not.

Best path today: api · Overall automatability: 7/10