citypay_api_client 1.1.2 → 1.1.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (167) hide show
  1. checksums.yaml +4 -4
  2. data/Gemfile.lock +73 -0
  3. data/README.md +59 -32
  4. data/citypay_api_client.gemspec +1 -1
  5. data/docs/Acknowledgement.md +2 -2
  6. data/docs/AclCheckResponseModel.md +3 -3
  7. data/docs/AuthRequest.md +7 -7
  8. data/docs/AuthResponse.md +4 -4
  9. data/docs/AuthorisationAndPaymentApi.md +75 -231
  10. data/docs/Batch.md +1 -1
  11. data/docs/BatchProcessingApi.md +11 -11
  12. data/docs/BatchReportResponseModel.md +2 -2
  13. data/docs/BatchTransaction.md +1 -1
  14. data/docs/BatchTransactionReportRequest.md +22 -0
  15. data/docs/BatchTransactionReportResponse.md +24 -0
  16. data/docs/BatchTransactionResultModel.md +1 -1
  17. data/docs/Bin.md +2 -2
  18. data/docs/CaptureRequest.md +1 -1
  19. data/docs/Card.md +2 -2
  20. data/docs/CardHolderAccountApi.md +9 -5
  21. data/docs/ChargeRequest.md +7 -7
  22. data/docs/Decision.md +0 -2
  23. data/docs/DirectPostApi.md +2 -16
  24. data/docs/DirectPostRequest.md +7 -7
  25. data/docs/EventDataModel.md +2 -2
  26. data/docs/MerchantBatchReportRequest.md +28 -0
  27. data/docs/MerchantBatchReportResponse.md +24 -0
  28. data/docs/MerchantBatchResponse.md +30 -0
  29. data/docs/NetSummaryResponse.md +32 -0
  30. data/docs/PaylinkAdjustmentRequest.md +1 -1
  31. data/docs/PaylinkApi.md +141 -1
  32. data/docs/PaylinkBillPaymentTokenRequest.md +1 -1
  33. data/docs/PaylinkErrorCode.md +2 -2
  34. data/docs/PaylinkResendNotificationRequest.md +20 -0
  35. data/docs/PaylinkStateEvent.md +4 -4
  36. data/docs/PaylinkTokenCreated.md +11 -11
  37. data/docs/PaylinkTokenStatus.md +7 -7
  38. data/docs/PaylinkTokenStatusChangeRequest.md +7 -7
  39. data/docs/PaylinkTokenStatusChangeResponse.md +6 -2
  40. data/docs/PaymentIntent.md +42 -0
  41. data/docs/PaymentIntentReference.md +18 -0
  42. data/docs/RefundRequest.md +1 -1
  43. data/docs/RemittanceData.md +28 -0
  44. data/docs/RemittanceReportRequest.md +28 -0
  45. data/docs/RemittanceReportResponse.md +24 -0
  46. data/docs/RemittedClientData.md +44 -0
  47. data/docs/ReportingApi.md +378 -0
  48. data/docs/TokenisationResponseModel.md +1 -1
  49. data/lib/.DS_Store +0 -0
  50. data/lib/citypay_api_client/api/authorisation_and_payment_api__.rb +71 -3
  51. data/lib/citypay_api_client/api/batch_processing_api__.rb +7 -7
  52. data/lib/citypay_api_client/api/card_holder_account_api__.rb +4 -1
  53. data/lib/citypay_api_client/api/direct_post_api__.rb +5 -5
  54. data/lib/citypay_api_client/api/operational_functions_api__.rb +1 -1
  55. data/lib/citypay_api_client/api/paylink_api__.rb +138 -1
  56. data/lib/citypay_api_client/api/reporting_api__.rb +381 -0
  57. data/lib/citypay_api_client/api_client.rb +1 -1
  58. data/lib/citypay_api_client/api_error.rb +1 -1
  59. data/lib/citypay_api_client/configuration.rb +1 -1
  60. data/lib/citypay_api_client/models/account_create.rb +1 -1
  61. data/lib/citypay_api_client/models/account_status.rb +1 -1
  62. data/lib/citypay_api_client/models/acknowledgement.rb +1 -29
  63. data/lib/citypay_api_client/models/acl_check_request.rb +1 -1
  64. data/lib/citypay_api_client/models/acl_check_response_model.rb +2 -2
  65. data/lib/citypay_api_client/models/airline_advice.rb +1 -1
  66. data/lib/citypay_api_client/models/airline_segment.rb +1 -1
  67. data/lib/citypay_api_client/models/auth_reference.rb +1 -1
  68. data/lib/citypay_api_client/models/auth_references.rb +1 -1
  69. data/lib/citypay_api_client/models/auth_request.rb +10 -9
  70. data/lib/citypay_api_client/models/auth_response.rb +2 -2
  71. data/lib/citypay_api_client/models/batch.rb +2 -2
  72. data/lib/citypay_api_client/models/batch_report_request.rb +1 -1
  73. data/lib/citypay_api_client/models/batch_report_response_model.rb +2 -2
  74. data/lib/citypay_api_client/models/batch_transaction.rb +1 -1
  75. data/lib/citypay_api_client/models/batch_transaction_report_request.rb +234 -0
  76. data/lib/citypay_api_client/models/batch_transaction_report_response.rb +252 -0
  77. data/lib/citypay_api_client/models/batch_transaction_result_model.rb +1 -1
  78. data/lib/citypay_api_client/models/bin.rb +1 -1
  79. data/lib/citypay_api_client/models/bin_lookup.rb +1 -1
  80. data/lib/citypay_api_client/models/c_res_auth_request.rb +1 -1
  81. data/lib/citypay_api_client/models/capture_request.rb +1 -1
  82. data/lib/citypay_api_client/models/card.rb +1 -1
  83. data/lib/citypay_api_client/models/card_holder_account.rb +1 -1
  84. data/lib/citypay_api_client/models/card_status.rb +1 -1
  85. data/lib/citypay_api_client/models/charge_request.rb +10 -9
  86. data/lib/citypay_api_client/models/check_batch_status.rb +1 -1
  87. data/lib/citypay_api_client/models/check_batch_status_response.rb +1 -1
  88. data/lib/citypay_api_client/models/contact_details.rb +1 -1
  89. data/lib/citypay_api_client/models/decision.rb +2 -11
  90. data/lib/citypay_api_client/models/direct_post_request.rb +10 -9
  91. data/lib/citypay_api_client/models/direct_token_auth_request.rb +1 -1
  92. data/lib/citypay_api_client/models/domain_key_check_request.rb +1 -1
  93. data/lib/citypay_api_client/models/domain_key_request.rb +1 -1
  94. data/lib/citypay_api_client/models/domain_key_response.rb +1 -1
  95. data/lib/citypay_api_client/models/error.rb +1 -1
  96. data/lib/citypay_api_client/models/event_data_model.rb +1 -1
  97. data/lib/citypay_api_client/models/exists.rb +1 -1
  98. data/lib/citypay_api_client/models/external_mpi.rb +1 -1
  99. data/lib/citypay_api_client/models/list_merchants_response.rb +1 -1
  100. data/lib/citypay_api_client/models/mcc6012.rb +1 -1
  101. data/lib/citypay_api_client/models/merchant.rb +1 -1
  102. data/lib/citypay_api_client/models/merchant_batch_report_request.rb +265 -0
  103. data/lib/citypay_api_client/models/merchant_batch_report_response.rb +252 -0
  104. data/lib/citypay_api_client/models/merchant_batch_response.rb +301 -0
  105. data/lib/citypay_api_client/models/net_summary_response.rb +472 -0
  106. data/lib/citypay_api_client/models/pa_res_auth_request.rb +1 -1
  107. data/lib/citypay_api_client/models/paylink_address.rb +1 -1
  108. data/lib/citypay_api_client/models/paylink_adjustment_request.rb +1 -1
  109. data/lib/citypay_api_client/models/paylink_attachment_request.rb +1 -1
  110. data/lib/citypay_api_client/models/paylink_attachment_result.rb +1 -1
  111. data/lib/citypay_api_client/models/paylink_bill_payment_token_request.rb +1 -1
  112. data/lib/citypay_api_client/models/paylink_card_holder.rb +1 -1
  113. data/lib/citypay_api_client/models/paylink_cart.rb +1 -1
  114. data/lib/citypay_api_client/models/paylink_cart_item_model.rb +1 -1
  115. data/lib/citypay_api_client/models/paylink_config.rb +1 -1
  116. data/lib/citypay_api_client/models/paylink_custom_param.rb +1 -1
  117. data/lib/citypay_api_client/models/paylink_email_notification_path.rb +1 -1
  118. data/lib/citypay_api_client/models/paylink_error_code.rb +1 -1
  119. data/lib/citypay_api_client/models/paylink_field_guard_model.rb +1 -1
  120. data/lib/citypay_api_client/models/paylink_part_payments.rb +1 -1
  121. data/lib/citypay_api_client/models/paylink_resend_notification_request.rb +224 -0
  122. data/lib/citypay_api_client/models/paylink_sms_notification_path.rb +1 -1
  123. data/lib/citypay_api_client/models/paylink_state_event.rb +2 -2
  124. data/lib/citypay_api_client/models/paylink_token_created.rb +36 -8
  125. data/lib/citypay_api_client/models/paylink_token_request_model.rb +1 -1
  126. data/lib/citypay_api_client/models/paylink_token_status.rb +30 -2
  127. data/lib/citypay_api_client/models/paylink_token_status_change_request.rb +6 -7
  128. data/lib/citypay_api_client/models/paylink_token_status_change_response.rb +23 -3
  129. data/lib/citypay_api_client/models/paylink_ui.rb +1 -1
  130. data/lib/citypay_api_client/models/payment_intent.rb +479 -0
  131. data/lib/citypay_api_client/models/payment_intent_reference.rb +221 -0
  132. data/lib/citypay_api_client/models/ping.rb +1 -1
  133. data/lib/citypay_api_client/models/process_batch_request.rb +1 -1
  134. data/lib/citypay_api_client/models/process_batch_response.rb +1 -1
  135. data/lib/citypay_api_client/models/refund_request.rb +1 -1
  136. data/lib/citypay_api_client/models/register_card.rb +1 -1
  137. data/lib/citypay_api_client/models/remittance_data.rb +404 -0
  138. data/lib/citypay_api_client/models/remittance_report_request.rb +265 -0
  139. data/lib/citypay_api_client/models/remittance_report_response.rb +252 -0
  140. data/lib/citypay_api_client/models/remitted_client_data.rb +612 -0
  141. data/lib/citypay_api_client/models/request_challenged.rb +1 -1
  142. data/lib/citypay_api_client/models/retrieve_request.rb +1 -1
  143. data/lib/citypay_api_client/models/three_d_secure.rb +1 -1
  144. data/lib/citypay_api_client/models/tokenisation_response_model.rb +1 -1
  145. data/lib/citypay_api_client/models/void_request.rb +1 -1
  146. data/lib/citypay_api_client/version.rb +2 -2
  147. data/lib/citypay_api_client.rb +15 -2
  148. data/spec/.DS_Store +0 -0
  149. data/spec/api/reporting_api___spec.rb +99 -0
  150. data/spec/it_api_sandbox_spec.rb +0 -3
  151. data/spec/models/batch_transaction_report_request_spec.rb +47 -0
  152. data/spec/models/batch_transaction_report_response_spec.rb +53 -0
  153. data/spec/models/decision_spec.rb +0 -26
  154. data/spec/models/merchant_batch_report_request_spec.rb +65 -0
  155. data/spec/models/merchant_batch_report_response_spec.rb +53 -0
  156. data/spec/models/merchant_batch_response_spec.rb +71 -0
  157. data/spec/models/net_summary_response_spec.rb +77 -0
  158. data/spec/models/paylink_resend_notification_request_spec.rb +41 -0
  159. data/spec/models/payment_intent_reference_spec.rb +35 -0
  160. data/spec/models/payment_intent_spec.rb +107 -0
  161. data/spec/models/remittance_data_spec.rb +65 -0
  162. data/spec/models/remittance_report_request_spec.rb +65 -0
  163. data/spec/models/remittance_report_response_spec.rb +53 -0
  164. data/spec/models/remitted_client_data_spec.rb +113 -0
  165. data/spec/spec_helper.rb +1 -1
  166. metadata +124 -69
  167. data/spec/models/authen_required_spec.rb +0 -52
