Skip to content

Commit 78ccf98

Browse files
gnongsiegnongsie
authored
Merge pull request #88 from CyberSource/april-release
April release
2 parents 5c7a1c6 + 65a0ad4 commit 78ccf98

16 files changed

+794
-22
lines changed

‎docs/CreateSharedSecretKeysVerifiRequest.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
# CyberSource.CreateSharedSecretKeysVerifiRequest
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**clientReferenceInformation** | [**Kmsv2keyssymClientReferenceInformation**](Kmsv2keyssymClientReferenceInformation.md) | | [optional]
7+
**keyInformation** | [**[Kmsv2keyssymverifiKeyInformation]**](Kmsv2keyssymverifiKeyInformation.md) | | [optional]
8+
9+

‎docs/Kmsv2keyssymverifiKeyInformation.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
# CyberSource.Kmsv2keyssymverifiKeyInformation
2+
3+
## Properties
4+
Name | Type | Description | Notes
5+
------------ | ------------- | ------------- | -------------
6+
**organizationId** | **String** | Merchant Id |
7+
**referenceNumber** | **String** | Reference number is a unique identifier provided by the client along with the organization Id. This is an optional field provided solely for the client’s convenience. If client specifies value for this field in the request, it is expected to be available in the response. | [optional]
8+
**digestAlgorithm** | **String** | Algorithm for message signature authentication | [optional] [default to 'HMACSHA2']
9+
10+
11+
<a name="DigestAlgorithmEnum"></a>
12+
## Enum: DigestAlgorithmEnum
13+
14+
15+
* `HMACSHA1` (value: `"HMACSHA1"`)
16+
17+
* `HMACSHA2` (value: `"HMACSHA2"`)
18+
19+
20+
21+

‎docs/Ptsv2paymentsProcessingInformationAuthorizationOptionsInitiator.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
66
**type** | **String** | This field indicates whether the transaction is a merchant-initiated transaction or customer-initiated transaction. Valid values: - **customer** - **merchant** | [optional]
77
**credentialStoredOnFile** | **Boolean** | Indicates to the issuing bank two things: - The merchant has received consent from the cardholder to store their card details on file - The merchant wants the issuing bank to check out the card details before the merchant initiates their first transaction for this cardholder. The purpose of the merchant-initiated transaction is to ensure that the cardholder’s credentials are valid (that the card is not stolen or has restrictions) and that the card details are good to be stored on the merchant’s file for future transactions. Valid values: - &#x60;true&#x60; means merchant will use this transaction to store payment credentials for follow-up merchant-initiated transactions. - &#x60;false&#x60; means merchant will not use this transaction to store payment credentials for follow-up merchant-initiated transactions. For details, see &#x60;subsequent_auth_first&#x60; 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/) **NOTE:** The value for this field does not correspond to any data in the TC 33 capture file5. This field is supported only for Visa transactions on CyberSource through VisaNet. | [optional]
8-
**storedCredentialUsed** | **Boolean** | Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file. Possible values: - **true** means the merchant-initiated transaction came from a card that was already stored on file. - **false** means the merchant-initiated transaction came from a card that was not stored on file. | [optional]
8+
**storedCredentialUsed** | **String** | Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file. Possible values: - **Y** means the merchant-initiated transaction came from a card that was already stored on file. - **N** means the merchant-initiated transaction came from a card that was not stored on file. | [optional]
99
**merchantInitiatedTransaction** | [**Ptsv2paymentsProcessingInformationAuthorizationOptionsInitiatorMerchantInitiatedTransaction**](Ptsv2paymentsProcessingInformationAuthorizationOptionsInitiatorMerchantInitiatedTransaction.md) | | [optional]
1010

1111

