External Accounts Updates by AaryamanBhute · Pull Request #202 · lightsparkdev/grid-api

AaryamanBhute · 2026-02-17T18:37:04Z

No description provided.

github-actions · 2026-02-17T18:37:34Z

✱ Stainless preview builds

This PR will update the grid SDKs with the following commit messages.

kotlin

feat: External Accounts Updates

openapi

feat(api): add 10 currency accounts, remove 7 legacy types, add originalQuoteId to quotes

python

feat(api): add BRL/DKK/GBP/HKD/IDR/INR/MXN/MYR/PHP/SGD/THB/USD/VND account types, quote field

typescript

feat(api): add BRL/DKK/GBP/HKD/IDR/INR/MXN/MYR/PHP/SGD/THB/USD/VND account types

Edit this comment to update them. They will appear in their respective SDK's changelogs.

✅ grid-openapi studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅

New diagnostics (34 note)

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

✅ grid-kotlin studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ✅ → lint ✅ → test ✅

New diagnostics (111 note)

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

✅ grid-python studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ✅ → lint ✅ → test ✅
pip install https://pkg.stainless.com/s/grid-python/d0c84c7eb073326db86d3e4de1b1b63e7bfa80e4/grid-0.0.1-py3-none-any.whl
New diagnostics (29 note)

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

✅ grid-typescript studio · code · diff

Your SDK build had at least one "note" diagnostic, but this did not represent a regression.
generate ✅ → build ✅ → lint ✅ → test ✅
npm install https://pkg.stainless.com/s/grid-typescript/d8ac654032d3c1b2372ffb2d26b5e76493be17dc/dist.tar.gz
New diagnostics (30 note)

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

💡 Schema/RequiredPropertyNotDefined: This schema marks `accountType` as `required`, but it isn't defined in `properties`, so it will be ignored.

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-02-23 02:47:38 UTC

greptile-apps · 2026-02-17T18:48:03Z

Greptile Summary

This PR migrates the external account schemas from legacy account-type-based naming (US_ACCOUNT, PIX, CLABE, IBAN, UPI) to currency-based naming (USD_ACCOUNT, BRL_ACCOUNT, MXN_ACCOUNT, etc.), expanding support to 15 currencies plus crypto wallets. It introduces beneficiary schemas for both individual and business accounts.

Key changes:

Replaced legacy account types with currency-based schemas for USD, BRL, MXN, DKK, INR, HKD, IDR, MYR, PHP, THB, and VND
Added beneficiary schemas supporting both INDIVIDUAL and BUSINESS beneficiary types
Updated discriminator mappings in BasePaymentAccountInfo and BaseExternalAccountInfo
Updated Stainless config to reference new schema names

Issues found:

UsdAccountInfo removed required accountCategory field (CHECKING/SAVINGS) and validation patterns from original UsAccountInfo - potential breaking change
Several schemas use incorrect or vague descriptions (e.g., PIX key "of the bank" should be "of the beneficiary")
IdrAccountInfo uses UK-specific sortCode terminology instead of Indonesian bankCode
Many new currency schemas lack validation patterns, examples, and specific constraints compared to well-defined schemas like GbpAccountInfo, SgdAccountInfo, and CadAccountInfo

Confidence Score: 3/5

Safe to merge with caution - contains potential breaking change for USD accounts and data quality issues
Score reflects one critical concern (missing required accountCategory field in USD schema may break existing integrations) and multiple data quality issues (incorrect terminology, vague descriptions, missing validation patterns) that reduce API usability. The schema migration itself is architecturally sound.
Pay close attention to openapi/components/schemas/common/UsdAccountInfo.yaml (potential breaking change) and schemas with terminology/validation issues: IdrAccountInfo.yaml, BrlAccountInfo.yaml, InrAccountInfo.yaml, HkdAccountInfo.yaml, DkkAccountInfo.yaml, ThbAccountInfo.yaml, VndAccountInfo.yaml, MyrAccountInfo.yaml

Important Files Changed

