@agent-cards/sdk 0.23.21 → 0.23.23

package/dist/creditguard.generated.js

@@ -1,6 +1,6 @@
 // @ts-nocheck
 // Generated from @agent-cards/payment-core. Do not edit.
-// artifact-sha256: 0110d9fe2e862aad2c1191c5927ebb98dcc4be9905554ed46e18719a0bad05fb
+// artifact-sha256: 24cac2580feefe7d273b89de8e5b84e744e561fd258252f98008801750370460
 // src/creditguard.js
 var CREDITGUARD_PPS_HOSTS = Object.freeze(["pps.creditguard.co.il", "pps2.creditguard.co.il", "ppsuat.creditguard.co.il"]);
 var CREDITGUARD_SANDBOX_HOST = "ppsuat.creditguard.co.il";
@@ -707,6 +707,7 @@ var THREE_DS_INIT_KEYS = Object.freeze([
     "cvv",
     "isGooglePayTxn",
     "isPayboxTxn",
+    "recaptchaValue",
     "useDcc",
     "acsWindowSize",
     "browserColorDepth",
@@ -837,6 +838,7 @@ function creditguardDeviceThreeDSInitRequest(processUrl, card, options = {}) {
         cvv: parts.cvc,
         isGooglePayTxn: false,
         isPayboxTxn: false,
+        recaptchaValue: "",
         useDcc: false,
         acsWindowSize: "4",
         browserColorDepth: browser.colorDepth,
@@ -887,7 +889,7 @@ function deviceStepBodyRefusal(step, txId, body) {
         return "dcc";
     if (value.txId !== txId)
         return "txid_mismatch";
-    if (value.acsWindowSize !== "4" || value.browserHeader !== BROWSER_HEADER || value.browserJavascriptEnabled !== true)
+    if (value.recaptchaValue !== "" || value.acsWindowSize !== "4" || value.browserHeader !== BROWSER_HEADER || value.browserJavascriptEnabled !== true)
         return "malformed_body";
     try {
         deviceBrowser({

package/dist/cse-body.js

@@ -4,6 +4,8 @@ import { substituteEncryptedFields } from './substitute.js';
 import { substituteMerchantHostedBody } from './merchant-hosted.js';
 import { fiservCapturePinId, isFiservCaptureHost, substituteFiservEnvelope } from './fiserv.js';
 import { substituteVerifoneBody } from './verifone.js';
+import { isToastHost } from './toast.generated.js';
+import { substituteToastCardData } from './toast-seal.generated.js';
 /**
  * The cse continuation: the paused body with the vault's ciphertext in place
  * of the dummy blobs. The adapters send it as postData ALONE. Chromium
@@ -44,6 +46,15 @@ export function cseBody(body, replay, url, preparation) {
     }
     if (isFiservCaptureHost(url))
         throw new Error('Refusing to substitute: a Fiserv capture continues only through a prepared Fiserv approval.');
+    // A request on Toast's payments host takes only Toast's own swap: the device's sealed card written over
+    // the paused card.cardData and no other byte, refused unless the paused body is still the frame's guest
+    // card request and the card is sealed under the key payment-core pins (toast-seal.js substituteToastCardData).
+    if (isToastHost(url)) {
+        if (replay.kind !== undefined || replay.substitutions.at !== 'card' || (replay.substitutions.remove ?? []).length > 0) {
+            throw new Error('Refusing to substitute: the paused request is not the Toast card request the cardholder approved.');
+        }
+        return substituteToastCardData(url, body, replay.substitutions.fields);
+    }
     // A merchant-hosted approval is written into the LIVE paused body, which must
     // still be the body the API checked at create (merchant-hosted.ts).
     if (replay.kind === 'merchant_hosted')

package/dist/ebanx.d.ts

@@ -75,7 +75,7 @@ export declare class EbanxFollowUps {
     stop(): void;
     /**
      * The approval the remembered token request went under, or null when none is remembered. The gate sends nothing
-     * unless the checkout's own state names this same approval (pre-claim.ts ebanxMaySend).
+     * unless the checkout's own state names this same approval (pre-claim.ts followUpMaySend).
      */
     get authorizationId(): string | null;
     /**

package/dist/ebanx.js

@@ -108,7 +108,7 @@ export class EbanxFollowUps {
     stop() { this.stopped = true; }
     /**
      * The approval the remembered token request went under, or null when none is remembered. The gate sends nothing
-     * unless the checkout's own state names this same approval (pre-claim.ts ebanxMaySend).
+     * unless the checkout's own state names this same approval (pre-claim.ts followUpMaySend).
      */
     get authorizationId() { return this.parent?.authorizationId ?? null; }
     /**

package/dist/eximbay.d.ts

@@ -0,0 +1,46 @@
+/**
+ * Eximbay's payment window (secureapi.eximbay.com, the Korean gateway that takes foreign cards for Korean merchants),
+ * as this SDK reads it.
+ *
+ * The merchant's page posts a signed entry form, top-level or into a window it opens, to
+ * https://secureapi.eximbay.com/Gateway/BasicProcessor.krp (Eximbay's test host for a test merchant), and Eximbay
+ * answers with a page that posts itself, with the session's paramkey, into its window. That entry carries no card,
+ * and it is the one request this SDK pauses: the cardholder's device repeats it over the end-to-end TLS relay and
+ * fills the card into the window Eximbay returns to it (payment-core processors/eximbay.js). Everything else the
+ * agent's browser posts to Eximbay follows the entry and leads to a card: the step that opens the window
+ * (/Gateway/BasicProcessor/230/NewGlobalStep1.jsp), the window's amount query and card lookup, which carries the
+ * card's first eight digits (controll/checkApprvJson.do, controll/checkCardBin.do), its card post
+ * (controll/checkApprv.jsp) and its other posts. This SDK aborts every one of them in a page it watches, so a
+ * placeholder card never reaches Eximbay from one. attachToCdp watches a window the merchant's page opens once it has
+ * armed that window. Eximbay's popup integration opens the window and posts the entry into it at once, so that entry
+ * can leave before the window is armed; the window's next post, the step, is then aborted like any other, and the
+ * checkout reads unsupported. attachToPlaywright routes the page alone, never a window it opens.
+ *
+ * EXIMBAY_HOSTS is payment-core's EXIMBAY_HOSTS, and isEximbayEntry takes the URLs payment-core's isEximbayEntryUrl
+ * takes; eximbay.test.mjs pins both to payment-core.
+ */
+export declare const EXIMBAY_PSP = "eximbay";
+/** The dark-launch capability the API serves Eximbay's recognizer behind (payment-core definitions.js). */
+export declare const EXIMBAY_CAPABILITY = "eximbay_hosted_payment_page";
+/** The live host and Eximbay's test host, which serves the same window for a test merchant. */
+export declare const EXIMBAY_HOSTS: readonly string[];
+/** Whether this URL is on one of Eximbay's two hosts. */
+export declare function isEximbayHost(url: string): boolean;
+/**
+ * The only request on Eximbay's hosts that is the merchant's entry: a POST to the entry path, written exactly as a
+ * browser posts a form to it, with no port, query or fragment (payment-core isEximbayEntryUrl takes those two strings
+ * only). The entry the SDK pauses; every other POST there is aborted.
+ */
+export declare function isEximbayEntry(url: string, method: string): boolean;
+/** The entry URL on the same Eximbay host, which the registry recognizes when this build is armed for Eximbay, or null. */
+export declare function eximbayEntryUrl(url: string): string | null;
+/**
+ * Whether an adapter must hand this request to the pre-claim gates: it is on an Eximbay host and this build's registry
+ * serves Eximbay's entry there. The step, the window's lookups and its card post are not the entry, so the registry's
+ * card-request test does not name them; the CDP adapter still pauses them through the recognizer's host pattern, and
+ * attachToPlaywright's route predicate asks this, so both adapters show the gates every request to Eximbay once
+ * Eximbay is armed.
+ */
+export declare function isArmedEximbayUrl(vault: {
+    isCardRequest(url: string, method?: string): boolean;
+}, url: string): boolean;

package/dist/eximbay.js

@@ -0,0 +1,69 @@
+/**
+ * Eximbay's payment window (secureapi.eximbay.com, the Korean gateway that takes foreign cards for Korean merchants),
+ * as this SDK reads it.
+ *
+ * The merchant's page posts a signed entry form, top-level or into a window it opens, to
+ * https://secureapi.eximbay.com/Gateway/BasicProcessor.krp (Eximbay's test host for a test merchant), and Eximbay
+ * answers with a page that posts itself, with the session's paramkey, into its window. That entry carries no card,
+ * and it is the one request this SDK pauses: the cardholder's device repeats it over the end-to-end TLS relay and
+ * fills the card into the window Eximbay returns to it (payment-core processors/eximbay.js). Everything else the
+ * agent's browser posts to Eximbay follows the entry and leads to a card: the step that opens the window
+ * (/Gateway/BasicProcessor/230/NewGlobalStep1.jsp), the window's amount query and card lookup, which carries the
+ * card's first eight digits (controll/checkApprvJson.do, controll/checkCardBin.do), its card post
+ * (controll/checkApprv.jsp) and its other posts. This SDK aborts every one of them in a page it watches, so a
+ * placeholder card never reaches Eximbay from one. attachToCdp watches a window the merchant's page opens once it has
+ * armed that window. Eximbay's popup integration opens the window and posts the entry into it at once, so that entry
+ * can leave before the window is armed; the window's next post, the step, is then aborted like any other, and the
+ * checkout reads unsupported. attachToPlaywright routes the page alone, never a window it opens.
+ *
+ * EXIMBAY_HOSTS is payment-core's EXIMBAY_HOSTS, and isEximbayEntry takes the URLs payment-core's isEximbayEntryUrl
+ * takes; eximbay.test.mjs pins both to payment-core.
+ */
+export const EXIMBAY_PSP = 'eximbay';
+/** The dark-launch capability the API serves Eximbay's recognizer behind (payment-core definitions.js). */
+export const EXIMBAY_CAPABILITY = 'eximbay_hosted_payment_page';
+/** The live host and Eximbay's test host, which serves the same window for a test merchant. */
+export const EXIMBAY_HOSTS = Object.freeze(['secureapi.eximbay.com', 'secureapi.test.eximbay.com']);
+const ENTRY_PATH = '/Gateway/BasicProcessor.krp';
+/** The Eximbay host a URL is on (https, no credentials, any port, any letter case, a trailing dot or not), or null. */
+function eximbayHost(raw) {
+    let url;
+    try {
+        url = new URL(raw);
+    }
+    catch {
+        return null;
+    }
+    if (url.protocol !== 'https:' || url.username || url.password)
+        return null;
+    const host = url.hostname.toLowerCase().replace(/\.$/, '');
+    return EXIMBAY_HOSTS.includes(host) ? host : null;
+}
+/** Whether this URL is on one of Eximbay's two hosts. */
+export function isEximbayHost(url) {
+    return eximbayHost(url) !== null;
+}
+/**
+ * The only request on Eximbay's hosts that is the merchant's entry: a POST to the entry path, written exactly as a
+ * browser posts a form to it, with no port, query or fragment (payment-core isEximbayEntryUrl takes those two strings
+ * only). The entry the SDK pauses; every other POST there is aborted.
+ */
+export function isEximbayEntry(url, method) {
+    return String(method).toUpperCase() === 'POST' && EXIMBAY_HOSTS.some((host) => url === `https://${host}${ENTRY_PATH}`);
+}
+/** The entry URL on the same Eximbay host, which the registry recognizes when this build is armed for Eximbay, or null. */
+export function eximbayEntryUrl(url) {
+    const host = eximbayHost(url);
+    return host === null ? null : `https://${host}${ENTRY_PATH}`;
+}
+/**
+ * Whether an adapter must hand this request to the pre-claim gates: it is on an Eximbay host and this build's registry
+ * serves Eximbay's entry there. The step, the window's lookups and its card post are not the entry, so the registry's
+ * card-request test does not name them; the CDP adapter still pauses them through the recognizer's host pattern, and
+ * attachToPlaywright's route predicate asks this, so both adapters show the gates every request to Eximbay once
+ * Eximbay is armed.
+ */
+export function isArmedEximbayUrl(vault, url) {
+    const entry = eximbayEntryUrl(url);
+    return entry !== null && vault.isCardRequest(entry, 'POST');
+}

package/dist/hosted-entry.js

@@ -3,7 +3,8 @@
  * processor's own page with a link (a redirect, or a page or frame location set by script) rather than a form post.
  *
  * Such an entry carries no card. The cardholder's device takes it over (mode hosted_form): it makes the processor's
- * own calls for the payment the link names, and the paused navigation gets this SDK's submitted_on_device notice.
+ * own calls for the payment the link names, and the paused navigation gets this SDK's submitted_on_device notice, or,
+ * for a Webpay shop Agentcard reviewed with its return page, that return page (transbank.ts transbankMerchantReturn).
  * A GET recognizer otherwise reads as a card request carried in the URL (Worldpay eProtect's registration), which
  * this build completes only for a grammar it checks, so a hosted page joins this table with the exact link
  * payment-core's resolveRecognizerForUrl admits for it, and nothing else: a URL the table does not admit is never

package/dist/hosted-form.d.ts

@@ -18,6 +18,11 @@
  * completed this payment on their own device, do not resubmit, confirm the
  * order with the merchant. This page says that, for a person and for an
  * agent, and nothing else.
+ *
+ * Webpay is the one hosted page whose merchant hears of a payment only from
+ * the buyer's browser, returning to the merchant's own page with Webpay's
+ * token. A paid Webpay entry is therefore sent to the reviewed shop's return
+ * page instead of this one (transbank.ts transbankMerchantReturn).
  */
 export interface HostedFormSubmittedPageInput {
     /** The approved authorization (`cauth_…`). */

package/dist/hosted-form.js

@@ -18,6 +18,11 @@
  * completed this payment on their own device, do not resubmit, confirm the
  * order with the merchant. This page says that, for a person and for an
  * agent, and nothing else.
+ *
+ * Webpay is the one hosted page whose merchant hears of a payment only from
+ * the buyer's browser, returning to the merchant's own page with Webpay's
+ * token. A paid Webpay entry is therefore sent to the reviewed shop's return
+ * page instead of this one (transbank.ts transbankMerchantReturn).
  */
 /** The outcome word on the page, the header and the JSON: one spelling everywhere. */
 export const HOSTED_FORM_SUBMITTED_OUTCOME = 'submitted_on_device';

package/dist/lifecycle.d.ts

@@ -159,6 +159,7 @@ export declare class CheckoutLifecycle implements CheckoutController {
     private stripeContinuationChecks;
     /** The handoff in progress is WSPay's 3-D Secure step; see handedOff. */
     private wspayChallenge;
+    private heldBeforeHandoff;
     private stripeContinuedReason;
     private approvedPaymentMethod;
     private ownedShopOrderId;
@@ -191,7 +192,8 @@ export declare class CheckoutLifecycle implements CheckoutController {
     preparationFailed(error: CheckoutPreparationError): void;
     isBlocked(): boolean;
     /**
-     * An EBANX send left for the cardholder's device under this attachment's approval (pre-claim.ts ebanxFollowUp). Until
+     * An EBANX or Payrexx send left for the cardholder's device under this attachment's approval (pre-claim.ts ebanxFollowUp,
+     * payrexxFollowUp). Until
      * the returned function runs, once the send's answer reached the page or the send failed, reconcile() and
      * retryAfterMerchantFailure() throw, as they do while a card request is active: a confirm may still pay. The returned
      * function settles the send once, however often it runs.
@@ -200,7 +202,7 @@ export declare class CheckoutLifecycle implements CheckoutController {
     /** Whether a reconcile() is still waiting on the application's merchant resolver; pre-claim.ts claims no EBANX send then. */
     isReconciling(): boolean;
     /**
-     * Whether an EBANX send this attachment claimed is still out (followUpStarted). Both adapters refuse a new card
+     * Whether an EBANX or Payrexx send this attachment claimed is still out (followUpStarted). Both adapters refuse a new card
      * request meanwhile, as they do while an approval is outstanding: a confirm that may pay is never hidden behind
      * another payment's state.
      */
@@ -284,10 +286,13 @@ export declare class CheckoutLifecycle implements CheckoutController {
      * paddle-vgs-pay.ts reasons), or the typed card that EBANX's 3-D Secure calls or
      * its hosted page's confirm send again after the token, when no approved token
      * request on this attachment covers that send or the cardholder's device did not
-     * send it (unsupported_ebanx_card_resend, ebanx.ts): once an approval exists the
+     * send it (unsupported_ebanx_card_resend, ebanx.ts), or the typed card Payrexx's card
+     * frame sends again for a 3-D Secure step when no approved card request on this
+     * attachment covers that send or the cardholder's device did not send it
+     * (unsupported_payrexx_card_resend, payrexx.ts): once an approval exists the
      * state keeps it, and only the hold changes.
      */
-    unsupported(reason?: 'unrecognized_payment_endpoint' | 'merchant_profile_observe' | 'merchant_request_unsupported' | GmoUnsupportedReason | 'microform_unsupported' | 'juspay_request_unsupported' | 'merchant_card_endpoint_not_enabled' | 'merchant_card_endpoint_resend_refused' | 'creditguard_three_d_secure' | 'unsupported_primer_sdk' | 'unsupported_primer_request' | PayrailsUnsupportedReason | ShijiStsUnsupportedReason | 'processor_card_page' | 'unsupported_paypal_hosted_fields' | PaypalCardFormReason | 'unsupported_cybersource_secure_acceptance' | PaddleVgsPayRefusal | 'unsupported_ebanx_card_resend'): void;
+    unsupported(reason?: 'unrecognized_payment_endpoint' | 'merchant_profile_observe' | 'merchant_request_unsupported' | GmoUnsupportedReason | 'microform_unsupported' | 'juspay_request_unsupported' | 'merchant_card_endpoint_not_enabled' | 'merchant_card_endpoint_resend_refused' | 'creditguard_three_d_secure' | 'unsupported_primer_sdk' | 'unsupported_primer_request' | PayrailsUnsupportedReason | ShijiStsUnsupportedReason | 'processor_card_page' | 'unsupported_paypal_hosted_fields' | PaypalCardFormReason | 'unsupported_cybersource_secure_acceptance' | PaddleVgsPayRefusal | 'unsupported_ebanx_card_resend' | 'unsupported_payrexx_card_resend'): void;
     /**
      * A card request that only a prepared checkout pays (an Adyen merchant
      * profile's, or a Fiserv card capture) arrived with no preparation on this

package/dist/lifecycle.js

@@ -57,6 +57,9 @@ export class CheckoutLifecycle {
     stripeContinuationChecks = 0;
     /** The handoff in progress is WSPay's 3-D Secure step; see handedOff. */
     wspayChallenge = false;
+    // Whether the attachment held when the handoff in progress began (prepareHandoff): a hold raised after that, while
+    // the answer was still landing, survives handedOff.
+    heldBeforeHandoff = false;
     // What the continuation that went through confirmed: a payment, or a card save.
     stripeContinuedReason = 'stripe_payment_continued';
     // The payment method a Stripe /v1/payment_methods approval returned: see approvedStripePaymentMethod.
@@ -120,7 +123,8 @@ export class CheckoutLifecycle {
     }
     isBlocked() { return this.held || this.cancelled; }
     /**
-     * An EBANX send left for the cardholder's device under this attachment's approval (pre-claim.ts ebanxFollowUp). Until
+     * An EBANX or Payrexx send left for the cardholder's device under this attachment's approval (pre-claim.ts ebanxFollowUp,
+     * payrexxFollowUp). Until
      * the returned function runs, once the send's answer reached the page or the send failed, reconcile() and
      * retryAfterMerchantFailure() throw, as they do while a card request is active: a confirm may still pay. The returned
      * function settles the send once, however often it runs.
@@ -136,7 +140,7 @@ export class CheckoutLifecycle {
     /** Whether a reconcile() is still waiting on the application's merchant resolver; pre-claim.ts claims no EBANX send then. */
     isReconciling() { return this.reconciliation !== null; }
     /**
-     * Whether an EBANX send this attachment claimed is still out (followUpStarted). Both adapters refuse a new card
+     * Whether an EBANX or Payrexx send this attachment claimed is still out (followUpStarted). Both adapters refuse a new card
      * request meanwhile, as they do while an approval is outstanding: a confirm that may pay is never hidden behind
      * another payment's state.
      */
@@ -283,7 +287,10 @@ export class CheckoutLifecycle {
      * paddle-vgs-pay.ts reasons), or the typed card that EBANX's 3-D Secure calls or
      * its hosted page's confirm send again after the token, when no approved token
      * request on this attachment covers that send or the cardholder's device did not
-     * send it (unsupported_ebanx_card_resend, ebanx.ts): once an approval exists the
+     * send it (unsupported_ebanx_card_resend, ebanx.ts), or the typed card Payrexx's card
+     * frame sends again for a 3-D Secure step when no approved card request on this
+     * attachment covers that send or the cardholder's device did not send it
+     * (unsupported_payrexx_card_resend, payrexx.ts): once an approval exists the
      * state keeps it, and only the hold changes.
      */
     unsupported(reason = 'unrecognized_payment_endpoint') {
@@ -305,6 +312,7 @@ export class CheckoutLifecycle {
         this.set({ ...this.state, status: 'failed', reason: 'preparation_required' });
     }
     prepareHandoff(replay, requestUrl) {
+        this.heldBeforeHandoff = this.held;
         this.wspayChallenge = isWspayChallenge(requestUrl, replay);
         this.handoffs.push(requestUrl);
         if (replay.mode === 'token' && replay.executionMode === 'autopilot' && replay.shopOrderId) {
@@ -422,10 +430,14 @@ export class CheckoutLifecycle {
             return;
         }
         const mismatch = (!replay.mode || replay.mode === 'token') && replay.amountVerified === false;
+        // A hold raised while the answer was still landing stands: the page may send its first follow-up the moment the
+        // answer lands, and an EBANX or Payrexx send that fails then stops the approval's follow-ups for good
+        // (pre-claim.ts), so a new card request must not reopen the checkout under an approval that cannot finish.
+        const heldDuringHandoff = this.held && !this.heldBeforeHandoff;
         // A card endpoint answer means the merchant already holds the card: its page's own
         // retry, or a step-up that sends the card again, is refused until the application
         // reconciles the order, exactly as for a hosted form the device submitted.
-        this.held = !!this.options.requireMerchantResult || replay.mode === 'hosted_form' || replay.mode === 'card_endpoint' || mismatch || this.unboundStripeToken;
+        this.held = heldDuringHandoff || !!this.options.requireMerchantResult || replay.mode === 'hosted_form' || replay.mode === 'card_endpoint' || mismatch || this.unboundStripeToken;
         if (mismatch)
             this.stripeTokenPrepared = false;
         this.set({ status: 'awaiting_merchant', authorizationId: replay.authorizationId, mode: replay.mode ?? 'token',

package/dist/paygent.generated.d.ts

@@ -0,0 +1,60 @@
+declare var PAYGENT_PSP: string;
+declare var PAYGENT_CAPABILITY: string;
+declare var PAYGENT_OPERATION: string;
+declare var PAYGENT_TOKEN_HOSTS: Readonly<{
+    production: readonly string[];
+    sandbox: readonly string[];
+}>;
+declare var PAYGENT_TOKEN_PATH: string;
+declare var PAYGENT_CONTENT_TYPE: string;
+declare var PAYGENT_BODY_KEYS: readonly string[];
+declare var PAYGENT_REFUSAL_CODES: readonly string[];
+declare function paygentEnvironment(url: any): "production" | "sandbox" | null;
+declare function isPaygentTokenUrl(url: any): boolean;
+declare function paygentBodyVerdict(body: any): Readonly<{
+    verdict: "refuse";
+    code: any;
+}> | Readonly<{
+    verdict: "card";
+}>;
+declare function paygentRequestVerdict(url: any, body: any): Readonly<{
+    verdict: "refuse";
+    code: any;
+}> | Readonly<{
+    verdict: "card";
+}>;
+declare function paygentRequestRefusal(request: any): any;
+declare function paygentMerchantId(body: any): string | null;
+declare function paygentBodyMerchant(body: any): {
+    merchantId: string;
+    tokenKey: string;
+} | null;
+declare function paygentPreparationUrl(environment: any): string;
+declare var PAYGENT_MERCHANT_PINS: readonly any[];
+declare function paygentMerchantPin(merchantOrigin: any, merchant: any, pins?: readonly any[]): any;
+declare function paygentMerchantRefusal(environment: any, merchantOrigin: any, merchant: any, facts?: {}, pins?: readonly any[]): "unsupported_environment" | "paygent_merchant_unreviewed" | "paygent_currency_mismatch" | "paygent_merchant_mismatch" | null;
+declare function isPreparedPaygentRequest(url: any, method: any, body: any, environment: any, headers: any, binding?: {}, pins?: readonly any[]): boolean;
+declare function injectPaygentCard(body: any, card: any): {
+    body: string;
+    where: any[];
+};
+declare var PAYGENT_ANSWER_REFUSAL_CODES: readonly string[];
+declare function paygentAnswerOutcome(status: any, text: any, card: any): {
+    outcome: string;
+    code: any;
+    reason?: undefined;
+    body?: undefined;
+} | {
+    outcome: string;
+    reason: string | undefined;
+    code?: undefined;
+    body?: undefined;
+} | {
+    outcome: string;
+    body: string;
+    code?: undefined;
+    reason?: undefined;
+};
+declare function paygentRefusalCode(text: any): any;
+declare function paygentRefusalMessage(code: any): any;
+export { PAYGENT_ANSWER_REFUSAL_CODES, PAYGENT_BODY_KEYS, PAYGENT_CAPABILITY, PAYGENT_CONTENT_TYPE, PAYGENT_MERCHANT_PINS, PAYGENT_OPERATION, PAYGENT_PSP, PAYGENT_REFUSAL_CODES, PAYGENT_TOKEN_HOSTS, PAYGENT_TOKEN_PATH, injectPaygentCard, isPaygentTokenUrl, isPreparedPaygentRequest, paygentAnswerOutcome, paygentBodyMerchant, paygentBodyVerdict, paygentEnvironment, paygentMerchantId, paygentMerchantPin, paygentMerchantRefusal, paygentPreparationUrl, paygentRefusalCode, paygentRefusalMessage, paygentRequestRefusal, paygentRequestVerdict };