‎docs/Ptsv2paymentsidProcessingInformationAuthorizationOptionsInitiator.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,6 @@
33
## Properties
44
Name | Type | Description | Notes
55
------------ | ------------- | ------------- | -------------
6-
**storedCredentialUsed** | **Boolean** | Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file. Possible values: - **true** means the merchant-initiated transaction came from a card that was already stored on file. - **false** means the merchant-initiated transaction came from a card that was not stored on file. | [optional]
6+
**storedCredentialUsed** | **String** | Indicates to an issuing bank whether a merchant-initiated transaction came from a card that was already stored on file. Possible values: - **Y** means the merchant-initiated transaction came from a card that was already stored on file. - **N** means the merchant-initiated transaction came from a card that was not stored on file. | [optional]
77

88

‎docs/SymmetricKeyManagementApi.md

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ All URIs are relative to *https://apitest.cybersource.com*
55
Method | HTTP request | Description
66
------------- | ------------- | -------------
77
[**createV2SharedSecretKeys**](SymmetricKeyManagementApi.md#createV2SharedSecretKeys) | **POST** /kms/v2/keys-sym | Create Shared-Secret Keys
8+
[**createV2SharedSecretKeysVerifi**](SymmetricKeyManagementApi.md#createV2SharedSecretKeysVerifi) | **POST** /kms/v2/keys-sym/verifi | Create Shared-Secret Keys as per verifi spec
89
[**deleteBulkSymmetricKeys**](SymmetricKeyManagementApi.md#deleteBulkSymmetricKeys) | **POST** /kms/v2/keys-sym/deletes | Delete one or more Symmetric keys
910
[**getKeyDetails**](SymmetricKeyManagementApi.md#getKeyDetails) | **GET** /kms/v2/keys-sym/{keyId} | Retrieves shared secret key details
1011

@@ -50,6 +51,55 @@ Name | Type | Description | Notes
5051

5152
No authorization required
5253

54+
### HTTP request headers
55+
56+
- **Content-Type**: application/json;charset=utf-8
57+
- **Accept**: application/hal+json;charset=utf-8
58+
59+
<a name="createV2SharedSecretKeysVerifi"></a>
60+
# **createV2SharedSecretKeysVerifi**
61+
> KmsV2KeysSymPost201Response createV2SharedSecretKeysVerifi(vIcDomain, createSharedSecretKeysVerifiRequest)
62+
63+
Create Shared-Secret Keys as per verifi spec
64+
65+
Create one or more Shared-Secret Keys as per Verifi spec with 32 chars, store digest algo during key generation.
66+
67+
### Example
68+
```javascript
69+
var CyberSource = require('CyberSource');
70+
71+
var apiInstance = new CyberSource.SymmetricKeyManagementApi();
72+
73+
var vIcDomain = "vIcDomain_example"; // String | domain
74+
75+
var createSharedSecretKeysVerifiRequest = new CyberSource.CreateSharedSecretKeysVerifiRequest(); // CreateSharedSecretKeysVerifiRequest |
76+
77+
78+
var callback = function(error, data, response) {
79+
if (error) {
80+
console.error(error);
81+
} else {
82+
console.log('API called successfully. Returned data: ' + data);
83+
}
84+
};
85+
apiInstance.createV2SharedSecretKeysVerifi(vIcDomain, createSharedSecretKeysVerifiRequest, callback);
86+
```
87+
88+
### Parameters
89+
90+
Name | Type | Description | Notes
91+
------------- | ------------- | ------------- | -------------
92+
**vIcDomain** | **String**| domain |
93+
**createSharedSecretKeysVerifiRequest** | [**CreateSharedSecretKeysVerifiRequest**](CreateSharedSecretKeysVerifiRequest.md)| |
94+
95+
### Return type
96+
97+
[**KmsV2KeysSymPost201Response**](KmsV2KeysSymPost201Response.md)
98+
99+
### Authorization
100+
101+
No authorization required
102+
53103
### HTTP request headers
54104

55105
- **Content-Type**: application/json;charset=utf-8

0 commit comments

Comments
 (0)