Filename	Overview
openapi/components/schemas/common/UsdAccountInfo.yaml	Replaced `UsAccountInfo` with simpler schema - missing required `accountCategory` field and validation patterns that existed in original
openapi/components/schemas/common/IdrAccountInfo.yaml	Uses UK-specific `sortCode` terminology for Indonesian banking - should be `bankCode`. Missing validation patterns
openapi/components/schemas/common/BrlAccountInfo.yaml	Field descriptions incorrectly attribute beneficiary data to "the bank". Missing validation patterns
openapi/components/schemas/common/InrAccountInfo.yaml	VPA description incorrectly attributes account holder property to "the bank". Missing validation patterns
openapi/components/schemas/common/HkdAccountInfo.yaml	Redundant descriptions like "bank name of the bank". Missing validation patterns and examples
openapi/components/schemas/common/DkkAccountInfo.yaml	Missing IBAN and SWIFT BIC validation patterns that would help API consumers provide correct data
openapi/components/schemas/common/ThbAccountInfo.yaml	Redundant descriptions and missing validation patterns. Same issues as HKD schema
openapi/components/schemas/common/VndAccountInfo.yaml	Missing validation patterns for Vietnamese account numbers
openapi/components/schemas/common/MyrAccountInfo.yaml	Redundant descriptions and missing validation patterns. Similar issues to THB and VND schemas
openapi/components/schemas/common/GbpAccountInfo.yaml	Good example schema with proper validation patterns, clear descriptions, and examples - sets standard for others
openapi/components/schemas/common/MxnAccountInfo.yaml	Good schema with proper CLABE validation patterns (18 digits). Clear and accurate descriptions
openapi/components/schemas/common/CadAccountInfo.yaml	Well-defined schema with proper validation for Canadian banking (institution number, transit number, account number)

Class Diagram

%%{init: {'theme': 'neutral'}}%%
classDiagram
    class BasePaymentAccountInfo {
        <<discriminator>>
        +accountType: PaymentAccountType
    }
    
    class BaseExternalAccountInfo {
        <<discriminator>>
        +accountType: ExternalAccountType
    }
    
    class CurrencyAccountInfo {
        +accountType: enum
        +countries: string[]
        +paymentRails: string[]
        +accountNumber: string
    }
    
    class BaseBeneficiary {
        <<discriminator>>
        +beneficiaryType: enum
    }
    
    class IndividualBeneficiary {
        +fullName: string
        +birthDate: string
        +nationality: string
    }
    
    class BusinessBeneficiary {
        +legalName: string
        +registrationNumber: string
        +taxId: string
    }
    
    class ExternalAccountInfo {
        +beneficiary: Beneficiary
    }
    
    BasePaymentAccountInfo <|-- UsdAccountInfo
    BasePaymentAccountInfo <|-- BrlAccountInfo
    BasePaymentAccountInfo <|-- MxnAccountInfo
    BasePaymentAccountInfo <|-- DkkAccountInfo
    BasePaymentAccountInfo <|-- InrAccountInfo
    
    CurrencyAccountInfo <|-- UsdAccountInfo
    CurrencyAccountInfo <|-- BrlAccountInfo
    CurrencyAccountInfo <|-- MxnAccountInfo
    
    BaseExternalAccountInfo <|-- ExternalAccountInfo
    CurrencyAccountInfo <|-- ExternalAccountInfo
    
    ExternalAccountInfo --> BaseBeneficiary
    BaseBeneficiary <|-- IndividualBeneficiary
    BaseBeneficiary <|-- BusinessBeneficiary
    
    note for BasePaymentAccountInfo "15 currency types:\nUSD, BRL, MXN, DKK, INR,\nNGN, CAD, GBP, HKD, IDR,\nMYR, PHP, SGD, THB, VND"
    
    note for ExternalAccountInfo "External accounts add\nbeneficiary information\nto base account schemas"

_{Last reviewed commit: 66e48c5}

greptile-apps

_{54 files reviewed, 7 comments}

_{Edit Code Review Agent Settings | Greptile}

openapi/components/schemas/common/UsdAccountInfo.yaml

openapi/components/schemas/common/IdrAccountInfo.yaml

openapi/components/schemas/common/BrlAccountInfo.yaml

