@agent-cards/sdk 0.23.25 → 0.23.26

package/dist/client.d.ts

@@ -499,6 +499,17 @@ export declare const SUPPORTED_REGISTRY_FEATURES: readonly string[];
  * amount, so the agent's pair, above zero, is the one the cardholder approves.
  * Served on the same terms: only to a build that lists it, for a company Agentcard turned APS on for.
  *
+ * `nexi_checkout_pay`: the card payment Nexi Checkout's card frame (checkout.dibspayment.eu/v1/, formerly Nets
+ * Easy) posts as JSON to its own pay endpoint, https://checkout.dibspayment.eu/api/v1/pay (the test host for a
+ * test row), under the merchant's checkout key and the payment's id. This build pauses only the card form's own
+ * body at that exact URL ("save my card", "remember me" and a card fee are refused at the pause, and the frame's
+ * card lookup while the number is typed continues untouched); the cardholder's device reads Nexi's own record of the
+ * payment and sends the card through the checkout relay, and the frame gets Nexi's answer as payment-core's judge
+ * rebuilt it: the payment done, or Nexi's 3-D Secure step, which the frame then runs in the agent's browser. The
+ * body names the payment's amount in minor units but not its currency, so the agent's pair, above zero, is the one
+ * the cardholder approves, and the API holds its amount to the body's. Served on the same terms: only to a build
+ * that lists it, for a company Agentcard turned Nexi Checkout on for.
+ *
  * `barion_hosted_payment_page`: Barion's Smart Gateway, whose card-free link
  * (secure.barion.com/Pay?Id=<payment id>, a plain GET the merchant's redirect or script sends
  * the buyer to) this build pauses for the cardholder's device by its exact link (hosted-entry.ts),
@@ -506,6 +517,30 @@ export declare const SUPPORTED_REGISTRY_FEATURES: readonly string[];
  * send (pre-claim.ts, barion.ts). Served on the same terms as Przelewy24's: only to a build that
  * lists it, for a company Agentcard turned Barion on for.
  *
+ * `paymob_checkout_pay`: the card payment Paymob's own checkout sends, from Unified Checkout
+ * (<country>.checkout.paymob.com) or from the Pixel card frame a merchant's page embeds, as JSON to
+ * https://<accept|uae|ksa|oman>.paymob.com/api/acceptance/payments/pay. This build pauses only the
+ * card form's own payment at that exact URL: a card Paymob saved, a payment that keeps the card,
+ * pays in installments, splits, converts or names a Paymob account, and a payment key that enrolls
+ * a subscription or names no amount are refused at the pause, and another method's payment with no
+ * card (a wallet, Apple Pay, cash) continues to Paymob untouched. The cardholder's device sends the
+ * payment to Paymob itself with the real card, and the checkout gets Paymob's answer as payment-core's
+ * judge rebuilt it. The payment key names the amount and currency, so an agent pair is optional and
+ * the API holds one to the key's figure. Served on the same terms: only to a build that lists it, for
+ * a company Agentcard turned Paymob on for.
+ *
+ * `payu_latam_webcheckout_card`: the card submit PayU Latam's WebCheckout page posts to
+ * checkout.payulatam.com/ppp-web-gateway-payu/checkout/submit/<country>/credit_card/<key>
+ * (sandbox.checkout.payulatam.com on PayU's test platform). This build pauses only the card form's
+ * own submit at that exact URL (a ticked save-my-card box, a card PayU saved, installments and a
+ * test order on the live host are refused at the pause); the cardholder's device writes the real
+ * card into the paused body and sends it to PayU itself, and the page gets PayU's answer as
+ * payment-core's judge reads it. The page's BIN lookup (checkout/card_info/) carries the typed
+ * placeholder and continues, as the page needs its answer to fill the card's facts. The submit's
+ * copy of the order is the browser's, so the agent's pair, above zero, is the one the cardholder
+ * approves, which the API holds to the order PayU reads back. Served on the same terms: only to a
+ * build that lists it, for a company Agentcard turned PayU Latam on for.
+ *
  * The list itself is capabilities.json, sorted, one per line (scripts/generate-capabilities.mjs).
  */
 export declare const SUPPORTED_CAPABILITIES: readonly string[];

package/dist/client.js

@@ -492,6 +492,17 @@ export const SUPPORTED_REGISTRY_FEATURES = ['card_fields', 'checkout_sessions'];
  * amount, so the agent's pair, above zero, is the one the cardholder approves.
  * Served on the same terms: only to a build that lists it, for a company Agentcard turned APS on for.
  *
+ * `nexi_checkout_pay`: the card payment Nexi Checkout's card frame (checkout.dibspayment.eu/v1/, formerly Nets
+ * Easy) posts as JSON to its own pay endpoint, https://checkout.dibspayment.eu/api/v1/pay (the test host for a
+ * test row), under the merchant's checkout key and the payment's id. This build pauses only the card form's own
+ * body at that exact URL ("save my card", "remember me" and a card fee are refused at the pause, and the frame's
+ * card lookup while the number is typed continues untouched); the cardholder's device reads Nexi's own record of the
+ * payment and sends the card through the checkout relay, and the frame gets Nexi's answer as payment-core's judge
+ * rebuilt it: the payment done, or Nexi's 3-D Secure step, which the frame then runs in the agent's browser. The
+ * body names the payment's amount in minor units but not its currency, so the agent's pair, above zero, is the one
+ * the cardholder approves, and the API holds its amount to the body's. Served on the same terms: only to a build
+ * that lists it, for a company Agentcard turned Nexi Checkout on for.
+ *
  * `barion_hosted_payment_page`: Barion's Smart Gateway, whose card-free link
  * (secure.barion.com/Pay?Id=<payment id>, a plain GET the merchant's redirect or script sends
  * the buyer to) this build pauses for the cardholder's device by its exact link (hosted-entry.ts),