@@ -5,10 +5,10 @@
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
7
  | **after** | **Time** | identifies the date and time to lookup changes after. | |
8
- | **max_results** | **Integer** | the maximum number of results between 5 and 250 to return. Default is 50. | [optional] |
8
+ | **max_results** | **Integer** | The maximum number of results to return in a single response. This value is used to limit the size of data returned by the API, enhancing performance and manageability. Values should be between 5 and 250. | [optional] |
9
9
  | **merchantid** | **Integer** | the merchant id to review tokens for. | |
10
- | **next_token** | **String** | the next token value when more results are available. | [optional] |
11
- | **order_by** | **Array<String>** | | [optional] |
10
+ | **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
11
+ | **order_by** | **String** | Specifies the field by which results are ordered. Available fields are [p.id]. By default, fields are ordered by OrderByExpression(p.id,ASC). To order in descending order, prefix with '-' or suffix with ' DESC'. | [optional] |
12
12
 
13
13
  ## Example
14
14
 
@@ -16,11 +16,11 @@
16
16
  require 'citypay_api_client'
17
17
 
18
18
  instance = CityPayApiClient::PaylinkTokenStatusChangeRequest.new(
19
- after: null,
20
- max_results: null,
19
+ after: 2024-04-22T13:29:14Z,
20
+ max_results: 50,
21
21
  merchantid: 11223344,
22
- next_token: null,
23
- order_by: null
22
+ next_token: n34liuwn435tUAGFNg34yn...,
23
+ order_by: date
24
24
  )
