Generate Transfers API and Webhooks

[gcatanese]

Generate Transfers API and webhooks code

🛠 Breaking Changes

Transfers API

• In AdditionalBankIdentification.cs the TypeEnum enums order has changed: the string value is still the same, but the underlying numeric index has changed

Transfer Webhooks

• In AdditionalBankIdentification.cs the TypeEnum enums order has changed: the string value is still the same, but the underlying numeric index has changed

New Features

Transfers API

• In TransactionsService add optional attribute sortOrder to GetAllTransactions method
• In TransfersService add optional attribute sortOrder to GetAllTransfers method
• In BankAccountV3 add storedPaymentMethodId attribute
• In ConfirmationTrackingData add enum accepted
• In IssuedCard add attribute threeDSecure
• In PartyIdentification add email and url attributes
• In Transfer add enums approvalExpiredand schemeAdvice
• In Transfer add attributes createdAt, executionDate
• In TransferData add enums approvalExpiredand schemeAdvice
• In TransferData add attributes createdAt, executionDate , updatedAt
• In TransferEvent add enums approvalExpiredand schemeAdvice
• In TransferInfo add attribute executionDate
• In UltimatePartyIdentification add attributes fundingInstrument, emailandurl`

Transfer Webhooks

• In BankAccountV3 add attribute storedPaymentMethodId
• In ConfirmationTrackingData add enum accepted
• In IssuedCard add attribute threeDSecure
• In PartyIdentification add attributes email and url
• In TransferData add enums approvalExpiredand schemeAdvice
• In TransferData add attributes createdAt, executionDate , updatedAt
• In TransferEvent add enums approvalExpiredand schemeAdvice

[gemini-code-assist]

Summary of Changes

Hello @gcatanese, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the Transfers API and its associated webhooks by introducing new data fields and expanding existing enumerations. These updates aim to provide more granular detail for financial transactions, including new bank identification types, improved tracking for transfer statuses, and the ability to specify 3D Secure information. The changes also include new models for execution dates and funding instruments, alongside better API query options, ultimately improving the flexibility and informational richness of the transfer system.

Highlights

• Enhanced Transfer Identification: New fields fundingInstrument in UltimatePartyIdentification and storedPaymentMethodId in BankAccountV3 have been added to provide more detailed identification for transfers.
• Expanded Enumerations: Several enumerations across models like AdditionalBankIdentification, Transfer, TransferData, TransferEvent, ConfirmationTrackingData, BankCategoryData, and PlatformPayment have been expanded to support new bank identification codes, transfer reasons (e.g., SCHEMEADVICE), and status types (e.g., accepted).
• New Data Models for Transfers: Two new data models, ExecutionDate and ThreeDSecure, have been introduced to handle scheduled transfers and include 3D Secure details within transfer information.
• Richer Party Information: The PartyIdentification model now includes email and url properties, allowing for more comprehensive counterparty information.
• Improved API Query Capabilities: A sortOrder parameter has been added to the GetAllTransactions and GetAllTransfers methods in TransactionsService and TransfersService, respectively, enhancing data retrieval flexibility.
• New Webhook Event: A new webhook event, balancePlatform.balanceAccount.balance.block.released, has been added to provide notifications when a balance block is released.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces several updates across both Transfer Webhooks and Transfers API models and services. Key changes include reordering and updating enum members in AdditionalBankIdentification (which is a breaking change due to altered integer values), refining documentation for Amount and BankCategoryData descriptions, and correcting a link in BalancePlatformNotificationResponse. New fields like storedPaymentMethodId have been added to BankAccountV3, email and url to PartyIdentification, and threeDSecure to IssuedCard. A new ExecutionDate model has been introduced, and HKLocalAccountIdentification now supports longer account numbers. The ConfirmationTrackingData and InternalReviewTrackingData models have updated status descriptions, with ConfirmationTrackingData adding an 'accepted' status. The PlatformPayment model received more detailed descriptions for its payment types. TransferData and Transfer models now include createdAt, executionDate, and updatedAt fields, with creationDate being deprecated, and new reasons (ApprovalExpired, SchemeAdvice) added to their ReasonEnum. The TransactionsService and TransfersService interfaces have been updated to include a sortOrder parameter in their GetAllTransactions and GetAllTransfers methods, respectively, which is noted as a breaking change for implementers. Additionally, FundingInstrument and ThreeDSecure models were added to the Transfers API, and UltimatePartyIdentification now includes email, url, and fundingInstrument fields.