@@ -499,6 +510,30 @@ export const SUPPORTED_REGISTRY_FEATURES = ['card_fields', 'checkout_sessions'];
  * send (pre-claim.ts, barion.ts). Served on the same terms as Przelewy24's: only to a build that
  * lists it, for a company Agentcard turned Barion on for.
  *
+ * `paymob_checkout_pay`: the card payment Paymob's own checkout sends, from Unified Checkout
+ * (<country>.checkout.paymob.com) or from the Pixel card frame a merchant's page embeds, as JSON to
+ * https://<accept|uae|ksa|oman>.paymob.com/api/acceptance/payments/pay. This build pauses only the
+ * card form's own payment at that exact URL: a card Paymob saved, a payment that keeps the card,
+ * pays in installments, splits, converts or names a Paymob account, and a payment key that enrolls
+ * a subscription or names no amount are refused at the pause, and another method's payment with no
+ * card (a wallet, Apple Pay, cash) continues to Paymob untouched. The cardholder's device sends the
+ * payment to Paymob itself with the real card, and the checkout gets Paymob's answer as payment-core's
+ * judge rebuilt it. The payment key names the amount and currency, so an agent pair is optional and
+ * the API holds one to the key's figure. Served on the same terms: only to a build that lists it, for
+ * a company Agentcard turned Paymob on for.
+ *
+ * `payu_latam_webcheckout_card`: the card submit PayU Latam's WebCheckout page posts to
+ * checkout.payulatam.com/ppp-web-gateway-payu/checkout/submit/<country>/credit_card/<key>
+ * (sandbox.checkout.payulatam.com on PayU's test platform). This build pauses only the card form's
+ * own submit at that exact URL (a ticked save-my-card box, a card PayU saved, installments and a
+ * test order on the live host are refused at the pause); the cardholder's device writes the real
+ * card into the paused body and sends it to PayU itself, and the page gets PayU's answer as
+ * payment-core's judge reads it. The page's BIN lookup (checkout/card_info/) carries the typed
+ * placeholder and continues, as the page needs its answer to fill the card's facts. The submit's
+ * copy of the order is the browser's, so the agent's pair, above zero, is the one the cardholder
+ * approves, which the API holds to the order PayU reads back. Served on the same terms: only to a
+ * build that lists it, for a company Agentcard turned PayU Latam on for.
+ *
  * The list itself is capabilities.json, sorted, one per line (scripts/generate-capabilities.mjs).
  */
 export const SUPPORTED_CAPABILITIES = DECLARED_CAPABILITIES;
@@ -602,6 +637,8 @@ export const SUPPORTED_CAPABILITIES = DECLARED_CAPABILITIES;
  * create route's refusal, not in this comment.
  */
 const REVOLUT_PSP = 'revolut';
+/** Nexi Checkout's card payment names the payment's amount in minor units but not its currency, as Revolut's does. */
+const NEXI_CHECKOUT_PSP = 'nexi_checkout';
 const AGENT_AMOUNT_PROCESSORS = AGENT_AMOUNT.processors;
 /** The ones a zero amount is refused for, like a missing one (authorize()). */
 const ABOVE_ZERO_PROCESSORS = AGENT_AMOUNT.aboveZero;
@@ -888,7 +925,7 @@ export class AmountRequiredError extends Error {
     constructor(psp) {
         const processor = PROCESSOR_NAMES[psp] ?? psp;
         // A Payrexx card request names the frame's total, but the merchant's page charges its own total after the token.
-        const lacks = psp === REVOLUT_PSP ? 'names its amount but not its currency'
+        const lacks = psp === REVOLUT_PSP || psp === NEXI_CHECKOUT_PSP ? 'names its amount but not its currency'
             : psp === PAYREXX_PSP ? "only mints a token the merchant's page charges later"
                 : psp === TAP_PAYMENTS_PSP ? 'does not decide the amount charged' : 'names no amount';
         // "An Omise payment request", "A Clover payment request": the article follows the name's first letter.