Argyle has introduced new fields to the card pay distribution configuration parameters:

• address_line1
• address_line2
• state
• city

Populating these fields in your configuration enables pay distribution updates for cards on platforms where address details are required to perform an update.

Additionally, these errors have been implemented in the pay distribution update flow to provide more accurate error messaging and troubleshooting steps for your users:

• physical_mfa_unsupported
• unsupported_bank_account_country

The Waitr integration is now live and can be accessed via the waitr Link Item.

Additionally, the krowD integration now supports the Pay Distribution Update functionality.

Argyle has added two new fields to the /pay-allocations endpoint:

• The destination_type field enables a more dynamic way of returning destination details for a pay allocation. The value of the destination_type field determines what type of destination object is returned for the pay allocation. The possible values are bank_account, card, and acss_debit.
  • As a result of introducing this field, the card object is only returned when the value of destination_type field is card. This change is part of Argyle’s initiative to continuously improve the newly-released Card pay distribution feature.
• The acss_debit object is a destination type that is introduced to enable reading pay allocations for Canadian bank accounts.

The krowD, Oasis Paychex HR and Veryable integrations are now live. krowD is powering multiple Link Items, including Darden Restaurants (darden_restaurants). Oasis Paychex HR and Veryable can be accessed via the oasis and veryable Link Items respectively.

Additionally, the Namely integration now supports the Pay Distribution Update functionality.

The Argyle team has made improvements to the Card Pay Distribution feature.

/pay-allocations endpoint:

• The card.is_default attribute has been removed.
• The card.is_platform_card attribute has been added to distinguish between platform and non-platform cards.

/link-items endpoint:

• The features.pay_distribution_card_update object has been added. It includes supported and max_allocations fields.

pd_config:

• cardholder_title is now an optional field.

• Argyle has added support for iPhone simulators on M1 MacBooks (ARM64 architecture).
• There are now even more payroll providers available to your users in the “Can’t find your employer?” questionnaire.
• Pay Distribution error messaging is now clearer, making it easier for your users to understand how they can troubleshoot issues.

Last week Argyle launched the Namely integration.

A new field has been added to the payload returned by the pay_distribution_updated webhook:

• pay_distribution_changed - Indicates whether a successful pay distribution update has resulted in any changes in the user’s pay distribution details.

Webhooks are now sourced from two different IP addresses. If you are subscribed to webhooks and use allowlists, add these IP addresses to your allowlists to avoid any issues:

• 35.188.163.115 - The existing IP address for webhooks, which you may already have on your allowlists.
• 34.122.50.253 - A new IP address for sourcing webhooks.

Last week Argyle:

• Upgraded the Paylocity integration to increase its speed dramatically. Your users should experience almost no waiting time when updating their Pay Distribution, and the team also shaved off two-thirds of the time it takes for you to receive data from this integration.
• Launched the Virtual OneStop and UKG Ready integrations.
• Upgraded the JPMorganChase integration to return previously unavailable Activities data.