openapi/components/schemas/common/InrAccountInfo.yaml

openapi/components/schemas/common/HkdAccountInfo.yaml

greptile-apps · 2026-02-17T18:48:24Z

Additional Comments (2)

openapi/paths/customers/customers_external_accounts.yaml
Stale example using removed account type

This example still uses accountType: US_ACCOUNT with accountCategory: CHECKING and bankName, but this PR removes US_ACCOUNT from the ExternalAccountType enum and replaces it with USD_ACCOUNT. The new UsdAccountInfo schema does not include accountCategory or bankName fields.

This example will now fail validation against the updated schema. It needs to be updated to use the new USD_ACCOUNT type and only include the fields defined in UsdAccountInfo (accountNumber, routingNumber).

                accountType: USD_ACCOUNT
                accountNumber: "12345678901"
                routingNumber: "123456789"

Prompt To Fix With AI

This is a comment left during a code review.
Path: openapi/paths/customers/customers_external_accounts.yaml
Line: 127:131

Comment:
**Stale example using removed account type**

This example still uses `accountType: US_ACCOUNT` with `accountCategory: CHECKING` and `bankName`, but this PR removes `US_ACCOUNT` from the `ExternalAccountType` enum and replaces it with `USD_ACCOUNT`. The new `UsdAccountInfo` schema does not include `accountCategory` or `bankName` fields.

This example will now fail validation against the updated schema. It needs to be updated to use the new `USD_ACCOUNT` type and only include the fields defined in `UsdAccountInfo` (`accountNumber`, `routingNumber`).

```suggestion
                accountType: USD_ACCOUNT
                accountNumber: "12345678901"
                routingNumber: "123456789"
```

How can I resolve this? If you propose a fix, please make it concise.

openapi/paths/platform/platform_external_accounts.yaml
Stale example using removed account type

Same issue as in customers_external_accounts.yaml: this example uses accountType: US_ACCOUNT with accountCategory: CHECKING and bankName, but US_ACCOUNT is no longer a valid ExternalAccountType value in this PR, and the new UsdAccountInfo schema does not include accountCategory or bankName.

                accountType: USD_ACCOUNT
                accountNumber: "12345678901"
                routingNumber: "123456789"

Prompt To Fix With AI

This is a comment left during a code review.
Path: openapi/paths/platform/platform_external_accounts.yaml
Line: 89:93

Comment:
**Stale example using removed account type**

Same issue as in `customers_external_accounts.yaml`: this example uses `accountType: US_ACCOUNT` with `accountCategory: CHECKING` and `bankName`, but `US_ACCOUNT` is no longer a valid `ExternalAccountType` value in this PR, and the new `UsdAccountInfo` schema does not include `accountCategory` or `bankName`.

```suggestion
                accountType: USD_ACCOUNT
                accountNumber: "12345678901"
                routingNumber: "123456789"
```

How can I resolve this? If you propose a fix, please make it concise.

greptile-apps

