Can I issue a partial refund with the XPay API?

Yes. POST /operations/{operationId}/refunds accepts a refund amount in the request body, so an agent can refund less than the original capture if the merchant policy allows it. Call GET /operations/{operationId}/actions first to confirm refund is valid for the current operation state.

What payment methods does the Nexi XPay API support?

The hosted payment page covers cards (Visa, Mastercard, and the Italian PagoBancomat circuit), Google Pay, and pay-by-link flows. GET /payment_methods returns the list configured for a specific merchant - what is offered to the shopper depends on contract terms with Nexi.

How do I create a pay-by-link order through Jentic?

Search Jentic for 'create a pay-by-link order on nexi xpay', load the POST /v2/orders/paybylink schema, and execute with the amount, currency, and expiry. Jentic injects the X-Api-Key header automatically and the response includes the URL to send to the customer.

Does the XPay API support PSD2 strong customer authentication?

Yes. The hosted payment page handles 3D Secure 2 challenges and SCA exemptions in line with PSD2, so merchants do not have to embed the challenge flow themselves. The API simply returns the order status once the cardholder completes authentication.

Can I limit what my agent is allowed to do with the Nexi XPay API?

Yes. Because you run Jentic One yourself, your own rules decide which XPay operations and credentials the agent may use, so you can allow read-only calls like GET /orders/{orderId} and GET /operations/{operationId}/actions while withholding the money-moving ones. Refunds, captures, and cancels on /operations/{operationId} are not available to the agent unless you deliberately add them. Since XPay puts the operation id in the URL path, a rule can even pin the agent to actions on a single operation. Your merchant key stays with your instance and is injected at execution time, never entering the agent's prompt or logs.