@alphawebai/hs-prism 0.1.0-rc.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (39) hide show
  1. package/LICENSE +201 -0
  2. package/README.md +493 -0
  3. package/dist/src/alphaweb/contracts.d.ts +6 -0
  4. package/dist/src/alphaweb/contracts.js +14 -0
  5. package/dist/src/alphaweb/error.d.ts +13 -0
  6. package/dist/src/alphaweb/error.js +100 -0
  7. package/dist/src/alphaweb/index.d.ts +3 -0
  8. package/dist/src/alphaweb/index.js +22 -0
  9. package/dist/src/alphaweb/manifest.d.ts +28 -0
  10. package/dist/src/alphaweb/manifest.js +55 -0
  11. package/dist/src/alphaweb/money.d.ts +19 -0
  12. package/dist/src/alphaweb/money.js +128 -0
  13. package/dist/src/alphaweb/stripe-connector.d.ts +58 -0
  14. package/dist/src/alphaweb/stripe-connector.js +1402 -0
  15. package/dist/src/alphaweb/types.d.ts +255 -0
  16. package/dist/src/alphaweb/types.js +3 -0
  17. package/dist/src/http_client.d.ts +58 -0
  18. package/dist/src/http_client.js +179 -0
  19. package/dist/src/index.d.ts +10 -0
  20. package/dist/src/index.js +41 -0
  21. package/dist/src/payments/_generated_connector_client_flows.d.ts +112 -0
  22. package/dist/src/payments/_generated_connector_client_flows.js +215 -0
  23. package/dist/src/payments/_generated_flows.js +141 -0
  24. package/dist/src/payments/_generated_grpc_client.d.ts +194 -0
  25. package/dist/src/payments/_generated_grpc_client.js +905 -0
  26. package/dist/src/payments/_generated_uniffi_client_flows.d.ts +169 -0
  27. package/dist/src/payments/_generated_uniffi_client_flows.js +342 -0
  28. package/dist/src/payments/connector_client.d.ts +51 -0
  29. package/dist/src/payments/connector_client.js +152 -0
  30. package/dist/src/payments/errors.d.ts +27 -0
  31. package/dist/src/payments/errors.js +39 -0
  32. package/dist/src/payments/generated/libconnector_service_ffi.so +0 -0
  33. package/dist/src/payments/generated/proto.d.ts +49087 -0
  34. package/dist/src/payments/generated/proto.js +154163 -0
  35. package/dist/src/payments/grpc_client.d.ts +1 -0
  36. package/dist/src/payments/grpc_client.js +20 -0
  37. package/dist/src/payments/uniffi_client.d.ts +40 -0
  38. package/dist/src/payments/uniffi_client.js +249 -0
  39. package/package.json +79 -0