25
25
  ```
26
26
 
@@ -4,7 +4,9 @@
4
4
 
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
- | **next_token** | **String** | If nextToken is returned, there are more results available. The value of nextToken is a unique pagination token for each page. Make the call again using the returned token to retrieve the next page. Keep all other arguments unchanged. | [optional] |
7
+ | **count** | **Integer** | The count of items returned in this page. | [optional] |
8
+ | **max_results** | **Integer** | The max results requested in this page. | [optional] |
9
+ | **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
8
10
  | **tokens** | [**Array<PaylinkTokenStatus>**](PaylinkTokenStatus.md) | | |
9
11
 
10
12
  ## Example
@@ -13,7 +15,9 @@
13
15
  require 'citypay_api_client'
14
16
 
15
17
  instance = CityPayApiClient::PaylinkTokenStatusChangeResponse.new(
16
- next_token: null,
18
+ count: 25,
19
+ max_results: 50,
20
+ next_token: n34liuwn435tUAGFNg34yn...,
17
21
  tokens: null
18
22
  )
19
23
  ```
@@ -0,0 +1,42 @@
1
+ # CityPayApiClient::PaymentIntent
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **amount** | **Integer** | The amount to authorise in the lowest unit of currency with a variable length to a maximum of 12 digits. No decimal points are to be included and no divisional characters such as 1,024. The amount should be the total amount required for the transaction. For example with GBP £1,021.95 the amount value is 102195. | |
8
+ | **avs_postcode_policy** | **String** | A policy value which determines whether an AVS postcode policy is enforced or bypassed. Values are: `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account. `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS postcode numeric value does not match. `2` to bypass. Transactions that are bypassed will be allowed through even if the postcode did not match. `3` to ignore. Transactions that are ignored will bypass the result and not send postcode details for authorisation. | [optional] |
9
+ | **bill_to** | [**ContactDetails**](ContactDetails.md) | | [optional] |
10
+ | **csc** | **String** | The Card Security Code (CSC) (also known as CV2/CVV2) is normally found on the back of the card (American Express has it on the front). The value helps to identify possession of the card as it is not available within the chip or magnetic swipe. When forwarding the CSC, please ensure the value is a string as some values start with 0 and this will be stripped out by any integer parsing. The CSC number aids fraud prevention in Mail Order and Internet payments. Business rules are available on your account to identify whether to accept or decline transactions based on mismatched results of the CSC. The Payment Card Industry (PCI) requires that at no stage of a transaction should the CSC be stored. This applies to all entities handling card data. It should also not be used in any hashing process. CityPay do not store the value and have no method of retrieving the value once the transaction has been processed. For this reason, duplicate checking is unable to determine the CSC in its duplication check algorithm. | [optional] |
11
+ | **csc_policy** | **String** | A policy value which determines whether a CSC policy is enforced or bypassed. Values are: `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account. `1` for an enforced policy. Transactions that are enforced will be rejected if the CSC value does not match. `2` to bypass. Transactions that are bypassed will be allowed through even if the CSC did not match. `3` to ignore. Transactions that are ignored will bypass the result and not send the CSC details for authorisation. | [optional] |
12
+ | **currency** | **String** | The processing currency for the transaction. Will default to the merchant account currency. | [optional] |
13
+ | **duplicate_policy** | **String** | A policy value which determines whether a duplication policy is enforced or bypassed. A duplication check has a window of time set against your account within which it can action. If a previous transaction with matching values occurred within the window, any subsequent transaction will result in a T001 result. Values are `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account. `1` for an enforced policy. Transactions that are enforced will be checked for duplication within the duplication window. `2` to bypass. Transactions that are bypassed will not be checked for duplication within the duplication window. `3` to ignore. Transactions that are ignored will have the same affect as bypass. | [optional] |
14
+ | **identifier** | **String** | The identifier of the transaction to process. The value should be a valid reference and may be used to perform post processing actions and to aid in reconciliation of transactions. The value should be a valid printable string with ASCII character ranges from 0x32 to 0x127. The identifier is recommended to be distinct for each transaction such as a [random unique identifier](https://en.wikipedia.org/wiki/Universally_unique_identifier) this will aid in ensuring each transaction is identifiable. When transactions are processed they are also checked for duplicate requests. Changing the identifier on a subsequent request will ensure that a transaction is considered as different. | |
15
+ | **match_avsa** | **String** | A policy value which determines whether an AVS address policy is enforced, bypassed or ignored. Values are: `0` for the default policy (default value if not supplied). Your default values are determined by your account manager on setup of the account. `1` for an enforced policy. Transactions that are enforced will be rejected if the AVS address numeric value does not match. `2` to bypass. Transactions that are bypassed will be allowed through even if the address did not match. `3` to ignore. Transactions that are ignored will bypass the result and not send address numeric details for authorisation. | [optional] |
16
+ | **ship_to** | [**ContactDetails**](ContactDetails.md) | | [optional] |
17
+ | **tag** | **Array<String>** | | [optional] |
18
+ | **trans_info** | **String** | Further information that can be added to the transaction will display in reporting. Can be used for flexible values such as operator id. | [optional] |
19
+ | **trans_type** | **String** | The type of transaction being submitted. Normally this value is not required and your account manager may request that you set this field. | [optional] |
20
+
21
+ ## Example
22
+
23
+ ```ruby
24
+ require 'citypay_api_client'
25
+
26
+ instance = CityPayApiClient::PaymentIntent.new(
27
+ amount: 19995,
28
+ avs_postcode_policy: null,
29
+ bill_to: null,
30
+ csc: 10,
31
+ csc_policy: null,
32
+ currency: GBP,
33
+ duplicate_policy: null,
34
+ identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
35
+ match_avsa: null,
36
+ ship_to: null,
37
+ tag: null,
38
+ trans_info: null,
39
+ trans_type: null
40
+ )
41
+ ```
42
+
@@ -0,0 +1,18 @@
1
+ # CityPayApiClient::PaymentIntentReference
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **payment_intent_id** | **String** | The intent id used for future referencing of the intent. | |
8
+
9
+ ## Example
10
+
11
+ ```ruby
12
+ require 'citypay_api_client'
13
+
14
+ instance = CityPayApiClient::PaymentIntentReference.new(
15
+ payment_intent_id: p13t1111222233334444
16
+ )
17
+ ```
18
+
@@ -16,7 +16,7 @@
16
16
  require 'citypay_api_client'
17
17
 
18
18
  instance = CityPayApiClient::RefundRequest.new(
19
- amount: 3600,
19
+ amount: 19995,
20
20
  identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
21
21
  merchantid: 11223344,
22
22
  refund_ref: 8322,
@@ -0,0 +1,28 @@
1
+ # CityPayApiClient::RemittanceData
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **date_created** | **Time** | Represents the date and time when the remittance was processed. This timestamp follows the ISO 8601 format for datetime representation. | [optional] |
8
+ | **net_amount** | **Integer** | Represents the net amount after accounting for refunds. This is calculated as SalesAmount - RefundAmount and expressed in the smallest currency unit. | [optional] |
9
+ | **refund_amount** | **Integer** | The total amount refunded to customers. | [optional] |
10
+ | **refund_count** | **Integer** | The total number of refund transactions processed. This figure helps in understanding the frequency of refunds relative to sales. | [optional] |
11
+ | **sales_amount** | **Integer** | The total monetary amount of sales transactions. | [optional] |
12
+ | **sales_count** | **Integer** | Indicates the total number of sales transactions that occurred. This count provides insight into the volume of sales. | [optional] |
13
+
14
+ ## Example
15
+
16
+ ```ruby
17
+ require 'citypay_api_client'
18
+
19
+ instance = CityPayApiClient::RemittanceData.new(
20
+ date_created: 2020-01-02T18:32:28Z,
21
+ net_amount: 11874500,
22
+ refund_amount: 11874500,
23
+ refund_count: 11874500,
24
+ sales_amount: 11874500,
25
+ sales_count: 11874500
26
+ )
27
+ ```
28
+
@@ -0,0 +1,28 @@
1
+ # CityPayApiClient::RemittanceReportRequest
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **date_from** | **Date** | Start date (YYYY-MM-DD) for batch Retrieval range, inclusive. Maximum value is 3 years ago. | [optional] |
8
+ | **date_until** | **Date** | End date (YYYY-MM-DD) for batch Retrieval range, inclusive. | [optional] |
9
+ | **max_results** | **Integer** | The maximum number of results to return in a single response. This value is used to limit the size of data returned by the API, enhancing performance and manageability. Values should be between 5 and 250. | [optional] |
10
+ | **merchant_id** | **Array<Integer>** | | [optional] |
11
+ | **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
12
+ | **order_by** | **String** | Specifies the field by which results are ordered. Available fields are [trans_no,date_when,amount]. By default, fields are ordered by OrderByExpression(trans_no,ASC). To order in descending order, prefix with '-' or suffix with ' DESC'. | [optional] |
13
+
14
+ ## Example
15
+
16
+ ```ruby
17
+ require 'citypay_api_client'
18
+
19
+ instance = CityPayApiClient::RemittanceReportRequest.new(
20
+ date_from: Wed Jan 24 00:00:00 UTC 2024,
21
+ date_until: Wed Jan 31 00:00:00 UTC 2024,
22
+ max_results: 50,
23
+ merchant_id: null,
24
+ next_token: n34liuwn435tUAGFNg34yn...,
25
+ order_by: date
26
+ )
27
+ ```
28
+
@@ -0,0 +1,24 @@
1
+ # CityPayApiClient::RemittanceReportResponse
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **count** | **Integer** | The count of items returned in this page. | [optional] |
8
+ | **data** | [**Array<RemittedClientData>**](RemittedClientData.md) | | |
9
+ | **max_results** | **Integer** | The max results requested in this page. | [optional] |
10
+ | **next_token** | **String** | A token that identifies the starting point of the page of results to be returned. An empty value indicates the start of the dataset. When supplied, it is validated and used to fetch the subsequent page of results. This token is typically obtained from the response of a previous pagination request. | [optional] |
11
+
12
+ ## Example
13
+
14
+ ```ruby
15
+ require 'citypay_api_client'
16
+
17
+ instance = CityPayApiClient::RemittanceReportResponse.new(
18
+ count: 25,
19
+ data: null,
20
+ max_results: 50,
21
+ next_token: n34liuwn435tUAGFNg34yn...
22
+ )
23
+ ```
24
+
@@ -0,0 +1,44 @@
1
+ # CityPayApiClient::RemittedClientData
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **batches** | [**Array<MerchantBatchResponse>**](MerchantBatchResponse.md) | | |
8
+ | **clientid** | **String** | The client id that the remittance data is for. | [optional] |
9
+ | **date** | **Date** | The date of the remittance. | [optional] |
10
+ | **date_created** | **Time** | The date time that the remittance was created. | [optional] |
11
+ | **net_amount** | **Integer** | Represents the net amount after accounting for refunds. This is calculated as SalesAmount - RefundAmount and expressed in the smallest currency unit. | [optional] |
12
+ | **processed_amount** | **Integer** | The total monetary amount processed consisting of sale and refund transactions. | [optional] |
13
+ | **processed_count** | **Integer** | Indicates the total number of sales and refund transactions that occurred. This count provides insight into the volume of processing. | [optional] |
14
+ | **refund_amount** | **Integer** | The total amount refunded to customers. | [optional] |
15
+ | **refund_count** | **Integer** | The total number of refund transactions processed. This figure helps in understanding the frequency of refunds relative to sales. | [optional] |
16
+ | **remittances** | [**Array<RemittanceData>**](RemittanceData.md) | | |
17
+ | **sales_amount** | **Integer** | The total monetary amount of sales transactions. | [optional] |
18
+ | **sales_count** | **Integer** | Indicates the total number of sales transactions that occurred. This count provides insight into the volume of sales. | [optional] |
19
+ | **settlement_implementation** | **String** | The name of the implementation. | [optional] |
20
+ | **uuid** | **String** | The uuid of the settlement file processed on. | [optional] |
21
+
22
+ ## Example
23
+
24
+ ```ruby
25
+ require 'citypay_api_client'
26
+
27
+ instance = CityPayApiClient::RemittedClientData.new(
28
+ batches: null,
29
+ clientid: PC12345,
30
+ date: Thu Jan 02 00:00:00 UTC 2020,
31
+ date_created: 2020-01-02T18:32:28Z,
32
+ net_amount: 11874500,
33
+ processed_amount: 11874500,
34
+ processed_count: 11874500,
35
+ refund_amount: 11874500,
36
+ refund_count: 11874500,
37
+ remittances: null,
38
+ sales_amount: 11874500,
39
+ sales_count: 11874500,
40
+ settlement_implementation: null,
41
+ uuid: 123e4567-e89b-12d3-a456-426614174000
42
+ )
43
+ ```
44
+
@@ -0,0 +1,378 @@
1
+ # CityPayApiClient::ReportingApi
2
+
3
+ All URIs are relative to *https://api.citypay.com*
4
+
5
+ | Method | HTTP request | Description |
6
+ | ------ | ------------ | ----------- |
7
+ | [**batched_transaction_report_request**](ReportingApi.md#batched_transaction_report_request) | **POST** /v6/merchant-batch/{merchantid}/{batch_no}/transactions | Batch Transaction Report Request |
8
+ | [**merchant_batch_report_request**](ReportingApi.md#merchant_batch_report_request) | **POST** /v6/merchant-batch/report | Merchant Batch Report Request |
9
+ | [**merchant_batch_request**](ReportingApi.md#merchant_batch_request) | **GET** /v6/merchant-batch/{merchantid}/{batch_no} | Merchant Batch Request |
10
+ | [**remittance_range_report**](ReportingApi.md#remittance_range_report) | **POST** /v6/remittance/report/{clientid} | Remittance Report Request |
11
+ | [**remittance_report_request**](ReportingApi.md#remittance_report_request) | **GET** /v6/remittance/report/{clientid}/{date} | Remittance Date Report Request |
12
+
13
+
14
+ ## batched_transaction_report_request
15
+
16
+ > <BatchTransactionReportResponse> batched_transaction_report_request(merchantid, batch_no, batch_transaction_report_request)
17
+
18
+ Batch Transaction Report Request
19
+
20
+ Retrieves transactions available on a given batch.
21
+
22
+ ### Examples
23
+
24
+ ```ruby
25
+ require 'time'
26
+ require 'citypay_api_client'
27
+ # setup authorization
28
+ CityPayApiClient.configure do |config|
29
+ config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
30
+ end
31
+
32
+ api_instance = CityPayApiClient::ReportingApi.new
33
+ merchantid = 56 # Integer | A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account.
34
+ batch_no = 'batch_no_example' # String | The batch number that is being requested.
35
+ batch_transaction_report_request = CityPayApiClient::BatchTransactionReportRequest.new # BatchTransactionReportRequest |
36
+
37
+ begin
38
+ # Batch Transaction Report Request
39
+ result = api_instance.batched_transaction_report_request(merchantid, batch_no, batch_transaction_report_request)
40
+ p result
41
+ rescue CityPayApiClient::ApiError => e
42
+ puts "Error when calling ReportingApi->batched_transaction_report_request: #{e}"
43
+ end
44
+ ```
45
+
46
+ #### Using the batched_transaction_report_request_with_http_info variant
47
+
48
+ This returns an Array which contains the response data, status code and headers.
49
+
50
+ > <Array(<BatchTransactionReportResponse>, Integer, Hash)> batched_transaction_report_request_with_http_info(merchantid, batch_no, batch_transaction_report_request)
51
+
52
+ ```ruby
53
+ begin
54
+ # Batch Transaction Report Request
55
+ data, status_code, headers = api_instance.batched_transaction_report_request_with_http_info(merchantid, batch_no, batch_transaction_report_request)
56
+ p status_code # => 2xx
57
+ p headers # => { ... }
58
+ p data # => <BatchTransactionReportResponse>
59
+ rescue CityPayApiClient::ApiError => e
60
+ puts "Error when calling ReportingApi->batched_transaction_report_request_with_http_info: #{e}"
61
+ end
62
+ ```
63
+
64
+ ### Parameters
65
+
66
+ | Name | Type | Description | Notes |
67
+ | ---- | ---- | ----------- | ----- |
68
+ | **merchantid** | **Integer** | A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account. | |
69
+ | **batch_no** | **String** | The batch number that is being requested. | |
70
+ | **batch_transaction_report_request** | [**BatchTransactionReportRequest**](BatchTransactionReportRequest.md) | | |
71
+
72
+ ### Return type
73
+
74
+ [**BatchTransactionReportResponse**](BatchTransactionReportResponse.md)
75
+
76
+ ### Authorization
77
+
78
+ [cp-api-key](../README.md#cp-api-key)
79
+
80
+ ### HTTP request headers
81
+
82
+ - **Content-Type**: application/json, text/xml
83
+ - **Accept**: application/json, text/xml
84
+
85
+
86
+ ## merchant_batch_report_request
87
+
88
+ > <MerchantBatchReportResponse> merchant_batch_report_request(merchant_batch_report_request)
89
+
90
+ Merchant Batch Report Request
91
+
92
+ Retrieves a report of merchant batches within a specified date range.
93
+ Batches, which aggregate daily processing activities, are typically generated at `00:00` each day.
94
+ These batches play a crucial role in the settlement of funds by summarising daily transactions.
95
+
96
+
97
+ ### Examples
98
+
99
+ ```ruby
100
+ require 'time'
101
+ require 'citypay_api_client'
102
+ # setup authorization
103
+ CityPayApiClient.configure do |config|
104
+ config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
105
+ end
106
+
107
+ api_instance = CityPayApiClient::ReportingApi.new
108
+ merchant_batch_report_request = CityPayApiClient::MerchantBatchReportRequest.new # MerchantBatchReportRequest |
109
+
110
+ begin
111
+ # Merchant Batch Report Request
112
+ result = api_instance.merchant_batch_report_request(merchant_batch_report_request)
113
+ p result
114
+ rescue CityPayApiClient::ApiError => e
115
+ puts "Error when calling ReportingApi->merchant_batch_report_request: #{e}"
116
+ end
117
+ ```
118
+
119
+ #### Using the merchant_batch_report_request_with_http_info variant
120
+
121
+ This returns an Array which contains the response data, status code and headers.
122
+
123
+ > <Array(<MerchantBatchReportResponse>, Integer, Hash)> merchant_batch_report_request_with_http_info(merchant_batch_report_request)
124
+
125
+ ```ruby
126
+ begin
127
+ # Merchant Batch Report Request
128
+ data, status_code, headers = api_instance.merchant_batch_report_request_with_http_info(merchant_batch_report_request)
129
+ p status_code # => 2xx
130
+ p headers # => { ... }
131
+ p data # => <MerchantBatchReportResponse>
132
+ rescue CityPayApiClient::ApiError => e
133
+ puts "Error when calling ReportingApi->merchant_batch_report_request_with_http_info: #{e}"
134
+ end
135
+ ```
136
+
137
+ ### Parameters
138
+
139
+ | Name | Type | Description | Notes |
140
+ | ---- | ---- | ----------- | ----- |
141
+ | **merchant_batch_report_request** | [**MerchantBatchReportRequest**](MerchantBatchReportRequest.md) | | |
142
+
143
+ ### Return type
144
+
145
+ [**MerchantBatchReportResponse**](MerchantBatchReportResponse.md)
146
+
147
+ ### Authorization
148
+
149
+ [cp-api-key](../README.md#cp-api-key)
150
+
151
+ ### HTTP request headers
152
+
153
+ - **Content-Type**: application/json, text/xml
154
+ - **Accept**: application/json, text/xml
155
+
156
+
157
+ ## merchant_batch_request
158
+
159
+ > <MerchantBatchResponse> merchant_batch_request(merchantid, batch_no)
160
+
161
+ Merchant Batch Request
162
+
163
+ Retrieves a report of merchant a merchant batch for a specified batch number.
164
+
165
+ ### Examples
166
+
167
+ ```ruby
168
+ require 'time'
169
+ require 'citypay_api_client'
170
+ # setup authorization
171
+ CityPayApiClient.configure do |config|
172
+ config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
173
+ end
174
+
175
+ api_instance = CityPayApiClient::ReportingApi.new
176
+ merchantid = 56 # Integer | A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account.
177
+ batch_no = 'batch_no_example' # String | The batch number that is being requested.
178
+
179
+ begin
180
+ # Merchant Batch Request
181
+ result = api_instance.merchant_batch_request(merchantid, batch_no)
182
+ p result
183
+ rescue CityPayApiClient::ApiError => e
184
+ puts "Error when calling ReportingApi->merchant_batch_request: #{e}"
185
+ end
186
+ ```
187
+
188
+ #### Using the merchant_batch_request_with_http_info variant
189
+
190
+ This returns an Array which contains the response data, status code and headers.
191
+
192
+ > <Array(<MerchantBatchResponse>, Integer, Hash)> merchant_batch_request_with_http_info(merchantid, batch_no)
193
+
194
+ ```ruby
195
+ begin
196
+ # Merchant Batch Request
197
+ data, status_code, headers = api_instance.merchant_batch_request_with_http_info(merchantid, batch_no)
198
+ p status_code # => 2xx
199
+ p headers # => { ... }
200
+ p data # => <MerchantBatchResponse>
201
+ rescue CityPayApiClient::ApiError => e
202
+ puts "Error when calling ReportingApi->merchant_batch_request_with_http_info: #{e}"
203
+ end
204
+ ```
205
+
206
+ ### Parameters
207
+
208
+ | Name | Type | Description | Notes |
209
+ | ---- | ---- | ----------- | ----- |
210
+ | **merchantid** | **Integer** | A merchant ID (MID) for which data is requested. This field allows for filtering of the request by a specific merchant account. | |
211
+ | **batch_no** | **String** | The batch number that is being requested. | |
212
+
213
+ ### Return type
214
+
215
+ [**MerchantBatchResponse**](MerchantBatchResponse.md)
216
+
217
+ ### Authorization
218
+
219
+ [cp-api-key](../README.md#cp-api-key)
220
+
221
+ ### HTTP request headers
222
+
223
+ - **Content-Type**: Not defined
224
+ - **Accept**: application/json, text/xml
225
+
226
+
227
+ ## remittance_range_report
228
+
229
+ > <RemittanceReportResponse> remittance_range_report(clientid, remittance_report_request)
230
+
231
+ Remittance Report Request
232
+
233
+ Fetches remittance reports for financial transactions within a specified date range,
234
+ covering all client-related activities. This report consolidates all batches disbursed to a
235
+ client, with each remittance summarising the aggregation of batches leading up to settlement.
236
+ Additionally, the net remittance amount presented in the final settlement will reflect any
237
+ deductions made by the acquirer.
238
+
239
+
240
+ ### Examples
241
+
242
+ ```ruby
243
+ require 'time'
244
+ require 'citypay_api_client'
245
+ # setup authorization
246
+ CityPayApiClient.configure do |config|
247
+ config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
248
+ end
249
+
250
+ api_instance = CityPayApiClient::ReportingApi.new
251
+ clientid = 'clientid_example' # String | A client Id for which data is requested.
252
+ remittance_report_request = CityPayApiClient::RemittanceReportRequest.new # RemittanceReportRequest |
253
+
254
+ begin
255
+ # Remittance Report Request
256
+ result = api_instance.remittance_range_report(clientid, remittance_report_request)
257
+ p result
258
+ rescue CityPayApiClient::ApiError => e
259
+ puts "Error when calling ReportingApi->remittance_range_report: #{e}"
260
+ end
261
+ ```
262
+
263
+ #### Using the remittance_range_report_with_http_info variant
264
+
265
+ This returns an Array which contains the response data, status code and headers.
266
+
267
+ > <Array(<RemittanceReportResponse>, Integer, Hash)> remittance_range_report_with_http_info(clientid, remittance_report_request)
268
+
269
+ ```ruby
270
+ begin
271
+ # Remittance Report Request
272
+ data, status_code, headers = api_instance.remittance_range_report_with_http_info(clientid, remittance_report_request)
273
+ p status_code # => 2xx
274
+ p headers # => { ... }
275
+ p data # => <RemittanceReportResponse>
276
+ rescue CityPayApiClient::ApiError => e
277
+ puts "Error when calling ReportingApi->remittance_range_report_with_http_info: #{e}"
278
+ end
279
+ ```
280
+
281
+ ### Parameters
282
+
283
+ | Name | Type | Description | Notes |
284
+ | ---- | ---- | ----------- | ----- |
285
+ | **clientid** | **String** | A client Id for which data is requested. | |
286
+ | **remittance_report_request** | [**RemittanceReportRequest**](RemittanceReportRequest.md) | | |
287
+
288
+ ### Return type
289
+
290
+ [**RemittanceReportResponse**](RemittanceReportResponse.md)
291
+
292
+ ### Authorization
293
+
294
+ [cp-api-key](../README.md#cp-api-key)
295
+
296
+ ### HTTP request headers
297
+
298
+ - **Content-Type**: application/json, text/xml
299
+ - **Accept**: application/json, text/xml
300
+
301
+
302
+ ## remittance_report_request
303
+
304
+ > <RemittedClientData> remittance_report_request(clientid, date)
305
+
306
+ Remittance Date Report Request
307
+
308
+ Fetches remittance reports for financial transactions for a given date,
309
+ covering all client-related activities. This report consolidates all batches disbursed to a
310
+ client, with each remittance summarising the aggregation of batches leading up to settlement.
311
+ Additionally, the net remittance amount presented in the final settlement will reflect any
312
+ deductions made by the acquirer.
313
+
314
+ The process also supports the notion of *today* deferring the date to today's date or *latest* reflecting the
315
+ latest remittance date available.
316
+
317
+
318
+ ### Examples
319
+
320
+ ```ruby
321
+ require 'time'
322
+ require 'citypay_api_client'
323
+ # setup authorization
324
+ CityPayApiClient.configure do |config|
325
+ config.api_key['cp-api-key'] = CityPayApiClient::ApiKey.new(client_id: 'YourClientId', licence_key: 'YourLicenceKey').generate
326
+ end
327
+
328
+ api_instance = CityPayApiClient::ReportingApi.new
329
+ clientid = 'clientid_example' # String | A client Id for which data is requested.
330
+ date = 'date_example' # String | Date (YYYY-MM-DD) to filter the request for.
331
+
332
+ begin
333
+ # Remittance Date Report Request
334
+ result = api_instance.remittance_report_request(clientid, date)
335
+ p result
336
+ rescue CityPayApiClient::ApiError => e
337
+ puts "Error when calling ReportingApi->remittance_report_request: #{e}"
338
+ end
339
+ ```
340
+
341
+ #### Using the remittance_report_request_with_http_info variant
342
+
343
+ This returns an Array which contains the response data, status code and headers.
344
+
345
+ > <Array(<RemittedClientData>, Integer, Hash)> remittance_report_request_with_http_info(clientid, date)
346
+
347
+ ```ruby
348
+ begin
349
+ # Remittance Date Report Request
350
+ data, status_code, headers = api_instance.remittance_report_request_with_http_info(clientid, date)
351
+ p status_code # => 2xx
352
+ p headers # => { ... }
353
+ p data # => <RemittedClientData>
354
+ rescue CityPayApiClient::ApiError => e
355
+ puts "Error when calling ReportingApi->remittance_report_request_with_http_info: #{e}"
356
+ end
357
+ ```
358
+
359
+ ### Parameters
360
+
361
+ | Name | Type | Description | Notes |
362
+ | ---- | ---- | ----------- | ----- |
363
+ | **clientid** | **String** | A client Id for which data is requested. | |
364
+ | **date** | **String** | Date (YYYY-MM-DD) to filter the request for. | |
365
+
366
+ ### Return type
367
+
368
+ [**RemittedClientData**](RemittedClientData.md)
369
+
370
+ ### Authorization
371
+
372
+ [cp-api-key](../README.md#cp-api-key)
373
+
374
+ ### HTTP request headers
375
+
376
+ - **Content-Type**: Not defined
377
+ - **Accept**: application/json, text/xml
378
+
@@ -25,7 +25,7 @@ instance = CityPayApiClient::TokenisationResponseModel.new(
25
25
  bin_commercial: null,
26
26
  bin_debit: null,
27
27
  bin_description: Platinum Card,
28
- eci: null,
28
+ eci: 5,
29
29
  identifier: 95b857a1-5955-4b86-963c-5a6dbfc4fb95,
30
30
  maskedpan: 4***********0002,
31
31
  scheme: Visa,
data/lib/.DS_Store CHANGED
Binary file