5.1.0

Release 5.1.0 (#347)

This release introduces several new features and improvements to the issuing and payments domains, including expanded support for dispute handling, enhancements to card activation and revocation scheduling, and richer order/payment setup models. It also removes some deprecated or redundant classes and fields to streamline the codebase.

Issuing Disputes Enhancements:

• Added new models for handling fraud-related dispute details (IssuingDisputeFraudDetails, IssuingDisputeFraudType) and integrated them into dispute request classes, allowing for more granular and structured fraud reporting. [1] [2] [3] [4] [5] [6]
• Introduced the AmendDisputeRequest model and corresponding amendDispute method in IssuingClient, enabling amendments to disputes that are blocked or require additional information. [1] [2] [3] [4]
• Marked the submitDispute method as deprecated, guiding users towards the new dispute amendment flow.

Card Management Improvements:

• Added activation_date and revocation_date fields to both CardRequest and UpdateCardRequest classes, allowing for scheduled card activation and automatic revocation. [1] [2]
• Removed the ScheduleRevocationRequest class and related scheduling methods from IssuingClient, consolidating revocation scheduling into the main card request models. [1] [2] [3]

Payments and Order Setup Extensions:

• Enhanced the Order model with new fields for invoice_id, shipping_amount, surcharge_amount, tax_amount, tipping_amount, and amount_allocations, supporting more detailed order breakdowns.
• Added new models for PaymentSetupAmountAllocation and AmountAllocationCommission, enabling split payments and commission handling in setup flows. [1] [2]
• Introduced the PaymentSetupBillingDescriptor model for richer payment descriptions and billing information.

Account and Instrument Details:

• Added InstrumentAccountType and InstrumentDetailsAch models to support ACH payment instrument details, including account and routing numbers. [1] [2]

Cleanup and Deprecations:

• Removed the CardholderDocument class and related references from cardholder request models, simplifying cardholder data structures. [1] [2] [3] [4]

These changes collectively improve the flexibility, compliance, and functionality of the issuing and payments APIs, while also streamlining the codebase for easier maintenance.…nd Platforms instrument details)