mirror of
https://github.com/jlengrand/adyen-node-api-library.git
synced 2026-03-10 08:01:20 +00:00
[create-pull-request] automated change (#969)
Co-authored-by: Wouter Boereboom <62436079+wboereboom@users.noreply.github.com>
This commit is contained in:
committed by
GitHub
parent
41f58990b4
commit
f6d61eae30
@@ -18,7 +18,7 @@ export class AdditionalDataCommon {
|
||||
*/
|
||||
'authorisationType'?: string;
|
||||
/**
|
||||
* Allows you to determine or override the acquirer account that should be used for the transaction. If you need to process a payment with an acquirer different from a default one, you can set up a corresponding configuration on the Adyen payments platform. Then you can pass a custom routing flag in a payment request\'s additional data to target a specific acquirer. To enable this functionality, contact [Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* Allows you to determine or override the acquirer account that should be used for the transaction. If you need to process a payment with an acquirer different from a default one, you can set up a corresponding configuration on the Adyen payments platform. Then you can pass a custom routing flag in a payment request\'s additional data to target a specific acquirer. To enable this functionality, contact [Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'customRoutingFlag'?: string;
|
||||
/**
|
||||
|
||||
@@ -105,7 +105,7 @@ export class CheckoutBalanceCheckRequest {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -12,7 +12,7 @@ import { FraudResult } from './fraudResult';
|
||||
|
||||
export class CheckoutBalanceCheckResponse {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
'balance': Amount;
|
||||
|
||||
@@ -12,7 +12,7 @@ import { FraudResult } from './fraudResult';
|
||||
|
||||
export class CheckoutCreateOrderResponse {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
'amount': Amount;
|
||||
|
||||
@@ -138,7 +138,7 @@ export class CreateCheckoutSessionRequest {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -146,7 +146,7 @@ export class CreateCheckoutSessionResponse {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -16,7 +16,7 @@ import { ThreeDS2Result } from './threeDS2Result';
|
||||
|
||||
export class PaymentDetailsResponse {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
'amount'?: Amount;
|
||||
|
||||
@@ -218,7 +218,7 @@ export class PaymentDonationRequest {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -206,7 +206,7 @@ export class PaymentRequest {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -29,7 +29,7 @@ export class PaymentResponse {
|
||||
*/
|
||||
'action'?: CheckoutAwaitAction | CheckoutBankTransferAction | CheckoutDonationAction | CheckoutOneTimePasscodeAction | CheckoutQrCodeAction | CheckoutRedirectAction | CheckoutSDKAction | CheckoutThreeDS2Action | CheckoutVoucherAction;
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
'amount'?: Amount;
|
||||
|
||||
@@ -148,7 +148,7 @@ export class PaymentSetupRequest {
|
||||
*/
|
||||
'shopperEmail'?: string;
|
||||
/**
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://support.adyen.com/hc/en-us/requests/new).
|
||||
* The shopper\'s IP address. In general, we recommend that you provide this data, as it is used in a number of risk checks (for instance, number of payment attempts or location-based checks). > For 3D Secure 2 transactions, schemes require `shopperIP` for all browser-based implementations. This field is also mandatory for some merchants depending on your business model. For more information, [contact Support](https://www.adyen.help/hc/en-us/requests/new).
|
||||
*/
|
||||
'shopperIP'?: string;
|
||||
/**
|
||||
|
||||
@@ -13,7 +13,7 @@ import { ServiceError2 } from './serviceError2';
|
||||
|
||||
export class PaymentVerificationResponse {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
'fraudResult'?: FraudResult;
|
||||
|
||||
@@ -12,7 +12,7 @@ import { FraudResult } from './fraudResult';
|
||||
|
||||
export class PaymentResult {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
/**
|
||||
|
||||
@@ -12,7 +12,7 @@ import { FraudResult } from './fraudResult';
|
||||
|
||||
export class PayoutResponse {
|
||||
/**
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Account** > **API URLs** > **Additional data settings**.
|
||||
* Contains additional information about the payment. Some data fields are included only if you select them first: Go to **Customer Area** > **Developers** > **Additional data**.
|
||||
*/
|
||||
'additionalData'?: { [key: string]: string; };
|
||||
/**
|
||||
|
||||
@@ -12,23 +12,23 @@ import { Address } from './address';
|
||||
export class Store {
|
||||
'address'?: Address;
|
||||
/**
|
||||
* The store description
|
||||
* The description of the store.
|
||||
*/
|
||||
'description'?: string;
|
||||
/**
|
||||
* List of unique terminal IDs assigned to this store
|
||||
* The list of terminals assigned to the store.
|
||||
*/
|
||||
'inStoreTerminals'?: Array<string>;
|
||||
/**
|
||||
* Merchant account code
|
||||
* The code of the merchant account.
|
||||
*/
|
||||
'merchantAccountCode'?: string;
|
||||
/**
|
||||
* Store status. Possible values: - `PreActive`: The store has been created, but not yet activated. - `Active`: The store has been activated. This means you can process payments over the store. - `Inactive`: The store is currently not active. - `InactiveWithModifications`: The store is currently not active, but payment modifications such as refunds are still allowed. - `Closed`: The store has been closed.
|
||||
* The status of the store: - `PreActive`: the store has been created, but not yet activated. - `Active`: the store has been activated. This means you can process payments for this store. - `Inactive`: the store is currently not active. - `InactiveWithModifications`: the store is currently not active, but payment modifications such as refunds are possible. - `Closed`: the store has been closed.
|
||||
*/
|
||||
'status'?: string;
|
||||
/**
|
||||
* The store code of the store.
|
||||
* The code of the store.
|
||||
*/
|
||||
'store': string;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user