Skip to content

Commit af7c1ba

Browse files
gaubansagaubansa
authored
Merge pull request #134 from CyberSource/release/july25
Release/july25
2 parents a0bb120 + 241eee0 commit af7c1ba

File tree

279 files changed

+9493
-1422
lines changed

Some content is hidden

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

279 files changed

+9493
-1422
lines changed

‎cybersource_rest_client.gemspec‎

Lines changed: 1 addition & 1 deletion
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.74"
20+
s.version = "0.0.75"
2121
s.platform = Gem::Platform::RUBY
2222
s.authors = ["CyberSource"]
2323
s.email = ["[email protected]"]

‎docs/BinLookupApi.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,11 +8,11 @@ Method | HTTP request | Description
88

99

1010
# **get_account_info**
11-
> InlineResponse2011 get_account_info(create_bin_lookup_request)
11+
> InlineResponse2012 get_account_info(create_bin_lookup_request)
1212
1313
BIN Lookup API
1414

15-
The BIN Lookup Service is a versatile business tool that provides card network agnostic solution designed to ensure frictionless transaction experience by utilizing up-to-date Bank Identification Number (BIN) attributes sourced from multiple global and regional data sources. This service helps to improve authorization rates by helping to route transactions to the best-suited card network, minimizes fraud through card detail verification and aids in regulatory compliance by identifying card properties. The service is flexible and provides businesses with a flexible choice of inputs such as primary account number (PAN), network token from major networks which includes device PAN (DPAN), and all types of tokens generated via CyberSource Token Management Service (TMS). Currently, the range of available credentials is contingent on the networks enabled for the business entity. Therefore, the network information specified in this documentation is illustrative and subject to personalized offerings for each reseller or merchant.
15+
The BIN Lookup Service is a versatile business tool that provides card network agnostic solution designed to ensure frictionless transaction experience by utilizing up-to-date Bank Identification Number (BIN) attributes sourced from multiple global and regional data sources. This service helps to improve authorization rates by helping to route transactions to the best-suited card network, minimizes fraud through card detail verification and aids in regulatory compliance by identifying card properties. The service is flexible and provides businesses with a flexible choice of inputs such as primary account number (PAN), network token from major networks (such as Visa, American Express, Discover and several regional networks) which includes device PAN (DPAN), and all types of tokens generated via CyberSource Token Management Service (TMS). Currently, the range of available credentials is contingent on the networks enabled for the business entity. Therefore, the network information specified in this documentation is illustrative and subject to personalized offerings for each reseller or merchant.
1616

