plaid 14.0.0.beta.2 → 14.0.0.beta.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e8c05e8bb5cbfacc0902d2ba1e55caa9e598903400664b6e3af05194f9030f48
-  data.tar.gz: d91005c3e51594ffd83a0a018eeed137c4617cf34e19b6d213de72576f351925
+  metadata.gz: ee2d1cba8ea4b9a4e74f6e845826457abfb0db01c73cbd5d81385040ad88bbe8
+  data.tar.gz: c30e67570b80c0eeb2d62fb1fff537747d736a80ce8d6801c5ef7d20f98fd628
 SHA512:
-  metadata.gz: 59a640409c54e4c585dff9597c99ee9cee2283d5b48299cc800e0e5572380e468d138553eb072523e209c21963850954f74d6310e77d58e153b2f50c8d2080f6
-  data.tar.gz: 7e951849c7ddc3da52f234959c7d598fe027445d1f7931e40f170937313993449b1247abef2abc27acbb1efbdfac246dc67e62b5cc68dbf6c5af4230da30f315
+  metadata.gz: a248f03836383e29d0aea12b05f8aaf7375bc62de99531bd5b83b7c858f40f30a38b20b820b4f9031e9a453f0d43493ecb4b5da52753292233b80de02ac82e63
+  data.tar.gz: b727db3ce0953017a6cbe565fc0690fddb9173d57b67a066ccb75bea778973170de4a0a0cad0c77d7e3be81c50b56e017d354a1563c600a00ddb545e3487bf05

data/CHANGELOG.md

