Skip to content

Commit 1fc958b

Browse files
rsachan8rsachan8
committed
Oct 22 release changes
1 parent b3eb3bc commit 1fc958b

File tree

80 files changed

+6885
-43
lines changed

Some content is hidden

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

80 files changed

+6885
-43
lines changed

‎docs/Body.md‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
# CyberSource::Body
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**requestor** | **String** | Identifies the service requesting parsing |
7+
**parsed_tag_limit** | **Integer** | Number of tags to parse for each EMV tag string provided. | [optional]
8+
**emv_details_list** | [**Array<Tssv2transactionsemvTagDetailsEmvDetailsList>**](Tssv2transactionsemvTagDetailsEmvDetailsList.md) | An array of objects, each containing a requestId and the corresponding emvRequestCombinedTags |
9+
10+

‎docs/EMVTagDetailsApi.md‎

Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
# CyberSource::EMVTagDetailsApi
2+
3+
All URIs are relative to *https://apitest.cybersource.com*
4+
5+
Method | HTTP request | Description
6+
------------- | ------------- | -------------
7+
[**get_emv_tags**](EMVTagDetailsApi.md#get_emv_tags) | **GET** /tss/v2/transactions/emvTagDetails | Retrieve the EMV Dictionary
8+
[**parse_emv_tags**](EMVTagDetailsApi.md#parse_emv_tags) | **POST** /tss/v2/transactions/emvTagDetails | Parse an EMV String
9+
10+
11+
# **get_emv_tags**
12+
> TssV2GetEmvTags200Response get_emv_tags
13+
14+
Retrieve the EMV Dictionary
15+
16+
Returns the entire EMV tag dictionary
17+
18+
### Example
19+
```ruby
20+
# load the gem
21+
require 'cybersource_rest_client'
22+
23+
api_instance = CyberSource::EMVTagDetailsApi.new
24+
25+
begin
26+
#Retrieve the EMV Dictionary
27+
result = api_instance.get_emv_tags
28+
p result
29+
rescue CyberSource::ApiError => e
30+
puts "Exception when calling EMVTagDetailsApi->get_emv_tags: #{e}"
31+
end
32+
```
33+
34+
### Parameters
35+
This endpoint does not need any parameter.
36+
37+
### Return type
38+
39+
[**TssV2GetEmvTags200Response**](TssV2GetEmvTags200Response.md)
40+
41+
### Authorization
42+
43+
No authorization required
44+
45+
### HTTP request headers
46+
47+
- **Content-Type**: application/json;charset=utf-8
48+
- **Accept**: application/json;charset=utf-8
49+
50+
51+
52+
# **parse_emv_tags**
53+
> TssV2PostEmvTags200Response parse_emv_tags(body)
54+
55+
Parse an EMV String
56+
57+
Pass an EMV Tag-Length-Value (TLV) string for parsing.
58+
59+
### Example
60+
```ruby
61+
# load the gem
62+
require 'cybersource_rest_client'
63+
64+
api_instance = CyberSource::EMVTagDetailsApi.new
65+
66+
body = CyberSource::Body.new # Body |
67+
68+
69+
begin
70+
#Parse an EMV String
71+
result = api_instance.parse_emv_tags(body)
72+
p result
73+
rescue CyberSource::ApiError => e
74+
puts "Exception when calling EMVTagDetailsApi->parse_emv_tags: #{e}"
75+
end
76+
```
77+
78+
### Parameters
79+
80+
Name | Type | Description | Notes
81+
------------- | ------------- | ------------- | -------------
82+
**body** | [**Body**](Body.md)| |
83+
84+
### Return type
85+
86+
[**TssV2PostEmvTags200Response**](TssV2PostEmvTags200Response.md)
87+
88+
### Authorization
89+
90+
No authorization required
91+
92+
### HTTP request headers
93+
94+
- **Content-Type**: application/json;charset=utf-8
95+
- **Accept**: application/hal+json;charset=utf-8
96+
97+
98+

‎docs/GenerateUnifiedCheckoutCaptureContextRequest.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# CyberSource::GenerateUnifiedCheckoutCaptureContextRequest
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**target_origins** | **Array<String>** | | [optional]
7+
**client_version** | **String** | verson number of Unified Checkout being used | [optional]
8+
**allowed_card_networks** | **Array<String>** | | [optional]
9+
**allowed_payment_types** | **Array<String>** | | [optional]
10+
**country** | **String** | Country the purchase is originating from (e.g. country of the merchant). Use the two- character ISO Standard | [optional]
11+
**locale** | **String** | Localization of the User experience conforming to the ISO 639-1 language standards and two-character ISO Standard Country Code | [optional]
12+
**capture_mandate** | [**Upv1capturecontextsCaptureMandate**](Upv1capturecontextsCaptureMandate.md) | | [optional]
13+
**order_information** | [**Upv1capturecontextsOrderInformation**](Upv1capturecontextsOrderInformation.md) | | [optional]
14+
**checkout_api_initialization** | [**Upv1capturecontextsCheckoutApiInitialization**](Upv1capturecontextsCheckoutApiInitialization.md) | | [optional]
15+
16+

‎docs/InlineResponse4003.md‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# CyberSource::InlineResponse4003
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**correlation_id** | **String** | | [optional]
7+
**details** | [**Array<InlineResponse4003Details>**](InlineResponse4003Details.md) | | [optional]
8+
**information_link** | **String** | | [optional]
9+
**message** | **String** | |
10+
**reason** | **String** | |
11+
12+

‎docs/InlineResponse4003Details.md‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# CyberSource::InlineResponse4003Details
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**location** | **String** | | [optional]
7+
**message** | **String** | | [optional]
8+
9+

‎docs/PtsV2PaymentsPost201ResponseConsumerAuthenticationInformationStrongAuthenticationIssuerInformation.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,8 @@ Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
66
**risk_analysis_exemption_result** | **String** | Possible values: Visa Platform Connect - `8401` Merchant not participating in Visa Trusted Listing Program. - `8402` Issuer not participating in Visa Trusted Listing Program. - `8403` Cardholder has not trusted the merchant (supplied by Visa Net). - `8404` Indeterminate or invalid issuer response. - `8473` Cardholder has not trusted the merchant (issuer-supplied). - `8474` Did not meet the exemption criteria (issuer-supplied). Upto 20 Values may be received in a transaction. | [optional]
77
**trusted_merchant_exemption_result** | **String** | Possible values: Visa Platform Connect - `2` Trusted merchant exemption validated/honored. - `3` Trusted merchant exemption failed validation/not honored. | [optional]
8+
**low_value_exemption_result** | **String** | This will be the value returned by Visanet when low value exemption has been requested. Valid values: Visa Platform Connect - `2` Low value exemption validated/honored - `3` Low value exemption failed validation/not honored | [optional]
9+
**secure_corporate_payment_result** | **String** | This will be the value returned by Visanet when secure corporate payment (scp) exemption has been requested. Valid values: Visa Platform Connect - `2` Secure corporate payment exemption validated/honored - `3` Secure corporate payment exemption failed validation/not honored | [optional]
10+
**transaction_risk_analysis_exemption_result** | **String** | This will be the value returned by Visanet when transaction risk analysis (TRA) exemption has been requested. Valid values: Visa Platform Connect - `2` transaction risk analysis (TRA) exemption validated/honored - `3` transaction risk analysis (TRA) exemption failed validation/not honored | [optional]
811

912

‎docs/PtsV2PaymentsPost201ResponseIssuerInformation.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,5 @@ Name | Type | Description | Notes
77
**discretionary_data** | **String** | Data defined by the issuer. The value for this reply field will probably be the same as the value that you submitted in the authorization request, but it is possible for the processor, issuer, or acquirer to modify the value. This field is supported only for Visa transactions on **CyberSource through VisaNet**. For details, see `issuer_additional_data` 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]
88
**country_specific_discretionary_data** | **String** | Data defined by the issuer. This national use field contains two subfields for information unique to the processing of Visa transactions by members in Japan. This subfield contains the Katakana text to be printed on the receipt. For details, see `jpo_issuer_message` 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]
99
**response_code** | **String** | Additional authorization code that must be printed on the receipt when returned by the processor. This value is generated by the processor and is returned only for a successful transaction. This reply field is supported only for these processors: - FDC Nashville Global - SIX | [optional]
10-
**response_raw** | **String** | issuerInformation.responseRaw is the raw processor auth response returned to merchant in CYBS auth response if auth request includes \"processingInformation.isReturnAuthRecordEnabled=true\". If supported by the gateway code, it is available to merchants who auth through CYBS and run their own settlement processing. | [optional]
1110

