@adyen/api-library
Version:
The Adyen API Library for NodeJS enables you to work with Adyen APIs.
72 lines (71 loc) • 4.08 kB
TypeScript
import { Address } from "./address";
import { Amount } from "./amount";
import { Card } from "./card";
import { FundSource } from "./fundSource";
import { Name } from "./name";
import { Recurring } from "./recurring";
export declare class PayoutRequest {
"amount": Amount;
"billingAddress"?: Address | null;
"card"?: Card | null;
/**
* An integer value that is added to the normal fraud score. The value can be either positive or negative.
*/
"fraudOffset"?: number;
"fundSource"?: FundSource | null;
/**
* The merchant account identifier, with which you want to process the transaction.
*/
"merchantAccount": string;
"recurring"?: Recurring | null;
/**
* The reference to uniquely identify a payment. This reference is used in all communication with you about the payment status. We recommend using a unique value per payment; however, it is not a requirement. If you need to provide multiple references for a transaction, separate them with hyphens (\"-\"). Maximum length: 80 characters.
*/
"reference": string;
/**
* The `recurringDetailReference` you want to use for this payment. The value `LATEST` can be used to select the most recently stored recurring detail.
*/
"selectedRecurringDetailReference"?: string;
/**
* The shopper\'s email address. We recommend that you provide this data, as it is used in velocity fraud checks. > Required for Visa and JCB transactions that require 3D Secure 2 authentication if you did not include the `telephoneNumber`.
*/
"shopperEmail"?: string;
/**
* Specifies the sales channel, through which the shopper gives their card details, and whether the shopper is a returning customer. For the web service API, Adyen assumes Ecommerce shopper interaction by default. This field has the following possible values: * `Ecommerce` - Online transactions where the cardholder is present (online). For better authorisation rates, we recommend sending the card security code (CSC) along with the request. * `ContAuth` - Card on file and/or subscription transactions, where the cardholder is known to the merchant (returning customer). If the shopper is present (online), you can supply also the CSC to improve authorisation (one-click payment). * `Moto` - Mail-order and telephone-order transactions where the shopper is in contact with the merchant via email or telephone. * `POS` - Point-of-sale transactions where the shopper is physically present to make a payment using a secure payment terminal.
*/
"shopperInteraction"?: PayoutRequest.ShopperInteractionEnum;
"shopperName"?: Name | null;
/**
* Required for recurring payments. Your reference to uniquely identify this shopper, for example user ID or account ID. The value is case-sensitive and must be at least three characters. > Your reference must not include personally identifiable information (PII) such as name or email address.
*/
"shopperReference"?: string;
/**
* The shopper\'s telephone number. > Required for Visa and JCB transactions that require 3D Secure 2 authentication, if you did not include the `shopperEmail`. The phone number must include a plus sign (+) and a country code (1-3 digits), followed by the number (4-15 digits). If the value you provide does not follow the guidelines, we drop the value and do not submit it for authentication.
*/
"telephoneNumber"?: string;
static readonly discriminator: string | undefined;
static readonly mapping: {
[index: string]: string;
} | undefined;
static readonly attributeTypeMap: Array<{
name: string;
baseName: string;
type: string;
format: string;
}>;
static getAttributeTypeMap(): {
name: string;
baseName: string;
type: string;
format: string;
}[];
constructor();
}
export declare namespace PayoutRequest {
enum ShopperInteractionEnum {
Ecommerce = "Ecommerce",
ContAuth = "ContAuth",
Moto = "Moto",
Pos = "POS"
}
}