@@ -1,3 +1,6 @@
+# 14.0.0.beta.3
+Type fixes, see full changelog [here](https://github.com/plaid/plaid-openapi/blob/master/CHANGELOG.md).
+
 # 14.0.0.beta.1
 
 This version represents a transition in how we maintain our external client libraries. We are now using an [API spec](https://github.com/plaid/plaid-openapi) written in `OpenAPI 3.0.0` and running our definition file through [OpenAPITool's `python` generator](https://github.com/OpenAPITools/openapi-generator).

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    plaid (14.0.0.beta.2)
+    plaid (14.0.0.beta.3)
       faraday (~> 1.0, >= 1.0.1)
 
 GEM

data/Makefile

@@ -2,9 +2,9 @@ CURRENT_DIR:=$(shell pwd)
 OPENAPI_FILE:=2020-09-14.yml
 # Theres a bug in 5.0.1 for ruby generation. https://github.com/OpenAPITools/openapi-generator/issues/8677
 OPENAPI_GENERATOR_5:=docker run --rm -v $(CURRENT_DIR):/local openapitools/openapi-generator-cli:v5.0.0 generate
-OPENAPI_VERSION:=1.5.0-beta
+OPENAPI_VERSION:=1.8.0-beta
 # Ruby embeds the version in the generator where as others dont os its not possible to cat for it.
-RUBY_PACKAGE_VERSION="14.0.0.beta.2"
+RUBY_PACKAGE_VERSION=14.0.0.beta.3
 
 .PHONY: pull-openapi
 pull-openapi:
@@ -17,5 +17,5 @@ build-openapi:
 	-o local/ \
 	--global-property=apiTests=false,modelTests=false  \
 	--library=faraday \
-	-p gemName=plaid,gemRequiredRubyVersion=">= 2.7.1",gemVersion=$(RUBY_PACKAGE_VERSION) \
+	-p gemName=plaid,gemRequiredRubyVersion=">= 2.4.0",gemVersion=$(RUBY_PACKAGE_VERSION) \
 	-t local/templates/ruby

data/README.md

@@ -16,9 +16,9 @@ And then execute:
 
 Or install it yourself as:
 
-    $ gem install plaid
+    $ gem install plaid --pre
 
-The gem supports Ruby 2.7.1+ only.
+The gem supports Ruby 2.4.0+ only.
 
 ### Versioning
 

data/docs/AssetReportTransaction.md

@@ -15,7 +15,9 @@
 | **merchant_name** | **String** | The merchant name, as extracted by Plaid from the `name` field. | [optional] |
 | **location** | [**Location**](Location.md) |  | [optional] |
 | **authorized_date** | **String** | The date that the transaction was authorized. Dates are returned in an ISO 8601 format ( `YYYY-MM-DD` ). | [optional] |
+| **authorized_datetime** | **String** | Date and time when a transaction was authorized in ISO 8601 format ( `YYYY-MM-DDTHH:mm:ssZ` ).  This field is only populated for UK institutions. For institutions in other countries, will be `null`. | [optional] |
 | **date** | **String** | For pending transactions, the date that the transaction occurred; for posted transactions, the date that the transaction posted. Both dates are returned in an ISO 8601 format ( `YYYY-MM-DD` ). |  |
+| **datetime** | **String** | Date and time when a transaction was posted in ISO 8601 format ( `YYYY-MM-DDTHH:mm:ssZ` ).  This field is only populated for UK institutions. For institutions in other countries, will be `null`. | [optional] |
 | **category_id** | **String** | The ID of the category to which this transaction belongs. See [Categories](https://plaid.com/docs/#category-overview).  If the `transaction` object was returned by an Assets endpoint such as `/asset_report/get/` or `/asset_report/pdf/get`, this field will only appear in an Asset Report with Insights. | [optional] |
 | **category** | **Array<String>** | A hierarchical array of the categories to which this transaction belongs. See [Categories](https://plaid.com/docs/#category-overview).  If the `transaction` object was returned by an Assets endpoint such as `/asset_report/get/` or `/asset_report/pdf/get`, this field will only appear in an Asset Report with Insights. | [optional] |
 | **unofficial_currency_code** | **String** | The unofficial currency code associated with the transaction. Always `null` if `iso_currency_code` is non-`null`. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.  See the [currency code schema](/docs/api/accounts#currency-code-schema) for a full listing of supported `iso_currency_code`s. | [optional] |
@@ -43,7 +45,9 @@ instance = Plaid::AssetReportTransaction.new(
   merchant_name: null,
   location: null,
   authorized_date: null,
+  authorized_datetime: null,
   date: null,
+  datetime: null,
   category_id: null,
   category: null,
   unofficial_currency_code: null,

data/docs/BankTransferBalanceGetResponse.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **balance** | [**BankTransferBalance**](BankTransferBalance.md) |  |  |
-| **origination_account_id** | **String** | The ID of the origination account that this balance belongs to. | [optional] |
+| **origination_account_id** | **String** | The ID of the origination account that this balance belongs to. |  |
 | **request_id** | **String** | A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive. |  |
 
 ## Example

data/docs/ExternalPaymentSchedule.md

@@ -6,8 +6,8 @@
 | ---- | ---- | ----------- | ----- |
 | **interval** | **String** | The frequency interval of the payment. Valid values are `\"WEEKLY\"` or `\"MONTHLY\"`. |  |
 | **interval_execution_day** | **Float** | The day of the interval on which to schedule the payment.  If the payment interval is weekly, `interval_execution_day` should be an integer from 1 (Monday) to 7 (Sunday).  If the payment interval is monthly, `interval_execution_day` should be an integer indicating which day of the month to make the payment on. Integers from 1 to 28 can be used to make a payment on that day of the month. Negative integers from -1 to -5 can be used to make a payment relative to the end of the month. To make a payment on the last day of the month, use -1; to make the payment on the second-to-last day, use -2, and so on. |  |
-| **start_date** | **String** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will begin on the first `interval_execution_day` on or after the `start_date`.  If the first `interval_execution_day` on or after the start date is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make the first payment on that day, but it is not guaranteed to do so. |  |
-| **end_date** | **String** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will end on the last `interval_execution_day` on or before the `end_date`.  If the only `interval_execution_day` between the start date and the end date (inclusive) is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make a payment on that day, but it is not guaranteed to do so. | [optional] |
+| **start_date** | **Date** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will begin on the first `interval_execution_day` on or after the `start_date`.  If the first `interval_execution_day` on or after the start date is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make the first payment on that day, but it is not guaranteed to do so. |  |
+| **end_date** | **Date** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will end on the last `interval_execution_day` on or before the `end_date`.  If the only `interval_execution_day` between the start date and the end date (inclusive) is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make a payment on that day, but it is not guaranteed to do so. | [optional] |
 
 ## Example
 

data/docs/ExternalPaymentScheduleGet.md

@@ -0,0 +1,26 @@
+# Plaid::ExternalPaymentScheduleGet
+
+## Properties
+
+| Name | Type | Description | Notes |
+| ---- | ---- | ----------- | ----- |
+| **adjusted_start_date** | **Date** | The start date sent to the bank after adjusting for holidays or weekends.  Will be provided in ISO 8601 format (YYYY-MM-DD). If the start date did not require adjustment, this field will be `null`. | [optional] |
+| **interval** | **String** | The frequency interval of the payment. Valid values are `\"WEEKLY\"` or `\"MONTHLY\"`. |  |
+| **interval_execution_day** | **Float** | The day of the interval on which to schedule the payment.  If the payment interval is weekly, `interval_execution_day` should be an integer from 1 (Monday) to 7 (Sunday).  If the payment interval is monthly, `interval_execution_day` should be an integer indicating which day of the month to make the payment on. Integers from 1 to 28 can be used to make a payment on that day of the month. Negative integers from -1 to -5 can be used to make a payment relative to the end of the month. To make a payment on the last day of the month, use -1; to make the payment on the second-to-last day, use -2, and so on. |  |
+| **start_date** | **Date** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will begin on the first `interval_execution_day` on or after the `start_date`.  If the first `interval_execution_day` on or after the start date is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make the first payment on that day, but it is not guaranteed to do so. |  |
+| **end_date** | **Date** | A date in ISO 8601 format (YYYY-MM-DD). Standing order payments will end on the last `interval_execution_day` on or before the `end_date`.  If the only `interval_execution_day` between the start date and the end date (inclusive) is also the same day that `/payment_initiation/payment/create` was called, the bank *may* make a payment on that day, but it is not guaranteed to do so. | [optional] |
+
+## Example
+
+```ruby
+require 'plaid'
+
+instance = Plaid::ExternalPaymentScheduleGet.new(
+  adjusted_start_date: null,
+  interval: null,
+  interval_execution_day: null,
+  start_date: null,
+  end_date: null
+)
+```
+

data/docs/Item.md

@@ -11,7 +11,7 @@
 | **available_products** | [**Array<Products>**](Products.md) | A list of products available for the Item that have not yet been accessed. |  |
 | **billed_products** | [**Array<Products>**](Products.md) | A list of products that have been billed for the Item. Note - `billed_products` is populated in all environments but only requests in Production are billed.  |  |
 | **consent_expiration_time** | **String** | The RFC 3339 timestamp after which the consent provided by the end user will expire. Upon consent expiration, the item will enter the `ITEM_LOGIN_REQUIRED` error state. To circumvent the `ITEM_LOGIN_REQUIRED` error and maintain continuous consent, the end user can reauthenticate via Link’s update mode in advance of the consent expiration time.  Note - This is only relevant for European institutions subject to PSD2 regulations mandating a 90-day consent window. For all other institutions, this field will be null.  | [optional] |
-| **update_type** | **String** |  | [optional] |
+| **update_type** | **String** | Indicates whether an Item requires user interaction to be updated, which can be the case for Items with some forms of two-factor authentication.  `background` - Item can be updated in the background  `requires_user_authentication` - Item requires user interaction to be updated |  |
 
 ## Example
 

data/docs/ItemStatus.md

@@ -4,9 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **investments** | [**ItemStatusInvestments**](ItemStatusInvestments.md) |  | [optional] |
-| **transactions** | [**ItemStatusTransactions**](ItemStatusTransactions.md) |  | [optional] |
-| **last_webhook** | [**ItemStatusLastWebhook**](ItemStatusLastWebhook.md) |  | [optional] |
+| **investments** | **Hash<String, Object>** | Information about the last successful and failed investments update for the Item. | [optional] |
+| **transactions** | **Hash<String, Object>** | Information about the last successful and failed transactions update for the Item. | [optional] |
+| **last_webhook** | **Hash<String, Object>** | Information about the last webhook fired for the Item. | [optional] |
 
 ## Example
 

data/docs/LinkTokenCreateRequest.md

@@ -10,7 +10,7 @@
 | **language** | **String** | The language that Link should be displayed in.  Supported languages are: - English (`'en'`) - French (`'fr'`) - Spanish (`'es'`) - Dutch (`'nl'`)  When using a Link customization, the language configured here must match the setting in the customization, or the customization will not be applied. |  |
 | **country_codes** | [**Array<CountryCode>**](CountryCode.md) | Specify an array of Plaid-supported country codes using the ISO-3166-1 alpha-2 country code standard. Institutions from all listed countries will be shown.  Supported country codes are: `US`, `CA`, `ES`, `FR`, `GB`, `IE`, `NL`. Example value: `['US', 'CA']`.  If Link is launched with multiple country codes, only products that you are enabled for in all countries will be used by Link. Note that while all countries are enabled by default in Sandbox and Development, in Production only US and Canada are enabled by default. To gain access to European institutions in the Production environment, [file a product access Support ticket](https://dashboard.plaid.com/support/new/product-and-development/product-troubleshooting/request-product-access) via the Plaid dashboard. If you initialize with a European country code, your users will see the European consent panel during the Link flow.  If using a Link customization, make sure the country codes in the customization match those specified in `country_codes`. If both `country_codes` and a Link customization are used, the value in `country_codes` may override the value in the customization.  If using the Auth features Instant Match, Same-day Micro-deposits, or Automated Micro-deposits, `country_codes` must be set to `['US']`. |  |
 | **user** | [**LinkTokenCreateRequestUser**](LinkTokenCreateRequestUser.md) |  |  |
-| **products** | [**Array<Products>**](Products.md) | List of Plaid product(s) you wish to use. If launching Link in update mode, should be omitted; required otherwise. Valid products are:  `transactions`, `auth`, `identity`, `assets`, `investments`, `liabilities`, `payment_initiation`, `deposit_switch`  Example: `['auth', 'transactions']`  `balance` is *not* a valid value, the Balance product does not require explicit initalization and will automatically be initialized when any other product is initialized.  Only institutions that support *all* requested products will be shown in Link; to maximize the number of institutions listed, it is recommended to initialize Link with the minimal product set required for your use case. Additional products can be added after Link initialization by calling the relevant endpoints. For details and exceptions, see [Choosing when to initialize products](/docs/link/best-practices/#choosing-when-to-initialize-products).          In Production, you will be billed for each product that you specify when initializing Link. Note that a product cannot be removed from an Item once the Item has been initialized with that product. To stop billing on an Item for subscription-based products, such as Liabilities, Investments, and Transactions, remove the Item via `/item/remove`. | [optional] |
+| **products** | [**Array<Products>**](Products.md) | List of Plaid product(s) you wish to use. If launching Link in update mode, should be omitted; required otherwise. Valid products are:  `transactions`, `auth`, `identity`, `assets`, `investments`, `liabilities`, `payment_initiation`, `deposit_switch`  Example: `['auth', 'transactions']`  `balance` is *not* a valid value, the Balance product does not require explicit initalization and will automatically be initialized when any other product is initialized.  Only institutions that support *all* requested products will be shown in Link; to maximize the number of institutions listed, it is recommended to initialize Link with the minimal product set required for your use case. Additional products can be added after Link initialization by calling the relevant endpoints. For details and exceptions, see [Choosing when to initialize products](/docs/link/best-practices/#choosing-when-to-initialize-products).  In Production, you will be billed for each product that you specify when initializing Link. Note that a product cannot be removed from an Item once the Item has been initialized with that product. To stop billing on an Item for subscription-based products, such as Liabilities, Investments, and Transactions, remove the Item via `/item/remove`. | [optional] |
 | **webhook** | **String** | The destination URL to which any webhooks should be sent. | [optional] |
 | **access_token** | **String** | The `access_token` associated with the Item to update, used when updating or modifying an existing `access_token`. Used when launching Link in update mode, when completing the Same-day (manual) Micro-deposit flow, or (optionally) when initializing Link as part of the Payment Initiation (UK and Europe) flow. | [optional] |
 | **link_customization_name** | **String** | The name of the Link customization from the Plaid Dashboard to be applied to Link. If not specified, the `default` customization will be used. When using a Link customization, the language in the customization must match the language selected via the `language` parameter, and the countries in the customization should match the country codes selected via `country_codes`. | [optional] |

data/docs/LinkTokenCreateRequestAccountSubtypes.md

@@ -4,10 +4,10 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **depository** | [**LinkTokenCreateRequestAccountSubtypesDepository**](LinkTokenCreateRequestAccountSubtypesDepository.md) |  | [optional] |
-| **credit** | [**LinkTokenCreateRequestAccountSubtypesCredit**](LinkTokenCreateRequestAccountSubtypesCredit.md) |  | [optional] |
-| **loan** | [**LinkTokenCreateRequestAccountSubtypesLoan**](LinkTokenCreateRequestAccountSubtypesLoan.md) |  | [optional] |
-| **investment** | [**LinkTokenCreateRequestAccountSubtypesInvestment**](LinkTokenCreateRequestAccountSubtypesInvestment.md) |  | [optional] |
+| **depository** | **Hash<String, Object>** | A filter to apply to `depository`-type accounts | [optional] |
+| **credit** | **Hash<String, Object>** | A filter to apply to `credit`-type accounts | [optional] |
+| **loan** | **Hash<String, Object>** | A filter to apply to `loan`-type accounts | [optional] |
+| **investment** | **Hash<String, Object>** | A filter to apply to `investment`-type accounts | [optional] |
 
 ## Example
 

data/docs/LinkTokenCreateRequestUser.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **client_user_id** | **String** | A unique ID representing the end user. Typically this will be a user ID number from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`. |  |
+| **client_user_id** | **String** | A unique ID representing the end user. Typically this will be a user ID number from your application. Personally identifiable information, such as an email address or phone number, should not be used in the `client_user_id`. It is currently used as a means of searching logs for the given user in the Plaid Dashboard. |  |
 | **legal_name** | **String** | The user's full legal name. This is an optional field used in the [returning user experience](/docs/link/returning-user) to associate Items to the user. | [optional] |
 | **phone_number** | **String** | The user's phone number in [E.164](https://en.wikipedia.org/wiki/E.164) format. This field is optional, but required to enable the [returning user experience](/docs/link/returning-user). | [optional] |
 | **phone_number_verified_time** | **String** | The date and time the phone number was verified in ISO 8601 format (`YYYY-MM-DDThh:mm:ssZ`). This field is optional, but required to enable any [returning user experience](/docs/link/returning-user).   Only pass a verification time for a phone number that you have verified. If you have performed verification but don’t have the time, you may supply a signal value of the start of the UNIX epoch.   Example: `2020-01-01T00:00:00Z`  | [optional] |

data/docs/LinkTokenCreateResponse.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **link_token** | **String** | A `link_token`, which can be supplied to Link in order to initialize it and receive a `public_token`, which can be exchanged for an `access_token`. |  |
-| **expiration** | **Time** | The expiration date for the `link_token`, in ISO 8601 format. A `link_token` created to generate a `public_token` that will be exchanged for a new `access_token` expires after 24 hours. A `link_token` created for an existing Item (such as when updating an existing `access_token` by launching Link in update mode) expires after 30 minutes. |  |
+| **expiration** | **Time** | The expiration date for the `link_token`, in ISO 8601 format. A `link_token` created to generate a `public_token` that will be exchanged for a new `access_token` expires after 4 hours. A `link_token` created for an existing Item (such as when updating an existing `access_token` by launching Link in update mode) expires after 30 minutes. |  |
 | **request_id** | **String** | A unique identifier for the request, which can be used for troubleshooting. This identifier, like all Plaid identifiers, is case sensitive. |  |
 
 ## Example

data/docs/NullableItemStatus.md

@@ -4,9 +4,9 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **investments** | [**ItemStatusInvestments**](ItemStatusInvestments.md) |  | [optional] |
-| **transactions** | [**ItemStatusTransactions**](ItemStatusTransactions.md) |  | [optional] |
-| **last_webhook** | [**ItemStatusLastWebhook**](ItemStatusLastWebhook.md) |  | [optional] |
+| **investments** | **Hash<String, Object>** | Information about the last successful and failed investments update for the Item. | [optional] |
+| **transactions** | **Hash<String, Object>** | Information about the last successful and failed transactions update for the Item. | [optional] |
+| **last_webhook** | **Hash<String, Object>** | Information about the last webhook fired for the Item. | [optional] |
 
 ## Example
 

data/docs/PaymentInitiationPaymentGetResponse.md

@@ -10,9 +10,9 @@
 | **status** | **String** | The status of the payment.  `PAYMENT_STATUS_INPUT_NEEDED`: This is the initial state of all payments. It indicates that the payment is waiting on user input to continue processing. A payment may re-enter this state later on if further input is needed.  `PAYMENT_STATUS_PROCESSING`: The payment is currently being processed. The payment will automatically exit this state when processing is complete.  `PAYMENT_STATUS_INITIATED`: The payment has been successfully initiated and is considered complete.  `PAYMENT_STATUS_COMPLETED`: Indicates that the standing order has been successfully established. This state is only used for standing orders.  `PAYMENT_STATUS_INSUFFICIENT_FUNDS`: The payment has failed due to insufficient funds.  `PAYMENT_STATUS_FAILED`: The payment has failed to be initiated. This error is retryable once the root cause is resolved.  `PAYMENT_STATUS_BLOCKED`: The payment has been blocked. This is a retryable error.  `PAYMENT_STATUS_UNKNOWN`: The payment status is unknown. |  |
 | **recipient_id** | **String** | The ID of the recipient |  |
 | **reference** | **String** | A reference for the payment. |  |
+| **adjusted_reference** | **String** | The value of the reference sent to the bank after adjustment to pass bank validation rules. | [optional] |
 | **last_status_update** | **String** | The date and time of the last time the `status` was updated, in IS0 8601 format |  |
-| **schedule** | [**ExternalPaymentSchedule**](ExternalPaymentSchedule.md) |  | [optional] |
-| **adjusted_reference** | **String** |  | [optional] |
+| **schedule** | [**ExternalPaymentScheduleGet**](ExternalPaymentScheduleGet.md) |  | [optional] |
 
 ## Example
 
@@ -26,9 +26,9 @@ instance = Plaid::PaymentInitiationPaymentGetResponse.new(
   status: null,
   recipient_id: null,
   reference: null,
+  adjusted_reference: null,
   last_status_update: null,
-  schedule: null,
-  adjusted_reference: null
+  schedule: null
 )
 ```
 

data/docs/PaymentInitiationRecipient.md

@@ -8,7 +8,7 @@
 | **name** | **String** | The name of the recipient |  |
 | **address** | [**PaymentInitiationAddress**](PaymentInitiationAddress.md) |  |  |
 | **iban** | **String** | The International Bank Account Number (IBAN) for the recipient. | [optional] |
-| **bacs** | [**PaymentInitiationRecipientBacs**](PaymentInitiationRecipientBacs.md) |  | [optional] |
+| **bacs** | **Hash<String, Object>** |  | [optional] |
 
 ## Example
 

data/docs/PaymentStatusUpdateWebhook.md

@@ -9,6 +9,10 @@
 | **payment_id** | **String** | The `payment_id` for the payment being updated |  |
 | **new_payment_status** | **String** | The new status of the payment.  `PAYMENT_STATUS_INPUT_NEEDED`: This is the initial state of all payments. It indicates that the payment is waiting on user input to continue processing. A payment may re-enter this state later on if further input is needed.  `PAYMENT_STATUS_PROCESSING`: The payment is currently being processed. The payment will automatically exit this state when processing is complete.  `PAYMENT_STATUS_INITIATED`: The payment has been successfully initiated and is considered complete.  `PAYMENT_STATUS_COMPLETED`: Indicates that the standing order has been successfully established. This state is only used for standing orders.  `PAYMENT_STATUS_INSUFFICIENT_FUNDS`: The payment has failed due to insufficient funds.  `PAYMENT_STATUS_FAILED`: The payment has failed to be initiated. This error is retryable once the root cause is resolved.  `PAYMENT_STATUS_BLOCKED`: The payment has been blocked. This is a retryable error.  `PAYMENT_STATUS_UNKNOWN`: The payment status is unknown. |  |
 | **old_payment_status** | **String** | The previous status of the payment.  `PAYMENT_STATUS_INPUT_NEEDED`: This is the initial state of all payments. It indicates that the payment is waiting on user input to continue processing. A payment may re-enter this state later on if further input is needed.  `PAYMENT_STATUS_PROCESSING`: The payment is currently being processed. The payment will automatically exit this state when processing is complete.  `PAYMENT_STATUS_INITIATED`: The payment has been successfully initiated and is considered complete.  `PAYMENT_STATUS_COMPLETED`: Indicates that the standing order has been successfully established. This state is only used for standing orders.  `PAYMENT_STATUS_INSUFFICIENT_FUNDS`: The payment has failed due to insufficient funds.  `PAYMENT_STATUS_FAILED`: The payment has failed to be initiated. This error is retryable once the root cause is resolved.  `PAYMENT_STATUS_BLOCKED`: The payment has been blocked. This is a retryable error.  `PAYMENT_STATUS_UNKNOWN`: The payment status is unknown. |  |
+| **original_reference** | **String** | The original value of the reference when creating the payment. | [optional] |
+| **adjusted_reference** | **String** | The value of the reference sent to the bank after adjustment to pass bank validation rules. | [optional] |
+| **original_start_date** | **Date** | The original value of the `start_date` provided during the creation of a standing order. If the payment is not a standing order, this field will be `null`. | [optional] |
+| **adjusted_start_date** | **Date** | The start date sent to the bank after adjusting for holidays or weekends.  Will be provided in ISO 8601 format (YYYY-MM-DD). If the start date did not require adjustment, or if the payment is not a standing order, this field will be `null`. | [optional] |
 | **timestamp** | **String** | The timestamp of the update, in ISO 8601 format, e.g. `\"2017-09-14T14:42:19.350Z\"` |  |
 | **error** | [**Error**](Error.md) |  | [optional] |
 
@@ -23,6 +27,10 @@ instance = Plaid::PaymentStatusUpdateWebhook.new(
   payment_id: null,
   new_payment_status: null,
   old_payment_status: null,
+  original_reference: null,
+  adjusted_reference: null,
+  original_start_date: null,
+  adjusted_start_date: null,
   timestamp: null,
   error: null
 )

data/docs/PlaidApi.md

@@ -3799,7 +3799,7 @@ end
 
 Create a payment
 
-After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.
+After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.  In the Development environment, payments must be below 5 GBP / EUR. For details on any payment limits in Production, contact your Plaid Account Manager.
 
 ### Examples
 
@@ -5449,7 +5449,7 @@ Plaid.configure do |config|
 end
 
 api_instance = Plaid::PlaidApi.new
-transactions_refresh_request = Plaid::TransactionsRefreshRequest.new # TransactionsRefreshRequest | 
+transactions_refresh_request = Plaid::TransactionsRefreshRequest.new({access_token: 'access_token_example'}) # TransactionsRefreshRequest | 
 
 begin
   # Refresh transaction data

data/docs/Transaction.md

@@ -15,7 +15,9 @@
 | **merchant_name** | **String** | The merchant name, as extracted by Plaid from the `name` field. | [optional] |
 | **location** | [**Location**](Location.md) |  | [optional] |
 | **authorized_date** | **String** | The date that the transaction was authorized. Dates are returned in an ISO 8601 format ( `YYYY-MM-DD` ). | [optional] |
+| **authorized_datetime** | **String** | Date and time when a transaction was authorized in ISO 8601 format ( `YYYY-MM-DDTHH:mm:ssZ` ).  This field is only populated for UK institutions. For institutions in other countries, will be `null`. | [optional] |
 | **date** | **String** | For pending transactions, the date that the transaction occurred; for posted transactions, the date that the transaction posted. Both dates are returned in an ISO 8601 format ( `YYYY-MM-DD` ). |  |
+| **datetime** | **String** | Date and time when a transaction was posted in ISO 8601 format ( `YYYY-MM-DDTHH:mm:ssZ` ).  This field is only populated for UK institutions. For institutions in other countries, will be `null`. | [optional] |
 | **category_id** | **String** | The ID of the category to which this transaction belongs. See [Categories](https://plaid.com/docs/#category-overview).  If the `transaction` object was returned by an Assets endpoint such as `/asset_report/get/` or `/asset_report/pdf/get`, this field will only appear in an Asset Report with Insights. | [optional] |
 | **category** | **Array<String>** | A hierarchical array of the categories to which this transaction belongs. See [Categories](https://plaid.com/docs/#category-overview).  If the `transaction` object was returned by an Assets endpoint such as `/asset_report/get/` or `/asset_report/pdf/get`, this field will only appear in an Asset Report with Insights. | [optional] |
 | **unofficial_currency_code** | **String** | The unofficial currency code associated with the transaction. Always `null` if `iso_currency_code` is non-`null`. Unofficial currency codes are used for currencies that do not have official ISO currency codes, such as cryptocurrencies and the currencies of certain countries.  See the [currency code schema](/docs/api/accounts#currency-code-schema) for a full listing of supported `iso_currency_code`s. | [optional] |
@@ -41,7 +43,9 @@ instance = Plaid::Transaction.new(
   merchant_name: null,
   location: null,
   authorized_date: null,
+  authorized_datetime: null,
   date: null,
+  datetime: null,
   category_id: null,
   category: null,
   unofficial_currency_code: null,

data/docs/TransactionsRefreshRequest.md

@@ -5,7 +5,7 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **client_id** | **String** | Your Plaid API `client_id`. | [optional] |
-| **access_token** | **String** | The access token associated with the Item data is being requested for. | [optional] |
+| **access_token** | **String** | The access token associated with the Item data is being requested for. |  |
 | **secret** | **String** | Your Plaid API `secret`. | [optional] |
 
 ## Example

data/lib/plaid.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0
@@ -121,6 +121,7 @@ require 'plaid/models/employers_search_request'
 require 'plaid/models/employers_search_response'
 require 'plaid/models/error'
 require 'plaid/models/external_payment_schedule'
+require 'plaid/models/external_payment_schedule_get'
 require 'plaid/models/health_incident'
 require 'plaid/models/historical_balance'
 require 'plaid/models/historical_update_webhook'
@@ -185,9 +186,6 @@ require 'plaid/models/item_public_token_exchange_response'
 require 'plaid/models/item_remove_request'
 require 'plaid/models/item_remove_response'
 require 'plaid/models/item_status'
-require 'plaid/models/item_status_investments'
-require 'plaid/models/item_status_last_webhook'
-require 'plaid/models/item_status_transactions'
 require 'plaid/models/item_webhook_update_request'
 require 'plaid/models/item_webhook_update_response'
 require 'plaid/models/jwk_public_key'
@@ -200,10 +198,6 @@ require 'plaid/models/liability_override'
 require 'plaid/models/link_token_account_filters'
 require 'plaid/models/link_token_create_request'
 require 'plaid/models/link_token_create_request_account_subtypes'
-require 'plaid/models/link_token_create_request_account_subtypes_credit'
-require 'plaid/models/link_token_create_request_account_subtypes_depository'
-require 'plaid/models/link_token_create_request_account_subtypes_investment'
-require 'plaid/models/link_token_create_request_account_subtypes_loan'
 require 'plaid/models/link_token_create_request_deposit_switch'
 require 'plaid/models/link_token_create_request_income_verification'
 require 'plaid/models/link_token_create_request_payment_initiation'
@@ -250,7 +244,6 @@ require 'plaid/models/payment_initiation_payment_list_response'
 require 'plaid/models/payment_initiation_payment_token_create_request'
 require 'plaid/models/payment_initiation_payment_token_create_response'
 require 'plaid/models/payment_initiation_recipient'
-require 'plaid/models/payment_initiation_recipient_bacs'
 require 'plaid/models/payment_initiation_recipient_create_request'
 require 'plaid/models/payment_initiation_recipient_create_response'
 require 'plaid/models/payment_initiation_recipient_get_request'

data/lib/plaid/api/plaid_api.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0
@@ -2990,7 +2990,7 @@ module Plaid
     end
 
     # Create a payment
-    # After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.
+    # After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.  In the Development environment, payments must be below 5 GBP / EUR. For details on any payment limits in Production, contact your Plaid Account Manager.
     # @param payment_initiation_payment_create_request [PaymentInitiationPaymentCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [PaymentInitiationPaymentCreateResponse]
@@ -3000,7 +3000,7 @@ module Plaid
     end
 
     # Create a payment
-    # After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.
+    # After creating a payment recipient, you can use the `/payment_initiation/payment/create` endpoint to create a payment to that recipient.  Payments can be one-time or standing order (recurring) and can be denominated in either EUR or GBP.  If making domestic GBP-denominated payments, your recipient must have been created with BACS numbers. In general, EUR-denominated payments will be sent via SEPA Credit Transfer and GBP-denominated payments will be sent via the Faster Payments network, but the payment network used will be determined by the institution. Payments sent via Faster Payments will typically arrive immediately, while payments sent via SEPA Credit Transfer will typically arrive in one business day.  Standing orders (recurring payments) must be denominated in GBP and can only be sent to recipients in the UK. Once created, standing order payments will continue indefinitely and cannot be modified or canceled via the API. An end user can cancel or modify a standing order directly on their banking application or website, or by contacting the bank. Standing orders will follow the payment rules of the underlying rails (Faster Payments in UK). Payments can be sent Monday to Friday, excluding bank holidays. If the pre-arranged date falls on a weekend or bank holiday, the payment is made on the next working day. It is not possible to guarantee the exact time the payment will reach the recipient’s account, although at least 90% of standing order payments are sent by 6am.  In the Development environment, payments must be below 5 GBP / EUR. For details on any payment limits in Production, contact your Plaid Account Manager.
     # @param payment_initiation_payment_create_request [PaymentInitiationPaymentCreateRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(PaymentInitiationPaymentCreateResponse, Integer, Hash)>] PaymentInitiationPaymentCreateResponse data, response status code and response headers

data/lib/plaid/api_client.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0

data/lib/plaid/api_error.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0

data/lib/plaid/configuration.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0

data/lib/plaid/models/account_assets.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0

data/lib/plaid/models/account_assets_all_of.rb

@@ -3,7 +3,7 @@
 
 #The Plaid REST API. Please see https://plaid.com/docs/api for more details.
 
-The version of the OpenAPI document: 2020-09-14_1.5.3
+The version of the OpenAPI document: 2020-09-14_1.8.0
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.0