Skip to content

Commit 21f9876

Browse files
sachshetsachshet
authored
Merge pull request #85 from CyberSource/feature/apr23-rel-updates
Apr-23 Release Updates
2 parents 4efe0b0 + 7b91d2d commit 21f9876

File tree

90 files changed

+1901
-172
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

90 files changed

+1901
-172
lines changed

‎cybersource_rest_client.gemspec

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ require "cybersource_rest_client/version"
1717

1818
Gem::Specification.new do |s|
1919
s.name = "cybersource_rest_client"
20-
s.version = "0.0.50"
20+
s.version = "0.0.51"
2121
s.platform = Gem::Platform::RUBY
2222
s.authors = ["CyberSource"]
2323
s.email = ["[email protected]"]

‎docs/CreateBundledDecisionManagerCaseRequest.md

+1
Original file line numberDiff line numberDiff line change
@@ -17,5 +17,6 @@ Name | Type | Description | Notes
1717
**acquirer_information** | [**Ptsv2paymentsAcquirerInformation**](Ptsv2paymentsAcquirerInformation.md) | | [optional]
1818
**recurring_payment_information** | [**Ptsv2paymentsRecurringPaymentInformation**](Ptsv2paymentsRecurringPaymentInformation.md) | | [optional]
1919
**consumer_authentication_information** | [**Riskv1decisionsConsumerAuthenticationInformation**](Riskv1decisionsConsumerAuthenticationInformation.md) | | [optional]
20+
**watchlist_screening_information** | [**Ptsv2paymentsWatchlistScreeningInformation**](Ptsv2paymentsWatchlistScreeningInformation.md) | | [optional]
2021

2122

‎docs/CreatePaymentRequest.md

+1
Original file line numberDiff line numberDiff line change
@@ -26,5 +26,6 @@ Name | Type | Description | Notes
2626
**risk_information** | [**Ptsv2paymentsRiskInformation**](Ptsv2paymentsRiskInformation.md) | | [optional]
2727
**acquirer_information** | [**Ptsv2paymentsAcquirerInformation**](Ptsv2paymentsAcquirerInformation.md) | | [optional]
2828
**recurring_payment_information** | [**Ptsv2paymentsRecurringPaymentInformation**](Ptsv2paymentsRecurringPaymentInformation.md) | | [optional]
29+
**watchlist_screening_information** | [**Ptsv2paymentsWatchlistScreeningInformation**](Ptsv2paymentsWatchlistScreeningInformation.md) | | [optional]
2930

3031

‎docs/PaymentsApi.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Method | HTTP request | Description
1414
1515
Process a Payment
1616