_{82 files reviewed, 4 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-20T18:47:00Z

openapi/components/schemas/common/DkkAccountInfo.yaml

+    type: string
+    description: The IBAN of the bank
+  swiftBic:
+    type: string
+    description: The SWIFT BIC of the bank


Missing validation patterns and examples for IBAN and SWIFT BIC. Compare with GbpAccountInfo:27-36 which includes proper validation patterns, examples, and specific constraints (e.g., pattern: ^[A-Z]{4}[A-Z]{2}[A-Z0-9]{2}([A-Z0-9]{3})?$ for SWIFT code).

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/DkkAccountInfo.yaml Line: 26-30 Comment: Missing validation patterns and examples for IBAN and SWIFT BIC. Compare with `GbpAccountInfo:27-36` which includes proper validation patterns, examples, and specific constraints (e.g., `pattern: ^[A-Z]{4}[A-Z]{2}[A-Z0-9]{2}([A-Z0-9]{3})?$` for SWIFT code). How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T18:47:03Z

openapi/components/schemas/common/ThbAccountInfo.yaml

+    type: string
+    description: The bank name of the bank
+  accountNumber:
+    type: string
+    description: The account number of the bank


Same redundant description issue as HkdAccountInfo - "bank name of the bank" and "account number of the bank". Also missing validation patterns and examples. Compare with NgnAccountInfo:26-34 which has precise descriptions, validation patterns, and examples.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/ThbAccountInfo.yaml Line: 26-30 Comment: Same redundant description issue as `HkdAccountInfo` - "bank name of the bank" and "account number of the bank". Also missing validation patterns and examples. Compare with `NgnAccountInfo:26-34` which has precise descriptions, validation patterns, and examples. Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time! How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T18:47:04Z

openapi/components/schemas/common/VndAccountInfo.yaml

+    type: string
+    description: The bank name of the bank
+  accountNumber:
+    type: string
+    description: The account number of the bank


Missing validation patterns and examples. Consider adding specific constraints if Vietnamese bank account numbers have a standard format.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/VndAccountInfo.yaml Line: 26-30 Comment: Missing validation patterns and examples. Consider adding specific constraints if Vietnamese bank account numbers have a standard format. Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time! How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T18:47:06Z

openapi/components/schemas/common/MyrAccountInfo.yaml

+    type: string
+    description: The bank name of the bank
+  accountNumber:
+    type: string
+    description: The account number of the bank


Redundant descriptions and missing validation patterns. Same issues as ThbAccountInfo and VndAccountInfo.

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/MyrAccountInfo.yaml Line: 26-30 Comment: Redundant descriptions and missing validation patterns. Same issues as `ThbAccountInfo` and `VndAccountInfo`. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps

_{83 files reviewed, 5 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-20T19:01:18Z

openapi/components/schemas/common/UsdAccountInfo.yaml

+  accountNumber:
+    type: string
+    description: The account number of the bank
+  routingNumber:
+    type: string
+    description: The routing number of the bank


Missing validation patterns and examples. The original UsAccountInfo included:

routingNumber with minLength: 9, maxLength: 9, pattern: ^[0-9]{9}$, and example

accountNumber with example

More precise descriptions

Also, the required accountCategory field (CHECKING/SAVINGS) was removed - confirm this isn't a breaking change for existing integrations.

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/UsdAccountInfo.yaml Line: 28-33 Comment: Missing validation patterns and examples. The original `UsAccountInfo` included: - `routingNumber` with `minLength: 9`, `maxLength: 9`, `pattern: ^[0-9]{9}$`, and example - `accountNumber` with example - More precise descriptions Also, the required `accountCategory` field (CHECKING/SAVINGS) was removed - confirm this isn't a breaking change for existing integrations. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T19:01:19Z

openapi/components/schemas/common/IdrAccountInfo.yaml

+  sortCode:
+    type: string
+    description: The sort code of the bank


sortCode is UK-specific banking terminology. Indonesian banks use "bank code" (kode bank) for routing. Rename to bankCode for accuracy.

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/IdrAccountInfo.yaml Line: 25-27 Comment: `sortCode` is UK-specific banking terminology. Indonesian banks use "bank code" (kode bank) for routing. Rename to `bankCode` for accuracy. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T19:01:20Z

openapi/components/schemas/common/BrlAccountInfo.yaml

+  pixKey:
+    type: string
+    description: The PIX key of the bank
+  pixKeyType:
+    type: string
+    description: The type of PIX key of the bank
+  taxId:
+    type: string
+    description: The tax ID of the bank account


Descriptions incorrectly attribute account holder data to "the bank". PIX keys and tax IDs belong to the beneficiary/account holder, not the bank. Compare with GbpAccountInfo:27 which uses precise language like "UK bank sort code".

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/BrlAccountInfo.yaml Line: 26-34 Comment: Descriptions incorrectly attribute account holder data to "the bank". PIX keys and tax IDs belong to the beneficiary/account holder, not the bank. Compare with `GbpAccountInfo:27` which uses precise language like "UK bank sort code". How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T19:01:21Z

openapi/components/schemas/common/HkdAccountInfo.yaml

+  bankName:
+    type: string
+    description: The bank name of the bank
+  accountNumber:
+    type: string
+    description: The account number of the bank


Redundant descriptions: "bank name of the bank" and "account number of the bank". Use clearer phrasing like SgdAccountInfo:30 ("Name of the beneficiary's bank") and add validation patterns/examples.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/HkdAccountInfo.yaml Line: 25-30 Comment: Redundant descriptions: "bank name of the bank" and "account number of the bank". Use clearer phrasing like `SgdAccountInfo:30` ("Name of the beneficiary's bank") and add validation patterns/examples. Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time! How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-02-20T19:01:22Z

openapi/components/schemas/common/DkkAccountInfo.yaml

+    type: string
+    description: The IBAN of the bank
+  swiftBic:
+    type: string
+    description: The SWIFT BIC of the bank


Missing validation patterns for IBAN and SWIFT BIC. Reference GbpAccountInfo:29 and SgdAccountInfo:33-38 which include proper patterns, length constraints, and examples.

Prompt To Fix With AI

This is a comment left during a code review. Path: openapi/components/schemas/common/DkkAccountInfo.yaml Line: 26-30 Comment: Missing validation patterns for IBAN and SWIFT BIC. Reference `GbpAccountInfo:29` and `SgdAccountInfo:33-38` which include proper patterns, length constraints, and examples. How can I resolve this? If you propose a fix, please make it concise.

Co-authored-by: Cursor <cursoragent@cursor.com>

Added beneficiary name verification fields to the External Account schema. - Added a new `BeneficiaryVerificationStatus` enum with values: `MATCHED`, `PARTIAL_MATCH`, `NOT_MATCHED`, `UNSUPPORTED`, `CHECKED_BY_RECEIVING_FI`, and `PENDING` - Added a new `VerifiedBeneficiaryData` object schema with a `fullName` property - Extended the `ExternalAccount` schema to include: - `beneficiaryVerificationStatus` field to indicate the result of name verification - `beneficiaryVerifiedData` field to store verified account holder information 1. Create an external account with a beneficiary name 2. Verify that the API returns the appropriate verification status and verified data 3. Test each possible verification status to ensure proper handling This change enables beneficiary name verification for external accounts, which helps prevent misdirected payments by confirming that the account holder name matches the expected beneficiary. This feature enhances security and reduces the risk of fraud or errors when sending payments to external accounts.

Co-authored-by: Cursor <cursoragent@cursor.com>

Update stale references to old payment-method-based schema names (UsAccountExternalAccountInfo, PaymentClabeAccountInfo, etc.) and remove BaseBeneficiary transform that no longer matches bundled output. Co-authored-by: Cursor <cursoragent@cursor.com>

Co-authored-by: Cursor <cursoragent@cursor.com>

AaryamanBhute force-pushed the changes-present branch from 780647d to 2032fbc Compare February 17, 2026 18:41

greptile-apps bot reviewed Feb 17, 2026

View reviewed changes

AaryamanBhute force-pushed the changes-present branch from d5016b7 to 7fcddff Compare February 20, 2026 18:42

greptile-apps bot reviewed Feb 20, 2026

View reviewed changes

pengying approved these changes Feb 20, 2026

View reviewed changes

AaryamanBhute and others added 7 commits February 22, 2026 18:39

updates

5bf549d

Co-authored-by: Cursor <cursoragent@cursor.com>

add

8a9ca97

updates

32cadfe

Co-authored-by: Cursor <cursoragent@cursor.com>

remove old and update payment instructions

af19932

chore: regenerate bundled OpenAPI spec after rebase

66e48c5

Co-authored-by: Cursor <cursoragent@cursor.com>

AaryamanBhute force-pushed the changes-present branch from 1460f90 to 66e48c5 Compare February 23, 2026 02:39

Comments

Conversation

AaryamanBhute commented Feb 17, 2026

Uh oh!

github-actions bot commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✱ Stainless preview builds

Uh oh!

greptile-apps bot commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 3/5

Important Files Changed

Class Diagram

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps bot commented Feb 17, 2026

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

github-actions bot commented Feb 17, 2026 •

edited

Loading

greptile-apps bot commented Feb 17, 2026 •

edited

Loading