PASAR API
Requires a Nexi merchant contract; each call carries the terminal's X-Api-Key header.
View docs ↗ More Payments APIs# Nexi XPay ~ card & e-commerce payment gateway needs an API key. # No single public base URL ~ start from the docs: # https://developer.nexi.it/en/api
I'm integrating a Italy API into my app. API: Nexi XPay ~ card & e-commerce payment gateway Provider: Nexi Auth: requires an API key (sign up: https://developer.nexi.it/en/api) Pricing: paid Important note: Requires a Nexi merchant contract; each call carries the terminal's X-Api-Key header. Source: Nexi (https://developer.nexi.it/en/api) Source type: Provider API or developer docs Endpoint type: Docs-first integration Integration difficulty: Needs API key Last checked: 2026-07-05 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.