1211

‎docs/PtsV2PayoutsPost201Response.md‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,5 +14,6 @@ Name | Type | Description | Notes
1414
**order_information** | [**PtsV2PayoutsPost201ResponseOrderInformation**](PtsV2PayoutsPost201ResponseOrderInformation.md) | | [optional]
1515
**processor_information** | [**PtsV2PayoutsPost201ResponseProcessorInformation**](PtsV2PayoutsPost201ResponseProcessorInformation.md) | | [optional]
1616
**recipient_information** | [**PtsV2PayoutsPost201ResponseRecipientInformation**](PtsV2PayoutsPost201ResponseRecipientInformation.md) | | [optional]
17+
**issuer_information** | [**PtsV2PayoutsPost201ResponseIssuerInformation**](PtsV2PayoutsPost201ResponseIssuerInformation.md) | | [optional]
1718

1819

‎docs/PtsV2PayoutsPost201ResponseIssuerInformation.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
# CyberSource::PtsV2PayoutsPost201ResponseIssuerInformation
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**service_processing_type** | **String** | This field contains values that identify the service type under which the transaction should be processed. The valid value for the Visa Alias Directory Service is A0 (Alias) and 00 (normal transaction). | [optional]
7+
8+

‎docs/Ptsv2paymentsPointOfSaleInformation.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Name | Type | Description | Notes
1818
**cardholder_verification_method** | **Array<String>** | Complete list of cardholder verification methods (CVMs) supported by the terminal. Optional field. Possible values: - `PIN`: For terminals with a PIN Pad - `Signature`: For terminals capable of receiving a signature - `pinOnGlass`: For terminals where PIN is entered on a glass-based capture mechanism **EXAMPLE**: [\"PIN\",\"Signature\"]; [\"pinOnGlass\",\"Signature\"] | [optional]
1919
**terminal_input_capability** | **Array<String>** | Complete list of card input methods supported by the terminal. Possible values: - `Keyed`: Terminal can accept card data that is entered manually. - `Swiped`: Terminal can accept card data from a magnetic stripe reader. - `Contact`: Terminal can accept card data in EMV contact mode (\"dipping a card\"). - `Contactless`: Terminal can accept card data in EMV contactless mode (\"tapping a card\"). - `BarCode`: Terminal can read bar codes. - `QRcode`: Terminal can read or scan QR codes. - `OCR`: Terminal can perform optical character recognition (OCT) on the card. **EXAMPLE**: [\"Keyed\",\"Swiped\",\"Contact\",\"Contactless\"] #### Used by **Authorization and Credit** Optional. This field is supported only by client software that is installed on your POS terminals for the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX | [optional]
2020
**terminal_card_capture_capability** | **String** | Indicates whether the terminal can capture the card. Possible values: - `1`: Terminal can capture card. - `0`: Terminal cannot capture card. For authorizations and credits, this field is supported only by these processors: - American Express Direct - Credit Mutuel-CIC - OmniPay Direct Optional field. | [optional]
21-
**terminal_output_capability** | **String** | Indicates whether the terminal can print or display messages. Possible values: - 1: Neither - 2: Print only - 3: Display only - 4: Print and display This field is supported for authorizations and credits only on the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX Optional field. | [optional]
21+
**terminal_output_capability** | **String** | Indicates whether the terminal can print or display messages. Possible values: - 1: Neither - 2: Print only - 3: Display only - 4: Print and display - 5: Merchant terminal supports purchase only approvals This field is supported for authorizations and credits only on the following processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX - VisaNet Optional field. | [optional]
2222
**terminal_pin_capability** | **Integer** | Maximum PIN length that the terminal can capture. Possible values: - 0: No PIN capture capability - 1: PIN capture capability unknown - 4: Four characters - 5: Five characters - 6: Six characters - 7: Seven characters - 8: Eight characters - 9: Nine characters - 10: Ten characters - 11: Eleven characters - 12: Twelve characters This field is supported for authorizations and credits only on the following processors: - American Express Direct - Credit Mutuel-CIC - OmniPay Direct - SIX Required field for authorization or credit of PIN transactions. | [optional]
2323
**device_id** | **String** | Value created by the client software that uniquely identifies the POS device. This value is provided by the client software that is installed on the POS terminal. CyberSource does not forward this value to the processor. Instead, the value is forwarded to the CyberSource reporting functionality. This field is supported only on American Express Direct, FDC Nashville Global, and SIX. | [optional]
2424
**pin_block_encoding_format** | **Integer** | Format that is used to encode the PIN block. This value is provided by the client software that is installed on the POS terminal. Possible values: - `0`: ISO 9564 format 0 - `1`: ISO 9564 format 1 - `2`: ISO 9564 format 2 - `3`: ISO 9564 format 3 #### Used by **Authorization, PIN Debit** - Required when the cardholder enters a PIN and the card cannot verify the PIN, which means that the issuer must verify the PIN. - Required for PIN debit credit or PIN debit purchase. For authorizations, this field is supported only on these processors: - American Express Direct - Credit Mutuel-CIC - FDC Nashville Global - OmniPay Direct - SIX This field is also supported by processors that support chip and online PIN transactions. The following table lists the EMV Cards and Cardholder Verification Methods (CVMs) that these processors support: | Processor | Chip and Offline PIN | Chip and Online PIN | Chip and Signature | | --- | --- | --- | --- | | American Express Direct | Yes | Yes | Yes | | Chase Paymentech Solutions | No | No | Yes | | Credit Mutuel-CIC | Yes | Yes | Yes | | CyberSource through VisaNet | Yes | No | Yes | | FDC Nashville Global | Yes | Yes | Yes | | GPN | No | No | Yes | | OmniPay Direct | Yes | No | Yes | | SIX | Yes | Yes | Yes | #### GPX For chip and online PIN transactions for authorization, GPX supports the following EMV Cards and Cardholder Verification Methods (CVMs): - Chip and Offline PIN - Chip and Signature For PIN Debit Purchase and Credit Service transactions, GPX supports the following EMV Cards and Cardholder Verification Methods (CVMs): - Chip and Online PIN | [optional]

0 commit comments

Comments
 (0)