@@ -0,0 +1,112 @@
1
+ import { ConnectorClient as _ConnectorClientBase } from "./connector_client";
2
+ import { types } from "./generated/proto";
3
+ export declare class CustomerClient extends _ConnectorClientBase {
4
+ /** CustomerService.Create — Create customer record in the payment processor system. Stores customer details for future payment operations without re-sending personal information. */
5
+ customerCreate(requestMsg: types.ICustomerServiceCreateRequest, options?: types.IRequestConfig | null): Promise<types.CustomerServiceCreateResponse>;
6
+ /** CustomerService.Get — Retrieves customer details from the payment processor. Callers typically use this before Create to implement get-or-create semantics for connectors that reject duplicates (e.g. Glomopay). */
7
+ customerGet(requestMsg: types.ICustomerServiceGetRequest, options?: types.IRequestConfig | null): Promise<types.CustomerServiceGetResponse>;
8
+ }
9
+ export declare class DisputeClient extends _ConnectorClientBase {
10
+ /** DisputeService.Accept — Concede dispute and accepts chargeback loss. Acknowledges liability and stops dispute defense process when evidence is insufficient. */
11
+ accept(requestMsg: types.IDisputeServiceAcceptRequest, options?: types.IRequestConfig | null): Promise<types.DisputeServiceAcceptResponse>;
12
+ /** DisputeService.Defend — Submit defense with reason code for dispute. Presents formal argument against customer's chargeback claim with supporting documentation. */
13
+ defend(requestMsg: types.IDisputeServiceDefendRequest, options?: types.IRequestConfig | null): Promise<types.DisputeServiceDefendResponse>;
14
+ /** DisputeService.SubmitEvidence — Upload evidence to dispute customer chargeback. Provides documentation like receipts and delivery proof to contest fraudulent transaction claims. */
15
+ submitEvidence(requestMsg: types.IDisputeServiceSubmitEvidenceRequest, options?: types.IRequestConfig | null): Promise<types.DisputeServiceSubmitEvidenceResponse>;
16
+ }
17
+ export declare class EventClient extends _ConnectorClientBase {
18
+ /** EventService.HandleEvent — Verify webhook source and return a unified typed response. Response mirrors PaymentService.Get / RefundService.Get / DisputeService.Get. */
19
+ handleEvent(requestMsg: types.IEventServiceHandleRequest, options?: types.IRequestConfig | null): Promise<types.EventServiceHandleResponse>;
20
+ /** EventService.ParseEvent — Parse a raw webhook payload without credentials. Returns resource reference and event type — sufficient to resolve secrets or early-exit. */
21
+ parseEvent(requestMsg: types.IEventServiceParseRequest, options?: types.IRequestConfig | null): Promise<types.EventServiceParseResponse>;
22
+ }
23
+ export declare class FraudAndRiskManagementClient extends _ConnectorClientBase {
24
+ /** FraudAndRiskManagementService.PostRiskCheck — Evaluate fraud risk after payment processing. Analyzes payment outcomes and post-transaction signals to refine risk models and detect chargeback fraud. */
25
+ postRiskCheck(requestMsg: types.IFrmServicePostRiskCheckRequest, options?: types.IRequestConfig | null): Promise<types.FrmServicePostRiskCheckResponse>;
26
+ /** FraudAndRiskManagementService.PreRiskCheck — Evaluate fraud risk before payment processing. Analyzes transaction details, customer behavior, and device fingerprints to determine if the payment should proceed, be rejected, or flagged for manual review. */
27
+ preRiskCheck(requestMsg: types.IFrmServicePreRiskCheckRequest, options?: types.IRequestConfig | null): Promise<types.FrmServicePreRiskCheckResponse>;
28
+ }
29
+ export declare class MerchantAuthenticationClient extends _ConnectorClientBase {
30
+ /** MerchantAuthenticationService.CreateClientAuthenticationToken — Initialize client-facing SDK sessions for wallets, device fingerprinting, etc. Returns structured data the client SDK needs to render payment/verification UI. */
31
+ createClientAuthenticationToken(requestMsg: types.IMerchantAuthenticationServiceCreateClientAuthenticationTokenRequest, options?: types.IRequestConfig | null): Promise<types.MerchantAuthenticationServiceCreateClientAuthenticationTokenResponse>;
32
+ /** MerchantAuthenticationService.CreateServerAuthenticationToken — Generate short-lived connector authentication token. Provides secure credentials for connector API access without storing secrets client-side. */
33
+ createServerAuthenticationToken(requestMsg: types.IMerchantAuthenticationServiceCreateServerAuthenticationTokenRequest, options?: types.IRequestConfig | null): Promise<types.MerchantAuthenticationServiceCreateServerAuthenticationTokenResponse>;
34
+ /** MerchantAuthenticationService.CreateServerSessionAuthenticationToken — Create a server-side session with the connector. Establishes session state for multi-step operations like 3DS verification or wallet authorization. */
35
+ createServerSessionAuthenticationToken(requestMsg: types.IMerchantAuthenticationServiceCreateServerSessionAuthenticationTokenRequest, options?: types.IRequestConfig | null): Promise<types.MerchantAuthenticationServiceCreateServerSessionAuthenticationTokenResponse>;
36
+ }
37
+ export declare class PaymentMethodAuthenticationClient extends _ConnectorClientBase {
38
+ /** PaymentMethodAuthenticationService.Authenticate — Execute 3DS challenge or frictionless verification. Authenticates customer via bank challenge or behind-the-scenes verification for fraud prevention. */
39
+ authenticate(requestMsg: types.IPaymentMethodAuthenticationServiceAuthenticateRequest, options?: types.IRequestConfig | null): Promise<types.PaymentMethodAuthenticationServiceAuthenticateResponse>;
40
+ /** PaymentMethodAuthenticationService.PostAuthenticate — Validate authentication results with the issuing bank. Processes bank's authentication decision to determine if payment can proceed. */
41
+ postAuthenticate(requestMsg: types.IPaymentMethodAuthenticationServicePostAuthenticateRequest, options?: types.IRequestConfig | null): Promise<types.PaymentMethodAuthenticationServicePostAuthenticateResponse>;
42
+ /** PaymentMethodAuthenticationService.PreAuthenticate — Initiate 3DS flow before payment authorization. Collects device data and prepares authentication context for frictionless or challenge-based verification. */
43
+ preAuthenticate(requestMsg: types.IPaymentMethodAuthenticationServicePreAuthenticateRequest, options?: types.IRequestConfig | null): Promise<types.PaymentMethodAuthenticationServicePreAuthenticateResponse>;
44
+ }
45
+ export declare class PaymentMethodClient extends _ConnectorClientBase {
46
+ /** PaymentMethodService.Eligibility — Check if the payment method is eligible for the transaction (e.g. BNPL pre-checkout check) */
47
+ eligibility(requestMsg: types.IPaymentMethodServiceEligibilityRequest, options?: types.IRequestConfig | null): Promise<types.PaymentMethodServiceEligibilityResponse>;
48
+ /** PaymentMethodService.Tokenize — Tokenize payment method for secure storage. Replaces raw card details with secure token for one-click payments and recurring billing. */
49
+ tokenize(requestMsg: types.IPaymentMethodServiceTokenizeRequest, options?: types.IRequestConfig | null): Promise<types.PaymentMethodServiceTokenizeResponse>;
50
+ }
51
+ export declare class PaymentClient extends _ConnectorClientBase {
52
+ /** PaymentService.Authorize — Authorize a payment amount on a payment method. This reserves funds without capturing them, essential for verifying availability before finalizing. */
53
+ authorize(requestMsg: types.IPaymentServiceAuthorizeRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceAuthorizeResponse>;
54
+ /** PaymentService.Capture — Finalize an authorized payment by transferring funds. Captures the authorized amount to complete the transaction and move funds to your merchant account. */
55
+ capture(requestMsg: types.IPaymentServiceCaptureRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceCaptureResponse>;
56
+ /** PaymentService.CreateOrder — Create a payment order for later processing. Establishes a transaction context that can be authorized or captured in subsequent API calls. */
57
+ createOrder(requestMsg: types.IPaymentServiceCreateOrderRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceCreateOrderResponse>;
58
+ /** PaymentService.Get — Retrieve current payment status from the payment processor. Enables synchronization between your system and payment processors for accurate state tracking. */
59
+ get(requestMsg: types.IPaymentServiceGetRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceGetResponse>;
60
+ /** PaymentService.IncrementalAuthorization — Increase the authorized amount for an existing payment. Enables you to capture additional funds when the transaction amount changes after initial authorization. */
61
+ incrementalAuthorization(requestMsg: types.IPaymentServiceIncrementalAuthorizationRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceIncrementalAuthorizationResponse>;
62
+ /** PaymentService.ProxyAuthorize — Authorize using vault-aliased card data. Proxy substitutes before connector. */
63
+ proxyAuthorize(requestMsg: types.IPaymentServiceProxyAuthorizeRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceAuthorizeResponse>;
64
+ /** PaymentService.ProxySetupRecurring — Setup recurring mandate using vault-aliased card data. */
65
+ proxySetupRecurring(requestMsg: types.IPaymentServiceProxySetupRecurringRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceSetupRecurringResponse>;
66
+ /** PaymentService.Refund — Process a partial or full refund for a captured payment. Returns funds to the customer when goods are returned or services are cancelled. */
67
+ refund(requestMsg: types.IPaymentServiceRefundRequest, options?: types.IRequestConfig | null): Promise<types.RefundResponse>;
68
+ /** PaymentService.Reverse — Reverse a captured payment in full. Initiates a complete refund when you need to cancel a settled transaction rather than just an authorization. */
69
+ reverse(requestMsg: types.IPaymentServiceReverseRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceReverseResponse>;
70
+ /** PaymentService.SetupRecurring — Configure a payment method for recurring billing. Sets up the mandate and payment details needed for future automated charges. */
71
+ setupRecurring(requestMsg: types.IPaymentServiceSetupRecurringRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceSetupRecurringResponse>;
72
+ /** PaymentService.TokenAuthorize — Authorize using a connector-issued payment method token. */
73
+ tokenAuthorize(requestMsg: types.IPaymentServiceTokenAuthorizeRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceAuthorizeResponse>;
74
+ /** PaymentService.TokenSetupRecurring — Setup a recurring mandate using a connector token. */
75
+ tokenSetupRecurring(requestMsg: types.IPaymentServiceTokenSetupRecurringRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceSetupRecurringResponse>;
76
+ /** PaymentService.Void — Cancel an authorized payment that has not been captured. Releases held funds back to the customer's payment method when a transaction cannot be completed. */
77
+ void(requestMsg: types.IPaymentServiceVoidRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceVoidResponse>;
78
+ /** PaymentService.VerifyRedirectResponse — Verify and process redirect responses from 3D Secure or other external flows. Validates authentication results and updates payment state accordingly. */
79
+ verifyRedirectResponse(requestMsg: types.IPaymentServiceVerifyRedirectResponseRequest, options?: types.IRequestConfig | null): Promise<types.PaymentServiceVerifyRedirectResponseResponse>;
80
+ }
81
+ export declare class PayoutClient extends _ConnectorClientBase {
82
+ /** PayoutService.Create — Creates a payout. */
83
+ payoutCreate(requestMsg: types.IPayoutServiceCreateRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceCreateResponse>;
84
+ /** PayoutService.CreateLink — Creates a link between the recipient and the payout. */
85
+ payoutCreateLink(requestMsg: types.IPayoutServiceCreateLinkRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceCreateLinkResponse>;
86
+ /** PayoutService.CreateRecipient — Create payout recipient. */
87
+ payoutCreateRecipient(requestMsg: types.IPayoutServiceCreateRecipientRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceCreateRecipientResponse>;
88
+ /** PayoutService.EnrollDisburseAccount — Enroll disburse account. */
89
+ payoutEnrollDisburseAccount(requestMsg: types.IPayoutServiceEnrollDisburseAccountRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceEnrollDisburseAccountResponse>;
90
+ /** PayoutService.Get — Retrieve payout details. */
91
+ payoutGet(requestMsg: types.IPayoutServiceGetRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceGetResponse>;
92
+ /** PayoutService.Stage — Stage the payout. */
93
+ payoutStage(requestMsg: types.IPayoutServiceStageRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceStageResponse>;
94
+ /** PayoutService.Transfer — Creates a payout fund transfer. */
95
+ payoutTransfer(requestMsg: types.IPayoutServiceTransferRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceTransferResponse>;
96
+ /** PayoutService.Void — Void a payout. */
97
+ payoutVoid(requestMsg: types.IPayoutServiceVoidRequest, options?: types.IRequestConfig | null): Promise<types.PayoutServiceVoidResponse>;
98
+ }
99
+ export declare class RecurringPaymentClient extends _ConnectorClientBase {
100
+ /** RecurringPaymentService.Charge — Charge using an existing stored recurring payment instruction. Processes repeat payments for subscriptions or recurring billing without collecting payment details. */
101
+ charge(requestMsg: types.IRecurringPaymentServiceChargeRequest, options?: types.IRequestConfig | null): Promise<types.RecurringPaymentServiceChargeResponse>;
102
+ /** RecurringPaymentService.Revoke — Cancel an existing recurring payment mandate. Stops future automatic charges on customer's stored consent for subscription cancellations. */
103
+ recurringRevoke(requestMsg: types.IRecurringPaymentServiceRevokeRequest, options?: types.IRequestConfig | null): Promise<types.RecurringPaymentServiceRevokeResponse>;
104
+ }
105
+ export declare class RefundClient extends _ConnectorClientBase {
106
+ /** RefundService.Get — Retrieve refund status from the payment processor. Tracks refund progress through processor settlement for accurate customer communication. */
107
+ refundGet(requestMsg: types.IRefundServiceGetRequest, options?: types.IRequestConfig | null): Promise<types.RefundResponse>;
108
+ }
109
+ export declare class SurchargeClient extends _ConnectorClientBase {
110
+ /** SurchargeService.Calculate — Calculate surcharge fees for a payment amount before processing. */
111
+ surchargeCalculate(requestMsg: types.ISurchargeServiceCalculateRequest, options?: types.IRequestConfig | null): Promise<types.SurchargeServiceCalculateResponse>;
112
+ }
@@ -0,0 +1,215 @@
1
+ "use strict";
2
+ // AUTO-GENERATED — do not edit by hand.
3
+ // Source: services.proto ∩ bindings/uniffi.rs | Regenerate: make generate
4
+ Object.defineProperty(exports, "__esModule", { value: true });
5
+ exports.SurchargeClient = exports.RefundClient = exports.RecurringPaymentClient = exports.PayoutClient = exports.PaymentClient = exports.PaymentMethodClient = exports.PaymentMethodAuthenticationClient = exports.MerchantAuthenticationClient = exports.FraudAndRiskManagementClient = exports.EventClient = exports.DisputeClient = exports.CustomerClient = void 0;
6
+ const connector_client_1 = require("./connector_client");
7
+ class CustomerClient extends connector_client_1.ConnectorClient {
8
+ /** CustomerService.Create — Create customer record in the payment processor system. Stores customer details for future payment operations without re-sending personal information. */
9
+ async customerCreate(requestMsg, options) {
10
+ return this._executeFlow('customer_create', requestMsg, options, 'CustomerServiceCreateRequest', 'CustomerServiceCreateResponse');
11
+ }
12
+ /** CustomerService.Get — Retrieves customer details from the payment processor. Callers typically use this before Create to implement get-or-create semantics for connectors that reject duplicates (e.g. Glomopay). */
13
+ async customerGet(requestMsg, options) {
14
+ return this._executeFlow('customer_get', requestMsg, options, 'CustomerServiceGetRequest', 'CustomerServiceGetResponse');
15
+ }
16
+ }
17
+ exports.CustomerClient = CustomerClient;
18
+ class DisputeClient extends connector_client_1.ConnectorClient {
19
+ /** DisputeService.Accept — Concede dispute and accepts chargeback loss. Acknowledges liability and stops dispute defense process when evidence is insufficient. */
20
+ async accept(requestMsg, options) {
21
+ return this._executeFlow('accept', requestMsg, options, 'DisputeServiceAcceptRequest', 'DisputeServiceAcceptResponse');
22
+ }
23
+ /** DisputeService.Defend — Submit defense with reason code for dispute. Presents formal argument against customer's chargeback claim with supporting documentation. */
24
+ async defend(requestMsg, options) {
25
+ return this._executeFlow('defend', requestMsg, options, 'DisputeServiceDefendRequest', 'DisputeServiceDefendResponse');
26
+ }
27
+ /** DisputeService.SubmitEvidence — Upload evidence to dispute customer chargeback. Provides documentation like receipts and delivery proof to contest fraudulent transaction claims. */
28
+ async submitEvidence(requestMsg, options) {
29
+ return this._executeFlow('submit_evidence', requestMsg, options, 'DisputeServiceSubmitEvidenceRequest', 'DisputeServiceSubmitEvidenceResponse');
30
+ }
31
+ }
32
+ exports.DisputeClient = DisputeClient;
33
+ class EventClient extends connector_client_1.ConnectorClient {
34
+ /** EventService.HandleEvent — Verify webhook source and return a unified typed response. Response mirrors PaymentService.Get / RefundService.Get / DisputeService.Get. */
35
+ async handleEvent(requestMsg, options) {
36
+ return this._executeDirect('handle_event', requestMsg, options, 'EventServiceHandleRequest', 'EventServiceHandleResponse');
37
+ }
38
+ /** EventService.ParseEvent — Parse a raw webhook payload without credentials. Returns resource reference and event type — sufficient to resolve secrets or early-exit. */
39
+ async parseEvent(requestMsg, options) {
40
+ return this._executeDirect('parse_event', requestMsg, options, 'EventServiceParseRequest', 'EventServiceParseResponse');
41
+ }
42
+ }
43
+ exports.EventClient = EventClient;
44
+ class FraudAndRiskManagementClient extends connector_client_1.ConnectorClient {
45
+ /** FraudAndRiskManagementService.PostRiskCheck — Evaluate fraud risk after payment processing. Analyzes payment outcomes and post-transaction signals to refine risk models and detect chargeback fraud. */
46
+ async postRiskCheck(requestMsg, options) {
47
+ return this._executeFlow('post_risk_check', requestMsg, options, 'FrmServicePostRiskCheckRequest', 'FrmServicePostRiskCheckResponse');
48
+ }
49
+ /** FraudAndRiskManagementService.PreRiskCheck — Evaluate fraud risk before payment processing. Analyzes transaction details, customer behavior, and device fingerprints to determine if the payment should proceed, be rejected, or flagged for manual review. */
50
+ async preRiskCheck(requestMsg, options) {
51
+ return this._executeFlow('pre_risk_check', requestMsg, options, 'FrmServicePreRiskCheckRequest', 'FrmServicePreRiskCheckResponse');
52
+ }
53
+ }
54
+ exports.FraudAndRiskManagementClient = FraudAndRiskManagementClient;
55
+ class MerchantAuthenticationClient extends connector_client_1.ConnectorClient {
56
+ /** MerchantAuthenticationService.CreateClientAuthenticationToken — Initialize client-facing SDK sessions for wallets, device fingerprinting, etc. Returns structured data the client SDK needs to render payment/verification UI. */
57
+ async createClientAuthenticationToken(requestMsg, options) {
58
+ return this._executeFlow('create_client_authentication_token', requestMsg, options, 'MerchantAuthenticationServiceCreateClientAuthenticationTokenRequest', 'MerchantAuthenticationServiceCreateClientAuthenticationTokenResponse');
59
+ }
60
+ /** MerchantAuthenticationService.CreateServerAuthenticationToken — Generate short-lived connector authentication token. Provides secure credentials for connector API access without storing secrets client-side. */
61
+ async createServerAuthenticationToken(requestMsg, options) {
62
+ return this._executeFlow('create_server_authentication_token', requestMsg, options, 'MerchantAuthenticationServiceCreateServerAuthenticationTokenRequest', 'MerchantAuthenticationServiceCreateServerAuthenticationTokenResponse');
63
+ }
64
+ /** MerchantAuthenticationService.CreateServerSessionAuthenticationToken — Create a server-side session with the connector. Establishes session state for multi-step operations like 3DS verification or wallet authorization. */
65
+ async createServerSessionAuthenticationToken(requestMsg, options) {
66
+ return this._executeFlow('create_server_session_authentication_token', requestMsg, options, 'MerchantAuthenticationServiceCreateServerSessionAuthenticationTokenRequest', 'MerchantAuthenticationServiceCreateServerSessionAuthenticationTokenResponse');
67
+ }
68
+ }
69
+ exports.MerchantAuthenticationClient = MerchantAuthenticationClient;
70
+ class PaymentMethodAuthenticationClient extends connector_client_1.ConnectorClient {
71
+ /** PaymentMethodAuthenticationService.Authenticate — Execute 3DS challenge or frictionless verification. Authenticates customer via bank challenge or behind-the-scenes verification for fraud prevention. */
72
+ async authenticate(requestMsg, options) {
73
+ return this._executeFlow('authenticate', requestMsg, options, 'PaymentMethodAuthenticationServiceAuthenticateRequest', 'PaymentMethodAuthenticationServiceAuthenticateResponse');
74
+ }
75
+ /** PaymentMethodAuthenticationService.PostAuthenticate — Validate authentication results with the issuing bank. Processes bank's authentication decision to determine if payment can proceed. */
76
+ async postAuthenticate(requestMsg, options) {
77
+ return this._executeFlow('post_authenticate', requestMsg, options, 'PaymentMethodAuthenticationServicePostAuthenticateRequest', 'PaymentMethodAuthenticationServicePostAuthenticateResponse');
78
+ }
79
+ /** PaymentMethodAuthenticationService.PreAuthenticate — Initiate 3DS flow before payment authorization. Collects device data and prepares authentication context for frictionless or challenge-based verification. */
80
+ async preAuthenticate(requestMsg, options) {
81
+ return this._executeFlow('pre_authenticate', requestMsg, options, 'PaymentMethodAuthenticationServicePreAuthenticateRequest', 'PaymentMethodAuthenticationServicePreAuthenticateResponse');
82
+ }
83
+ }
84
+ exports.PaymentMethodAuthenticationClient = PaymentMethodAuthenticationClient;
85
+ class PaymentMethodClient extends connector_client_1.ConnectorClient {
86
+ /** PaymentMethodService.Eligibility — Check if the payment method is eligible for the transaction (e.g. BNPL pre-checkout check) */
87
+ async eligibility(requestMsg, options) {
88
+ return this._executeFlow('eligibility', requestMsg, options, 'PaymentMethodServiceEligibilityRequest', 'PaymentMethodServiceEligibilityResponse');
89
+ }
90
+ /** PaymentMethodService.Tokenize — Tokenize payment method for secure storage. Replaces raw card details with secure token for one-click payments and recurring billing. */
91
+ async tokenize(requestMsg, options) {
92
+ return this._executeFlow('tokenize', requestMsg, options, 'PaymentMethodServiceTokenizeRequest', 'PaymentMethodServiceTokenizeResponse');
93
+ }
94
+ }
95
+ exports.PaymentMethodClient = PaymentMethodClient;
96
+ class PaymentClient extends connector_client_1.ConnectorClient {
97
+ /** PaymentService.Authorize — Authorize a payment amount on a payment method. This reserves funds without capturing them, essential for verifying availability before finalizing. */
98
+ async authorize(requestMsg, options) {
99
+ return this._executeFlow('authorize', requestMsg, options, 'PaymentServiceAuthorizeRequest', 'PaymentServiceAuthorizeResponse');
100
+ }
101
+ /** PaymentService.Capture — Finalize an authorized payment by transferring funds. Captures the authorized amount to complete the transaction and move funds to your merchant account. */
102
+ async capture(requestMsg, options) {
103
+ return this._executeFlow('capture', requestMsg, options, 'PaymentServiceCaptureRequest', 'PaymentServiceCaptureResponse');
104
+ }
105
+ /** PaymentService.CreateOrder — Create a payment order for later processing. Establishes a transaction context that can be authorized or captured in subsequent API calls. */
106
+ async createOrder(requestMsg, options) {
107
+ return this._executeFlow('create_order', requestMsg, options, 'PaymentServiceCreateOrderRequest', 'PaymentServiceCreateOrderResponse');
108
+ }
109
+ /** PaymentService.Get — Retrieve current payment status from the payment processor. Enables synchronization between your system and payment processors for accurate state tracking. */
110
+ async get(requestMsg, options) {
111
+ return this._executeFlow('get', requestMsg, options, 'PaymentServiceGetRequest', 'PaymentServiceGetResponse');
112
+ }
113
+ /** PaymentService.IncrementalAuthorization — Increase the authorized amount for an existing payment. Enables you to capture additional funds when the transaction amount changes after initial authorization. */
114
+ async incrementalAuthorization(requestMsg, options) {
115
+ return this._executeFlow('incremental_authorization', requestMsg, options, 'PaymentServiceIncrementalAuthorizationRequest', 'PaymentServiceIncrementalAuthorizationResponse');
116
+ }
117
+ /** PaymentService.ProxyAuthorize — Authorize using vault-aliased card data. Proxy substitutes before connector. */
118
+ async proxyAuthorize(requestMsg, options) {
119
+ return this._executeFlow('proxy_authorize', requestMsg, options, 'PaymentServiceProxyAuthorizeRequest', 'PaymentServiceAuthorizeResponse');
120
+ }
121
+ /** PaymentService.ProxySetupRecurring — Setup recurring mandate using vault-aliased card data. */
122
+ async proxySetupRecurring(requestMsg, options) {
123
+ return this._executeFlow('proxy_setup_recurring', requestMsg, options, 'PaymentServiceProxySetupRecurringRequest', 'PaymentServiceSetupRecurringResponse');
124
+ }
125
+ /** PaymentService.Refund — Process a partial or full refund for a captured payment. Returns funds to the customer when goods are returned or services are cancelled. */
126
+ async refund(requestMsg, options) {
127
+ return this._executeFlow('refund', requestMsg, options, 'PaymentServiceRefundRequest', 'RefundResponse');
128
+ }
129
+ /** PaymentService.Reverse — Reverse a captured payment in full. Initiates a complete refund when you need to cancel a settled transaction rather than just an authorization. */
130
+ async reverse(requestMsg, options) {
131
+ return this._executeFlow('reverse', requestMsg, options, 'PaymentServiceReverseRequest', 'PaymentServiceReverseResponse');
132
+ }
133
+ /** PaymentService.SetupRecurring — Configure a payment method for recurring billing. Sets up the mandate and payment details needed for future automated charges. */
134
+ async setupRecurring(requestMsg, options) {
135
+ return this._executeFlow('setup_recurring', requestMsg, options, 'PaymentServiceSetupRecurringRequest', 'PaymentServiceSetupRecurringResponse');
136
+ }
137
+ /** PaymentService.TokenAuthorize — Authorize using a connector-issued payment method token. */
138
+ async tokenAuthorize(requestMsg, options) {
139
+ return this._executeFlow('token_authorize', requestMsg, options, 'PaymentServiceTokenAuthorizeRequest', 'PaymentServiceAuthorizeResponse');
140
+ }
141
+ /** PaymentService.TokenSetupRecurring — Setup a recurring mandate using a connector token. */
142
+ async tokenSetupRecurring(requestMsg, options) {
143
+ return this._executeFlow('token_setup_recurring', requestMsg, options, 'PaymentServiceTokenSetupRecurringRequest', 'PaymentServiceSetupRecurringResponse');
144
+ }
145
+ /** PaymentService.Void — Cancel an authorized payment that has not been captured. Releases held funds back to the customer's payment method when a transaction cannot be completed. */
146
+ async void(requestMsg, options) {
147
+ return this._executeFlow('void', requestMsg, options, 'PaymentServiceVoidRequest', 'PaymentServiceVoidResponse');
148
+ }
149
+ /** PaymentService.VerifyRedirectResponse — Verify and process redirect responses from 3D Secure or other external flows. Validates authentication results and updates payment state accordingly. */
150
+ async verifyRedirectResponse(requestMsg, options) {
151
+ return this._executeDirect('verify_redirect_response', requestMsg, options, 'PaymentServiceVerifyRedirectResponseRequest', 'PaymentServiceVerifyRedirectResponseResponse');
152
+ }
153
+ }
154
+ exports.PaymentClient = PaymentClient;
155
+ class PayoutClient extends connector_client_1.ConnectorClient {
156
+ /** PayoutService.Create — Creates a payout. */
157
+ async payoutCreate(requestMsg, options) {
158
+ return this._executeFlow('payout_create', requestMsg, options, 'PayoutServiceCreateRequest', 'PayoutServiceCreateResponse');
159
+ }
160
+ /** PayoutService.CreateLink — Creates a link between the recipient and the payout. */
161
+ async payoutCreateLink(requestMsg, options) {
162
+ return this._executeFlow('payout_create_link', requestMsg, options, 'PayoutServiceCreateLinkRequest', 'PayoutServiceCreateLinkResponse');
163
+ }
164
+ /** PayoutService.CreateRecipient — Create payout recipient. */
165
+ async payoutCreateRecipient(requestMsg, options) {
166
+ return this._executeFlow('payout_create_recipient', requestMsg, options, 'PayoutServiceCreateRecipientRequest', 'PayoutServiceCreateRecipientResponse');
167
+ }
168
+ /** PayoutService.EnrollDisburseAccount — Enroll disburse account. */
169
+ async payoutEnrollDisburseAccount(requestMsg, options) {
170
+ return this._executeFlow('payout_enroll_disburse_account', requestMsg, options, 'PayoutServiceEnrollDisburseAccountRequest', 'PayoutServiceEnrollDisburseAccountResponse');
171
+ }
172
+ /** PayoutService.Get — Retrieve payout details. */
173
+ async payoutGet(requestMsg, options) {
174
+ return this._executeFlow('payout_get', requestMsg, options, 'PayoutServiceGetRequest', 'PayoutServiceGetResponse');
175
+ }
176
+ /** PayoutService.Stage — Stage the payout. */
177
+ async payoutStage(requestMsg, options) {
178
+ return this._executeFlow('payout_stage', requestMsg, options, 'PayoutServiceStageRequest', 'PayoutServiceStageResponse');
179
+ }
180
+ /** PayoutService.Transfer — Creates a payout fund transfer. */
181
+ async payoutTransfer(requestMsg, options) {
182
+ return this._executeFlow('payout_transfer', requestMsg, options, 'PayoutServiceTransferRequest', 'PayoutServiceTransferResponse');
183
+ }
184
+ /** PayoutService.Void — Void a payout. */
185
+ async payoutVoid(requestMsg, options) {
186
+ return this._executeFlow('payout_void', requestMsg, options, 'PayoutServiceVoidRequest', 'PayoutServiceVoidResponse');
187
+ }
188
+ }
189
+ exports.PayoutClient = PayoutClient;
190
+ class RecurringPaymentClient extends connector_client_1.ConnectorClient {
191
+ /** RecurringPaymentService.Charge — Charge using an existing stored recurring payment instruction. Processes repeat payments for subscriptions or recurring billing without collecting payment details. */
192
+ async charge(requestMsg, options) {
193
+ return this._executeFlow('charge', requestMsg, options, 'RecurringPaymentServiceChargeRequest', 'RecurringPaymentServiceChargeResponse');
194
+ }
195
+ /** RecurringPaymentService.Revoke — Cancel an existing recurring payment mandate. Stops future automatic charges on customer's stored consent for subscription cancellations. */
196
+ async recurringRevoke(requestMsg, options) {
197
+ return this._executeFlow('recurring_revoke', requestMsg, options, 'RecurringPaymentServiceRevokeRequest', 'RecurringPaymentServiceRevokeResponse');
198
+ }
199
+ }
200
+ exports.RecurringPaymentClient = RecurringPaymentClient;
201
+ class RefundClient extends connector_client_1.ConnectorClient {
202
+ /** RefundService.Get — Retrieve refund status from the payment processor. Tracks refund progress through processor settlement for accurate customer communication. */
203
+ async refundGet(requestMsg, options) {
204
+ return this._executeFlow('refund_get', requestMsg, options, 'RefundServiceGetRequest', 'RefundResponse');
205
+ }
206
+ }
207
+ exports.RefundClient = RefundClient;
208
+ class SurchargeClient extends connector_client_1.ConnectorClient {
209
+ /** SurchargeService.Calculate — Calculate surcharge fees for a payment amount before processing. */
210
+ async surchargeCalculate(requestMsg, options) {
211
+ return this._executeFlow('surcharge_calculate', requestMsg, options, 'SurchargeServiceCalculateRequest', 'SurchargeServiceCalculateResponse');
212
+ }
213
+ }
214
+ exports.SurchargeClient = SurchargeClient;
215
+ //# sourceMappingURL=_generated_connector_client_flows.js.map
@@ -0,0 +1,141 @@
1
+ // AUTO-GENERATED — do not edit by hand.
2
+ // Source: services.proto ∩ bindings/uniffi.rs | Regenerate: make generate
3
+ "use strict";
4
+
5
+ const FLOWS = {
6
+ // accept: DisputeService.Accept — Concede dispute and accepts chargeback loss. Acknowledges liability and stops dispute defense process when evidence is insufficient.
7
+ accept : { request: "DisputeServiceAcceptRequest", response: "DisputeServiceAcceptResponse" },
8
+
9
+ // authenticate: PaymentMethodAuthenticationService.Authenticate — Execute 3DS challenge or frictionless verification. Authenticates customer via bank challenge or behind-the-scenes verification for fraud prevention.
10
+ authenticate : { request: "PaymentMethodAuthenticationServiceAuthenticateRequest", response: "PaymentMethodAuthenticationServiceAuthenticateResponse" },
11
+
12
+ // authorize: PaymentService.Authorize — Authorize a payment amount on a payment method. This reserves funds without capturing them, essential for verifying availability before finalizing.
13
+ authorize : { request: "PaymentServiceAuthorizeRequest", response: "PaymentServiceAuthorizeResponse" },
14
+
15
+ // capture: PaymentService.Capture — Finalize an authorized payment by transferring funds. Captures the authorized amount to complete the transaction and move funds to your merchant account.
16
+ capture : { request: "PaymentServiceCaptureRequest", response: "PaymentServiceCaptureResponse" },
17
+
18
+ // charge: RecurringPaymentService.Charge — Charge using an existing stored recurring payment instruction. Processes repeat payments for subscriptions or recurring billing without collecting payment details.
19
+ charge : { request: "RecurringPaymentServiceChargeRequest", response: "RecurringPaymentServiceChargeResponse" },
20
+
21
+ // create_client_authentication_token: MerchantAuthenticationService.CreateClientAuthenticationToken — Initialize client-facing SDK sessions for wallets, device fingerprinting, etc. Returns structured data the client SDK needs to render payment/verification UI.
22
+ create_client_authentication_token : { request: "MerchantAuthenticationServiceCreateClientAuthenticationTokenRequest", response: "MerchantAuthenticationServiceCreateClientAuthenticationTokenResponse" },
23
+
24
+ // create_order: PaymentService.CreateOrder — Create a payment order for later processing. Establishes a transaction context that can be authorized or captured in subsequent API calls.
25
+ create_order : { request: "PaymentServiceCreateOrderRequest", response: "PaymentServiceCreateOrderResponse" },
26
+
27
+ // create_server_authentication_token: MerchantAuthenticationService.CreateServerAuthenticationToken — Generate short-lived connector authentication token. Provides secure credentials for connector API access without storing secrets client-side.
28
+ create_server_authentication_token : { request: "MerchantAuthenticationServiceCreateServerAuthenticationTokenRequest", response: "MerchantAuthenticationServiceCreateServerAuthenticationTokenResponse" },
29
+
30
+ // create_server_session_authentication_token: MerchantAuthenticationService.CreateServerSessionAuthenticationToken — Create a server-side session with the connector. Establishes session state for multi-step operations like 3DS verification or wallet authorization.
31
+ create_server_session_authentication_token : { request: "MerchantAuthenticationServiceCreateServerSessionAuthenticationTokenRequest", response: "MerchantAuthenticationServiceCreateServerSessionAuthenticationTokenResponse" },
32
+
33
+ // customer_create: CustomerService.Create — Create customer record in the payment processor system. Stores customer details for future payment operations without re-sending personal information.
34
+ customer_create : { request: "CustomerServiceCreateRequest", response: "CustomerServiceCreateResponse" },
35
+
36
+ // customer_get: CustomerService.Get — Retrieves customer details from the payment processor. Callers typically use this before Create to implement get-or-create semantics for connectors that reject duplicates (e.g. Glomopay).
37
+ customer_get : { request: "CustomerServiceGetRequest", response: "CustomerServiceGetResponse" },
38
+
39
+ // defend: DisputeService.Defend — Submit defense with reason code for dispute. Presents formal argument against customer's chargeback claim with supporting documentation.
40
+ defend : { request: "DisputeServiceDefendRequest", response: "DisputeServiceDefendResponse" },
41
+
42
+ // eligibility: PaymentMethodService.Eligibility — Check if the payment method is eligible for the transaction (e.g. BNPL pre-checkout check)
43
+ eligibility : { request: "PaymentMethodServiceEligibilityRequest", response: "PaymentMethodServiceEligibilityResponse" },
44
+
45
+ // get: PaymentService.Get — Retrieve current payment status from the payment processor. Enables synchronization between your system and payment processors for accurate state tracking.
46
+ get : { request: "PaymentServiceGetRequest", response: "PaymentServiceGetResponse" },
47
+
48
+ // incremental_authorization: PaymentService.IncrementalAuthorization — Increase the authorized amount for an existing payment. Enables you to capture additional funds when the transaction amount changes after initial authorization.
49
+ incremental_authorization : { request: "PaymentServiceIncrementalAuthorizationRequest", response: "PaymentServiceIncrementalAuthorizationResponse" },
50
+
51
+ // payout_create: PayoutService.Create — Creates a payout.
52
+ payout_create : { request: "PayoutServiceCreateRequest", response: "PayoutServiceCreateResponse" },
53
+
54
+ // payout_create_link: PayoutService.CreateLink — Creates a link between the recipient and the payout.
55
+ payout_create_link : { request: "PayoutServiceCreateLinkRequest", response: "PayoutServiceCreateLinkResponse" },
56
+
57
+ // payout_create_recipient: PayoutService.CreateRecipient — Create payout recipient.
58
+ payout_create_recipient : { request: "PayoutServiceCreateRecipientRequest", response: "PayoutServiceCreateRecipientResponse" },
59
+
60
+ // payout_enroll_disburse_account: PayoutService.EnrollDisburseAccount — Enroll disburse account.
61
+ payout_enroll_disburse_account : { request: "PayoutServiceEnrollDisburseAccountRequest", response: "PayoutServiceEnrollDisburseAccountResponse" },
62
+
63
+ // payout_get: PayoutService.Get — Retrieve payout details.
64
+ payout_get : { request: "PayoutServiceGetRequest", response: "PayoutServiceGetResponse" },
65
+
66
+ // payout_stage: PayoutService.Stage — Stage the payout.
67
+ payout_stage : { request: "PayoutServiceStageRequest", response: "PayoutServiceStageResponse" },
68
+
69
+ // payout_transfer: PayoutService.Transfer — Creates a payout fund transfer.
70
+ payout_transfer : { request: "PayoutServiceTransferRequest", response: "PayoutServiceTransferResponse" },
71
+
72
+ // payout_void: PayoutService.Void — Void a payout.
73
+ payout_void : { request: "PayoutServiceVoidRequest", response: "PayoutServiceVoidResponse" },
74
+
75
+ // post_authenticate: PaymentMethodAuthenticationService.PostAuthenticate — Validate authentication results with the issuing bank. Processes bank's authentication decision to determine if payment can proceed.
76
+ post_authenticate : { request: "PaymentMethodAuthenticationServicePostAuthenticateRequest", response: "PaymentMethodAuthenticationServicePostAuthenticateResponse" },
77
+
78
+ // post_risk_check: FraudAndRiskManagementService.PostRiskCheck — Evaluate fraud risk after payment processing. Analyzes payment outcomes and post-transaction signals to refine risk models and detect chargeback fraud.
79
+ post_risk_check : { request: "FrmServicePostRiskCheckRequest", response: "FrmServicePostRiskCheckResponse" },
80
+
81
+ // pre_authenticate: PaymentMethodAuthenticationService.PreAuthenticate — Initiate 3DS flow before payment authorization. Collects device data and prepares authentication context for frictionless or challenge-based verification.
82
+ pre_authenticate : { request: "PaymentMethodAuthenticationServicePreAuthenticateRequest", response: "PaymentMethodAuthenticationServicePreAuthenticateResponse" },
83
+
84
+ // pre_risk_check: FraudAndRiskManagementService.PreRiskCheck — Evaluate fraud risk before payment processing. Analyzes transaction details, customer behavior, and device fingerprints to determine if the payment should proceed, be rejected, or flagged for manual review.
85
+ pre_risk_check : { request: "FrmServicePreRiskCheckRequest", response: "FrmServicePreRiskCheckResponse" },
86
+
87
+ // proxy_authorize: PaymentService.ProxyAuthorize — Authorize using vault-aliased card data. Proxy substitutes before connector.
88
+ proxy_authorize : { request: "PaymentServiceProxyAuthorizeRequest", response: "PaymentServiceAuthorizeResponse" },
89
+
90
+ // proxy_setup_recurring: PaymentService.ProxySetupRecurring — Setup recurring mandate using vault-aliased card data.
91
+ proxy_setup_recurring : { request: "PaymentServiceProxySetupRecurringRequest", response: "PaymentServiceSetupRecurringResponse" },
92
+
93
+ // recurring_revoke: RecurringPaymentService.Revoke — Cancel an existing recurring payment mandate. Stops future automatic charges on customer's stored consent for subscription cancellations.
94
+ recurring_revoke : { request: "RecurringPaymentServiceRevokeRequest", response: "RecurringPaymentServiceRevokeResponse" },
95
+
96
+ // refund: PaymentService.Refund — Process a partial or full refund for a captured payment. Returns funds to the customer when goods are returned or services are cancelled.
97
+ refund : { request: "PaymentServiceRefundRequest", response: "RefundResponse" },
98
+
99
+ // refund_get: RefundService.Get — Retrieve refund status from the payment processor. Tracks refund progress through processor settlement for accurate customer communication.
100
+ refund_get : { request: "RefundServiceGetRequest", response: "RefundResponse" },
101
+
102
+ // reverse: PaymentService.Reverse — Reverse a captured payment in full. Initiates a complete refund when you need to cancel a settled transaction rather than just an authorization.
103
+ reverse : { request: "PaymentServiceReverseRequest", response: "PaymentServiceReverseResponse" },
104
+
105
+ // setup_recurring: PaymentService.SetupRecurring — Configure a payment method for recurring billing. Sets up the mandate and payment details needed for future automated charges.
106
+ setup_recurring : { request: "PaymentServiceSetupRecurringRequest", response: "PaymentServiceSetupRecurringResponse" },
107
+
108
+ // submit_evidence: DisputeService.SubmitEvidence — Upload evidence to dispute customer chargeback. Provides documentation like receipts and delivery proof to contest fraudulent transaction claims.
109
+ submit_evidence : { request: "DisputeServiceSubmitEvidenceRequest", response: "DisputeServiceSubmitEvidenceResponse" },
110
+
111
+ // surcharge_calculate: SurchargeService.Calculate — Calculate surcharge fees for a payment amount before processing.
112
+ surcharge_calculate : { request: "SurchargeServiceCalculateRequest", response: "SurchargeServiceCalculateResponse" },
113
+
114
+ // token_authorize: PaymentService.TokenAuthorize — Authorize using a connector-issued payment method token.
115
+ token_authorize : { request: "PaymentServiceTokenAuthorizeRequest", response: "PaymentServiceAuthorizeResponse" },
116
+
117
+ // token_setup_recurring: PaymentService.TokenSetupRecurring — Setup a recurring mandate using a connector token.
118
+ token_setup_recurring : { request: "PaymentServiceTokenSetupRecurringRequest", response: "PaymentServiceSetupRecurringResponse" },
119
+
120
+ // tokenize: PaymentMethodService.Tokenize — Tokenize payment method for secure storage. Replaces raw card details with secure token for one-click payments and recurring billing.
121
+ tokenize : { request: "PaymentMethodServiceTokenizeRequest", response: "PaymentMethodServiceTokenizeResponse" },
122
+
123
+ // void: PaymentService.Void — Cancel an authorized payment that has not been captured. Releases held funds back to the customer's payment method when a transaction cannot be completed.
124
+ void : { request: "PaymentServiceVoidRequest", response: "PaymentServiceVoidResponse" },
125
+
126
+ };
127
+
128
+ // Single-step flows: no HTTP round-trip.
129
+ const SINGLE_FLOWS = {
130
+ // handle_event: EventService.HandleEvent — Verify webhook source and return a unified typed response. Response mirrors PaymentService.Get / RefundService.Get / DisputeService.Get.
131
+ handle_event : { request: "EventServiceHandleRequest", response: "EventServiceHandleResponse" },
132
+
133
+ // parse_event: EventService.ParseEvent — Parse a raw webhook payload without credentials. Returns resource reference and event type — sufficient to resolve secrets or early-exit.
134
+ parse_event : { request: "EventServiceParseRequest", response: "EventServiceParseResponse" },
135
+
136
+ // verify_redirect_response: PaymentService.VerifyRedirectResponse — Verify and process redirect responses from 3D Secure or other external flows. Validates authentication results and updates payment state accordingly.
137
+ verify_redirect_response : { request: "PaymentServiceVerifyRedirectResponseRequest", response: "PaymentServiceVerifyRedirectResponseResponse" },
138
+
139
+ };
140
+
141
+ module.exports = { FLOWS, SINGLE_FLOWS };