You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**status** | **String** | The status for payerAuthentication 201 enroll and validate calls. Possible values are: - `AUTHENTICATION_SUCCESSFUL` - `PENDING_AUTHENTICATION` - `INVALID_REQUEST` - `AUTHENTICATION_FAILED` | [optional]
8
+
**reason** | **String** | The reason of the status. Possible values are: - `INVALID_MERCHANT_CONFIGURATION` - `CONSUMER_AUTHENTICATION_REQUIRED` - `CONSUMER_AUTHENTICATION_FAILED` - `AUTHENTICATION_FAILED` | [optional]
9
+
**message** | **String** | The message describing the reason of the status. Value is: - Encountered a Payer Authentication problem. Payer could not be authenticated. | [optional]
**status** | **String** | The status for the call can be: - COMPLETED - INVALID_REQUEST - DECLINED | [optional]
8
+
**reason** | **String** | The reason of the status. Value can be - `CUSTOMER_WATCHLIST_MATCH` - `ADDRESS_COUNTRY_WATCHLIST_MATCH` - `EMAIL_COUNTRY_WATCHLIST_MATCH` - `IP_COUNTRY_WATCHLIST_MATCH` - `INVALID_MERCHANT_CONFIGURATION` | [optional]
9
+
**message** | **String** | The message describing the reason of the status. Value can be - The customer matched the Denied Parties List - The Export bill_country/ship_country match - Export email_country match - Export hostname_country/ip_country match | [optional]
**actionList** | **List<String>** | Array of actions (one or more) to be included in the payment to invoke bundled services along with payment. Possible values are one or more of follows: - `DECISION_SKIP`: Use this when you want to skip Decision Manager service(s). - `TOKEN_CREATE`: Use this when you want to create a token from the card/bank data in your payment request. - `CONSUMER_AUTHENTICATION`: Use this when you want to check if a card is enrolled in Payer Authentioncation along with your payment request. - `VALIDATE_CONSUMER_AUTHENTICATION`: Use this after you acquire a Payer Authentioncation result that needs to be included for your payment request. - `AP_INITIATE`: Use this when Alternative Payment Initiate service is requested. - `WATCHLIST_SCREENING` : Use this when you want to call Watchlist Screening service. | [optional]
7
+
**actionList** | **List<String>** | Array of actions (one or more) to be included in the payment to invoke bundled services along with payment. Possible values are one or more of follows: - `DECISION_SKIP`: Use this when you want to skip Decision Manager service(s). - `TOKEN_CREATE`: Use this when you want to create a token from the card/bank data in your payment request. - `CONSUMER_AUTHENTICATION`: Use this when you want to check if a card is enrolled in Payer Authentication along with your payment request. - `VALIDATE_CONSUMER_AUTHENTICATION`: Use this after you acquire a Payer Authentication result that needs to be included for your payment request. - `AP_INITIATE`: Use this when Alternative Payment Initiate service is requested. - `WATCHLIST_SCREENING` : Use this when you want to call Watchlist Screening service. | [optional]
8
8
**enableEscrowOption** | **Boolean** | Indicates whether to use the customer’s escrow agreement. Possible values: - `true`: yes, use the customer’s escrow agreement. - `false`: no, do not use the customer’s escrow agreement. | [optional]
9
9
**actionTokenTypes** | **List<String>** | CyberSource tokens types you are performing a create on. If not supplied the default token type for the merchants token vault will be used. Valid values: - customer - paymentInstrument - instrumentIdentifier - shippingAddress | [optional]
10
10
**binSource** | **String** | Bin Source File Identifier. Possible values: - itmx - rupay | [optional]
Copy file name to clipboardExpand all lines: docs/Ptsv2paymentsRecipientInformation.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,7 @@ Name | Type | Description | Notes
8
8
**lastName** | **String** | Recipient’s last name. This field is a _passthrough_, which means that CyberSource does not verify the value or modify it in any way before sending it to the processor. If the field is not required for the transaction, CyberSource does not forward it to the processor. For details, see the `recipient_lastname` field description in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) | [optional]
9
9
**middleName** | **String** | Recipient’s middle name. This field is a _passthrough_, which means that CyberSource does not verify the value or modify it in any way before sending it to the processor. If the field is not required for the transaction, CyberSource does not forward it to the processor. For details, see the `recipient_middlename` field description in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) | [optional]
10
10
**postalCode** | **String** | Partial postal code for the recipient’s address. For example, if the postal code is **NN5 7SG**, the value for this field should be the first part of the postal code: **NN5**. This field is a _pass-through_, which means that CyberSource does not verify the value or modify it in any way before sending it to the processor. If the field is not required for the transaction, CyberSource does not forward it to the processor. For details, see the `recipient_postal_code` field description in [Credit Card Services Using the SCMP API.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) | [optional]
11
+
**dateOfBirth** | **String** | Recipient’s date of birth. **Format**: `YYYYMMDD`. This field is a `pass-through`, which means that CyberSource ensures that the value is eight numeric characters but otherwise does not verify the value or modify it in any way before sending it to the processor. If the field is not required for the transaction, CyberSource does not forward it to the processor. For more details, see `recipient_date_of_birth` field description in the [Credit Card Services Using the SCMP API Guide.](https://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html/) | [optional]
0 commit comments