17-
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/api/developer-guides/dita-payments/GettingStarted.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation.
17+
A payment authorizes the amount for the transaction. There are a number of supported payment feature, such as E-commerce and Card Present - Credit Card/Debit Card, Echeck, e-Wallets, Level II/III Data, etc.. A payment response includes the status of the request. It also includes processor-specific information when the request is successful and errors if unsuccessful. See the [Payments Developer Guides Page](https://developer.cybersource.com/docs/cybs/en-us/payments/developer/ctv/rest/payments/payments-intro.html). Authorization can be requested with Capture, Decision Manager, Payer Authentication(3ds), and Token Creation.
1818

1919
### Example
2020
```ruby

‎docs/PtsV2PaymentsPost201Response.md

+1
Original file line numberDiff line numberDiff line change
@@ -23,5 +23,6 @@ Name | Type | Description | Notes
2323
**buyer_information** | [**PtsV2PaymentsPost201ResponseBuyerInformation**](PtsV2PaymentsPost201ResponseBuyerInformation.md) | | [optional]
2424
**risk_information** | [**PtsV2PaymentsPost201ResponseRiskInformation**](PtsV2PaymentsPost201ResponseRiskInformation.md) | | [optional]
2525
**consumer_authentication_information** | [**PtsV2PaymentsPost201ResponseConsumerAuthenticationInformation**](PtsV2PaymentsPost201ResponseConsumerAuthenticationInformation.md) | | [optional]
26+
**watchlist_screening_information** | [**PtsV2PaymentsPost201ResponseWatchlistScreeningInformation**](PtsV2PaymentsPost201ResponseWatchlistScreeningInformation.md) | | [optional]
2627

2728

‎docs/PtsV2PaymentsPost201ResponseErrorInformation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**reason** | **String** | The reason of the status. Possible values: - AVS_FAILED - CONTACT_PROCESSOR - EXPIRED_CARD - PROCESSOR_DECLINED - INSUFFICIENT_FUND - STOLEN_LOST_CARD - ISSUER_UNAVAILABLE - UNAUTHORIZED_CARD - CVN_NOT_MATCH - EXCEEDS_CREDIT_LIMIT - INVALID_CVN - DECLINED_CHECK - BLACKLISTED_CUSTOMER - SUSPENDED_ACCOUNT - PAYMENT_REFUSED - CV_FAILED - INVALID_ACCOUNT - GENERAL_DECLINE - INVALID_MERCHANT_CONFIGURATION - DECISION_PROFILE_REJECT - SCORE_EXCEEDS_THRESHOLD - PENDING_AUTHENTICATION - ACH_VERIFICATION_FAILED - DECISION_PROFILE_REVIEW - CONSUMER_AUTHENTICATION_REQUIRED - CONSUMER_AUTHENTICATION_FAILED - ALLOWABLE_PIN_RETRIES_EXCEEDED - PROCESSOR_ERROR | [optional]
6+
**reason** | **String** | The reason of the status. Possible values: - AVS_FAILED - CONTACT_PROCESSOR - EXPIRED_CARD - PROCESSOR_DECLINED - INSUFFICIENT_FUND - STOLEN_LOST_CARD - ISSUER_UNAVAILABLE - UNAUTHORIZED_CARD - CVN_NOT_MATCH - EXCEEDS_CREDIT_LIMIT - INVALID_CVN - DECLINED_CHECK - BLACKLISTED_CUSTOMER - SUSPENDED_ACCOUNT - PAYMENT_REFUSED - CV_FAILED - INVALID_ACCOUNT - GENERAL_DECLINE - INVALID_MERCHANT_CONFIGURATION - DECISION_PROFILE_REJECT - SCORE_EXCEEDS_THRESHOLD - PENDING_AUTHENTICATION - ACH_VERIFICATION_FAILED - DECISION_PROFILE_REVIEW - CONSUMER_AUTHENTICATION_REQUIRED - CONSUMER_AUTHENTICATION_FAILED - ALLOWABLE_PIN_RETRIES_EXCEEDED - PROCESSOR_ERROR - CUSTOMER_WATCHLIST_MATCH - ADDRESS_COUNTRY_WATCHLIST_MATCH - EMAIL_COUNTRY_WATCHLIST_MATCH - IP_COUNTRY_WATCHLIST_MATCH - INVALID_MERCHANT_CONFIGURATION | [optional]
77
**message** | **String** | The detail message related to the status and reason listed above. | [optional]
88
**details** | [**Array<PtsV2PaymentsPost201ResponseErrorInformationDetails>**](PtsV2PaymentsPost201ResponseErrorInformationDetails.md) | | [optional]
99

‎docs/PtsV2PaymentsPost201ResponseOrderInformation.md

+1
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,6 @@ Name | Type | Description | Notes
66
**amount_details** | [**PtsV2PaymentsPost201ResponseOrderInformationAmountDetails**](PtsV2PaymentsPost201ResponseOrderInformationAmountDetails.md) | | [optional]
77
**invoice_details** | [**PtsV2PaymentsPost201ResponseOrderInformationInvoiceDetails**](PtsV2PaymentsPost201ResponseOrderInformationInvoiceDetails.md) | | [optional]
88
**reward_points_details** | [**PtsV2PaymentsPost201ResponseOrderInformationRewardPointsDetails**](PtsV2PaymentsPost201ResponseOrderInformationRewardPointsDetails.md) | | [optional]
9+
**bill_to** | [**PtsV2PaymentsPost201ResponseOrderInformationBillTo**](PtsV2PaymentsPost201ResponseOrderInformationBillTo.md) | | [optional]
910

1011

‎docs/PtsV2PaymentsPost201ResponseOrderInformationBillTo.md

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# CyberSource::PtsV2PaymentsPost201ResponseOrderInformationBillTo
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**alternate_phone_number_verification_status** | **String** | #### Visa Platform Connect Contains one of the following values that will identify the phone number result code in the account verification response message: 'VERIFIED' - Customer verified 'UNVERIFIED' - Customer not verified 'FAILED' - Customer verification failed | [optional]
7+
**alternate_email_verification_status** | **String** | #### Visa Platform Connect Contains one of the following values that will identify the phone number result code in the account verification response message: 'VERIFIED' - Customer verified 'UNVERIFIED' - Customer not verified 'FAILED' - Customer verification failed | [optional]
8+
9+

‎docs/PtsV2PaymentsPost201ResponsePaymentInformationTokenizedCard.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,10 @@ Name | Type | Description | Notes
66
**prefix** | **String** | First six digits of token. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. For details, see `token_prefix` field description in [Google Pay Using the SCMP API.] (https://apps.cybersource.com/library/documentation/dev_guides/Google_Pay_SCMP_API/html/) | [optional]
77
**suffix** | **String** | Last four digits of token. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. For details, see `token_suffix` field description in [Google Pay Using the SCMP API.] (https://apps.cybersource.com/library/documentation/dev_guides/Google_Pay_SCMP_API/html/) | [optional]
88
**type** | **String** | Three-digit value that indicates the card type. **IMPORTANT** It is strongly recommended that you include the card type field in request messages even if it is optional for your processor and card type. Omitting the card type can cause the transaction to be processed with the wrong card type. Possible values: - `001`: Visa. For card-present transactions on all processors except SIX, the Visa Electron card type is processed the same way that the Visa debit card is processed. Use card type value `001` for Visa Electron. - `002`: Mastercard, Eurocard[^1], which is a European regional brand of Mastercard. - `003`: American Express - `004`: Discover - `005`: Diners Club - `006`: Carte Blanche[^1] - `007`: JCB[^1] - `014`: Enroute[^1] - `021`: JAL[^1] - `024`: Maestro (UK Domestic)[^1] - `031`: Delta[^1]: Use this value only for Ingenico ePayments. For other processors, use `001` for all Visa card types. - `033`: Visa Electron[^1]. Use this value only for Ingenico ePayments and SIX. For other processors, use `001` for all Visa card types. - `034`: Dankort[^1] - `036`: Cartes Bancaires[^1,4] - `037`: Carta Si[^1] - `039`: Encoded account number[^1] - `040`: UATP[^1] - `042`: Maestro (International)[^1] - `050`: Hipercard[^2,3] - `051`: Aura - `054`: Elo[^3] - `062`: China UnionPay - '070': EFTPOS [^1]: For this card type, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in your request for an authorization or a stand-alone credit. [^2]: For this card type on Cielo 3.0, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. This card type is not supported on Cielo 1.5. [^3]: For this card type on Getnet and Rede, you must include the `paymentInformation.card.type` or `paymentInformation.tokenizedCard.type` field in a request for an authorization or a stand-alone credit. [^4]: For this card type, you must include the `paymentInformation.card.type` in your request for any payer authentication services. #### Used by **Authorization** Required for Carte Blanche and JCB. Optional for all other card types. #### Card Present reply This field is included in the reply message when the client software that is installed on the POS terminal uses the token management service (TMS) to retrieve tokenized payment details. You must contact customer support to have your account enabled to receive these fields in the credit reply message. Returned by the Credit service. This reply field is only supported by the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX #### Google Pay transactions For PAN-based Google Pay transactions, this field is returned in the API response. #### GPX This field only supports transactions from the following card types: - Visa - Mastercard - AMEX - Discover - Diners - JCB - Union Pay International | [optional]
9-
**assurance_level** | **String** | Confidence level of the tokenization. This value is assigned by the token service provider. **Note** This field is supported only for **CyberSource through VisaNet** and **FDC Nashville Global**. Returned by PIN debit credit or PIN debit purchase. | [optional]
9+
**assurance_level** | **String** | Confidence level of the tokenization. This value is assigned by the token service provider. **Note** This field is supported only for **CyberSource through VisaNet** and **FDC Nashville Global**. Returned by PIN debit credit or PIN debit purchase. **Note** Merchants supported for **CyberSource through VisaNet**/**Visa Platform Connect** are advised not to use this field. | [optional]
1010
**expiration_month** | **String** | One of two possible meanings: - The two-digit month in which a token expires. - The two-digit month in which a card expires. Format: `MM` Possible values: `01` through `12` **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below. #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (`01` through `12`) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request. #### Encoded Account Numbers For encoded account numbers (`card_type=039`), if there is no expiration date on the card, use `12`.\\ **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. #### Samsung Pay and Apple Pay Month in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. For processor-specific information, see the `customer_cc_expmo` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) | [optional]
1111
**expiration_year** | **String** | One of two possible meanings: - The four-digit year in which a token expires. - The four-digit year in which a card expires. Format: `YYYY` Possible values: `1900` through `3000` Data type: Non-negative integer **NOTE** The meaning of this field is dependent on the payment processor that is returning the value in an authorization reply. Please see the processor-specific details below. #### Barclays and Streamline For Maestro (UK Domestic) and Maestro (International) cards on Barclays and Streamline, this must be a valid value (1900 through 3000) but is not required to be a valid expiration date. In other words, an expiration date that is in the past does not cause CyberSource to reject your request. However, an invalid expiration date might cause the issuer to reject your request. #### Encoded Account Numbers For encoded account numbers (`card_ type=039`), if there is no expiration date on the card, use `2021`. #### FDC Nashville Global and FDMS South You can send in 2 digits or 4 digits. When you send in 2 digits, they must be the last 2 digits of the year. #### Samsung Pay and Apple Pay Year in which the token expires. CyberSource includes this field in the reply message when it decrypts the payment blob for the tokenized transaction. **Important** It is your responsibility to determine whether a field is required for the transaction you are requesting. For processor-specific information, see the `customer_cc_expyr` or `token_expiration_year` field in [Credit Card Services Using the SCMP API.](http://apps.cybersource.com/library/documentation/dev_guides/CC_Svcs_SCMP_API/html) | [optional]
1212
**requestor_id** | **String** | Value that identifies your business and indicates that the cardholder’s account number is tokenized. This value is assigned by the token service provider and is unique within the token service provider’s database. **Note** This field is supported only for **CyberSource through VisaNet** and **FDC Nashville Global**. #### PIN debit Optional field for PIN debit credit or PIN debit purchase transactions that use payment network tokens; otherwise, not used. | [optional]
13+
**assurance_method** | **String** | Confidence level of the tokenization. This value is assigned by the token service provider. **Note** This field is supported only for **Visa Platform Connect** | [optional]
1314

1415

‎docs/PtsV2PaymentsPost201ResponseProcessorInformationElectronicVerificationResults.md

+8-2
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,13 @@ Name | Type | Description | Notes
1313
**postal_code_raw** | **String** | Raw Electronic Verification response code from the processor for the customer’s postal code. | [optional]
1414
**street** | **String** | Mapped Electronic Verification response code for the customer’s street address. For details, see `auth_ev_street` 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]
1515
**street_raw** | **String** | Raw Electronic Verification response code from the processor for the customer’s street address. | [optional]
16-
**name** | **String** | Mapped Electronic Verification response code for the customer’s name. | [optional]
17-
**name_raw** | **String** | Raw Electronic Verification response code from the processor for the customer’s name. | [optional]
16+
**name** | **String** | #### Visa Platform Connect Mapped Electronic Verification response code for the customer’s name. Valid values : 'Y' Yes, the data Matches 'N' No Match 'O' Partial Match | [optional]
17+
**name_raw** | **String** | #### Visa Platform Connect Raw Electronic Verification response code from the processor for the customer’s name. Valid values : '01' Match '50' Partial Match '99' No Match | [optional]
18+
**first_name_raw** | **String** | #### Visa Platform Connect Raw electronic verification response code from the processor for the customer’s first name. Valid values : '01' Match '50' Partial Match '99' No Match | [optional]
19+
**first_name** | **String** | #### Visa Platform Connect Mapped electronic verification response code from the processor for the customer’s first name. Valid values : 'Y' Yes, the data Matches 'N' No Match 'O' Partial Match | [optional]
20+
**middle_name_raw** | **String** | #### Visa Platform Connect Raw electronic verification response code from the processor for the customer’s middle name. Valid values : '01' Match '50' Partial Match '99' No Match | [optional]
21+
**middle_name** | **String** | #### Visa Platform Connect Mapped electronic verification response code from the processor for the customer’s middle name. Valid values : 'Y' Yes, the data Matches 'N' No Match 'O' Partial Match | [optional]
22+
**last_name_raw** | **String** | #### Visa Platform Connect Raw electronic verification response code from the processor for the customer’s last name. Valid values : '01' Match '50' Partial Match '99' No Match | [optional]
23+
**last_name** | **String** | #### Visa Platform Connect Mapped electronic verification response code from the processor for the customer’s last name. Valid values : 'Y' Yes, the data Matches 'N' No Match 'O' Partial Match | [optional]
1824

1925

0 commit comments

Comments
 (0)