1717
### Example
1818
```ruby
@@ -41,7 +41,7 @@ Name | Type | Description | Notes
4141

4242
### Return type
4343

44-
[**InlineResponse2011**](InlineResponse2011.md)
44+
[**InlineResponse2012**](InlineResponse2012.md)
4545

4646
### Authorization
4747

‎docs/CreateNewWebhooksApi.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ No authorization required
5757

5858

5959
# **notification_subscriptions_v2_webhooks_post**
60-
> InlineResponse2014 notification_subscriptions_v2_webhooks_post(opts)
60+
> InlineResponse2015 notification_subscriptions_v2_webhooks_post(opts)
6161
6262
Create a New Webhook Subscription
6363

@@ -91,7 +91,7 @@ Name | Type | Description | Notes
9191

9292
### Return type
9393

94-
[**InlineResponse2014**](InlineResponse2014.md)
94+
[**InlineResponse2015**](InlineResponse2015.md)
9595

9696
### Authorization
9797

@@ -105,7 +105,7 @@ No authorization required
105105

106106

107107
# **save_sym_egress_key**
108-
> InlineResponse2013 save_sym_egress_key(v_c_sender_organization_id, v_c_permissions, opts)
108+
> InlineResponse2014 save_sym_egress_key(v_c_sender_organization_id, v_c_permissions, opts)
109109
110110
Create Webhook Security Keys
111111

@@ -147,7 +147,7 @@ Name | Type | Description | Notes
147147

148148
### Return type
149149

150-
[**InlineResponse2013**](InlineResponse2013.md)
150+
[**InlineResponse2014**](InlineResponse2014.md)
151151

152152
### Authorization
153153

‎docs/CreateOrderRequest.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,9 @@ Name | Type | Description | Notes
88
**merchant_information** | [**Ptsv2intentsMerchantInformation**](Ptsv2intentsMerchantInformation.md) | | [optional]
99
**payment_information** | [**Ptsv2intentsPaymentInformation**](Ptsv2intentsPaymentInformation.md) | | [optional]
1010
**order_information** | [**Ptsv2intentsOrderInformation**](Ptsv2intentsOrderInformation.md) | | [optional]
11+
**sender_information** | [**Ptsv2intentsSenderInformation**](Ptsv2intentsSenderInformation.md) | | [optional]
12+
**event_information** | [**Ptsv2intentsEventInformation**](Ptsv2intentsEventInformation.md) | | [optional]
13+
**travel_information** | [**Ptsv2intentsTravelInformation**](Ptsv2intentsTravelInformation.md) | | [optional]
14+
**recipient_information** | [**Ptsv2intentsRecipientInformation**](Ptsv2intentsRecipientInformation.md) | | [optional]
1115

1216

‎docs/DecisionManagerApi.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,7 +112,7 @@ No authorization required
112112

113113

114114
# **comment_decision_manager_case**
115-
> InlineResponse201 comment_decision_manager_case(id, case_management_comments_request)
115+
> InlineResponse2011 comment_decision_manager_case(id, case_management_comments_request)
116116
117117
Add a comment to a DM post-transactional case
118118

@@ -148,7 +148,7 @@ Name | Type | Description | Notes
148148

149149
### Return type
150150

151-
[**InlineResponse201**](InlineResponse201.md)
151+
[**InlineResponse2011**](InlineResponse2011.md)
152152

153153
### Authorization
154154

‎docs/InlineResponse2002.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ Name | Type | Description | Notes
77
**integration_information** | [**InlineResponse2002IntegrationInformation**](InlineResponse2002IntegrationInformation.md) | | [optional]
88
**organization_information** | [**Boardingv1registrationsOrganizationInformation**](Boardingv1registrationsOrganizationInformation.md) | | [optional]
99
**product_information** | [**Boardingv1registrationsProductInformation**](Boardingv1registrationsProductInformation.md) | | [optional]
10-
**product_information_setups** | [**Array<InlineResponse2012ProductInformationSetups>**](InlineResponse2012ProductInformationSetups.md) | | [optional]
10+
**product_information_setups** | [**Array<InlineResponse2013ProductInformationSetups>**](InlineResponse2013ProductInformationSetups.md) | | [optional]
1111
**document_information** | [**Boardingv1registrationsDocumentInformation**](Boardingv1registrationsDocumentInformation.md) | | [optional]
1212
**details** | **Hash<String, Array<Object>>** | | [optional]
1313

‎docs/InlineResponse201.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,9 @@
33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**id** | **String** | UUID uniquely generated for this comments. | [optional]
7-
**submit_time_utc** | **String** | Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services. | [optional]
8-
**status** | **String** | Status of the comment creation. Possible values are: - `COMPLETED` | [optional]
6+
**id** | **String** | An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response. | [optional]
7+
**status** | **String** | The status of the request. Possible values: - COMPLETED | [optional]
8+
**payment_information** | [**InlineResponse201PaymentInformation**](InlineResponse201PaymentInformation.md) | | [optional]
9+
**order_information** | [**InlineResponse201OrderInformation**](InlineResponse201OrderInformation.md) | | [optional]
910

1011

‎docs/InlineResponse2011.md‎

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,8 @@
33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**id** | **String** | An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response. | [optional]
6+
**id** | **String** | UUID uniquely generated for this comments. | [optional]
77
**submit_time_utc** | **String** | Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services. | [optional]
8-
**status** | **String** | The status of the submitted transaction. Possible values: - COMPLETED - MULTIPLE - NO MATCH | [optional]
9-
**payment_account_information** | [**TmsBinLookupPaymentAccountInformation**](TmsBinLookupPaymentAccountInformation.md) | | [optional]
10-
**issuer_information** | [**TmsBinLookupIssuerInformation**](TmsBinLookupIssuerInformation.md) | | [optional]
11-
**payout_information** | [**InlineResponse2011PayoutInformation**](InlineResponse2011PayoutInformation.md) | | [optional]
8+
**status** | **String** | Status of the comment creation. Possible values are: - `COMPLETED` | [optional]
129

1310

‎docs/InlineResponse2012.md‎

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,14 +3,11 @@
33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**id** | **String** | | [optional]
7-
**submit_time_utc** | **DateTime** | Time of request in UTC. `Format: YYYY-MM-DDThh:mm:ssZ` Example 2016-08-11T22:47:57Z equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The T separates the date and the time. The Z indicates UTC. | [optional]
8-
**status** | **String** | The status of Registration request Possible Values: - 'INITIALIZED' - 'RECEIVED' - 'PROCESSING' - 'SUCCESS' - 'FAILURE' - 'PARTIAL' | [optional]
9-
**registration_information** | [**InlineResponse2012RegistrationInformation**](InlineResponse2012RegistrationInformation.md) | | [optional]
10-
**integration_information** | [**InlineResponse2012IntegrationInformation**](InlineResponse2012IntegrationInformation.md) | | [optional]
11-
**organization_information** | [**InlineResponse2012OrganizationInformation**](InlineResponse2012OrganizationInformation.md) | | [optional]
12-
**product_information_setups** | [**Array<InlineResponse2012ProductInformationSetups>**](InlineResponse2012ProductInformationSetups.md) | | [optional]
13-
**message** | **String** | | [optional]
14-
**details** | **Hash<String, Array<Object>>** | | [optional]
6+
**id** | **String** | An unique identification number generated by Cybersource to identify the submitted request. Returned by all services. It is also appended to the endpoint of the resource. On incremental authorizations, this value with be the same as the identification number returned in the original authorization response. | [optional]
7+
**submit_time_utc** | **String** | Time of request in UTC. Format: `YYYY-MM-DDThh:mm:ssZ` **Example** `2016-08-11T22:47:57Z` equals August 11, 2016, at 22:47:57 (10:47:57 p.m.). The `T` separates the date and the time. The `Z` indicates UTC. Returned by Cybersource for all services. | [optional]
8+
**status** | **String** | The status of the submitted transaction. Possible values: - COMPLETED - MULTIPLE - NO MATCH | [optional]
9+
**payment_account_information** | [**TmsBinLookupPaymentAccountInformation**](TmsBinLookupPaymentAccountInformation.md) | | [optional]
10+
**issuer_information** | [**TmsBinLookupIssuerInformation**](TmsBinLookupIssuerInformation.md) | | [optional]
11+
**payout_information** | [**InlineResponse2012PayoutInformation**](InlineResponse2012PayoutInformation.md) | | [optional]
1512

1613

‎docs/InlineResponse2011PayoutInformation.md‎ renamed to ‎docs/InlineResponse2012PayoutInformation.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
1-
# CyberSource::InlineResponse2011PayoutInformation
1+
# CyberSource::InlineResponse2012PayoutInformation
22

33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**push_funds** | [**InlineResponse2011PayoutInformationPushFunds**](InlineResponse2011PayoutInformationPushFunds.md) | | [optional]
7-
**pull_funds** | [**InlineResponse2011PayoutInformationPullFunds**](InlineResponse2011PayoutInformationPullFunds.md) | | [optional]
6+
**push_funds** | [**InlineResponse2012PayoutInformationPushFunds**](InlineResponse2012PayoutInformationPushFunds.md) | | [optional]
7+
**pull_funds** | [**InlineResponse2012PayoutInformationPullFunds**](InlineResponse2012PayoutInformationPullFunds.md) | | [optional]
88
**geo_restriction_indicator** | **String** | This field indicates if the recipient issuer can accept transactions from the originator country. Possible values: - `Y` - `N` | [optional]
99

1010

0 commit comments

Comments
 (0)