Argyle has released these API improvements:

• You can now trigger errors in Sandbox mode directly in Console or via the API. Use this feature to understand and tailor error handling in your implementation. See the Sandbox guide to learn more.
• The bank_name field is now available in the bank_account object. See Pay allocations to learn more.

You can now enable instant payout to cards in the Direct deposit switching experience, even if you do not have PCI DSS compliance. Through an integration with Unit, Argyle retrieves the data needed in the background using the card_source object, without the need for you to handle sensitive data. See the documentation on the card_source object for more information.

Argyle has added the destinations array of objects to the /payouts endpoint. destinations details how the user’s net pay is distributed. See the Payouts endpoint documentation to learn more.

Argyle has introduced a major upgrade to the granularity of available user-permissioned pay data. This new data is available via the /payouts endpoint for each paystub associated with a user’s payroll account:

• An itemized breakdown of gross pay line items, available via gross_pay_list.
• Total hours and pay across five categories of gross pay: base, overtime, bonus, commission, other. These are available via gross_pay_list_totals.
• Five new year-to-date attributes: hours_ytd, deductions_ytd, taxes_ytd, deduction_list.amount_ytd, tax_list.amount_ytd.

Learn more about the structure of payout data in the Pay data structure guide. Visit the Payouts page in the API Reference for full details on all available attributes, including a sample JSON.

Also in this release:

Passing the card_name attribute when encrypting a PD config has changed from required to optional.

As part of Argyle's API improvement initiatives, the /finances endpoint has been removed. This endpoint has already been deprecated as of June 10, 2021.

Argyle recommends reviewing your implementation to ensure that you are not using this endpoint. Reach out to your Customer Success Manager if you would like to discuss alternative endpoints regarding this data.

Argyle has released two new webhooks to improve the OCR for Documents service.

These webhooks notify your system when data retrieval through OCR fails:

• forms.ocr_failed triggers for uploaded documents
• documents.ocr_failed triggers for documents scanned by Argyle from a connected account

If you have subscribed to all webhooks, you will automatically start receiving notifications when these webhooks are triggered.

As part of Argyle's API improvement initiatives, the /finances endpoint will be removed on July 1, 2022. This endpoint has already been deprecated as of June 10, 2021.

Argyle recommends reviewing your implementation to ensure that you are not using this endpoint. Reach out to your Customer Success Manager if you would like to discuss alternative endpoints regarding this data.

Argyle has added two new attributes to the /link-items endpoint:

• The features.pay_distribution_update object now returns required_fields.bank_account. This object lists the fields required by a given Link item to successfully update a pay distribution for bank accounts.
• The features.pay_distribution_card_update object now returns required_fields.card. This object lists the fields required by a given Link item to successfully update a pay distribution for cards.

• The Argyle team has added additional field and type validation when you are encrypting a pay distribution config. See Validation to learn more.
• These fields are now optional in the cardobject:
  • cardholder_first_name
  • cardholder_last_name
  • country
  • postal_code
• On June 28, Argyle is releasing two new webhooks: forms.ocr_failed and documents.ocr_failed. If you have subscribed to all webhooks, you will start receiving the forms.ocr_failed and documents.ocr_failed at this time.

Argyle has updated the accounts.pay_distribution_updated webhook. This webhook now notifies you for each successfully updated allocation that you specify in your pay distribution configuration, with separate notifications for each allocation type. The payload is extended to include information about the type of the allocation that is updated, and the type of pay distribution flow that triggered the update. Visit this webhook’s reference page for more details.

Argyle has added the missing_allocation error, which tells your users when their employment account does not have an allocation set up to allocate a remainder amount.