release: 1.9.0 by stainless-app[bot] · Pull Request #20 · lightsparkdev/grid-js-sdk

stainless-app · 2026-05-28T22:42:50Z

Automated Release PR

1.9.0 (2026-07-02)

Full Changelog: v1.8.0...v1.9.0

Features

Add encrypted OTP flow (948a93b)
api: add BANK_TRANSFER rail support to CNY accounts with accountNumber field (d0e7b9a)
api: add bankName field to GTQ/JMD external accounts (5c5c59c)
api: add card transaction type to transaction union responses (5f7a560)
api: add CNY_ACCOUNT support to external accounts (98235f5)
api: add CNY_ACCOUNT support to external accounts and payment instructions (2a4c89d)
api: add contactVerification field to customer responses (6798574)
api: add direction field to transaction responses (8eea143)
api: add FAMILY_SUPPORT and SALARY_PAYMENT to quotes purpose field (2a7f1a0)
api: add ID_TYPE and ID_NUMBER to CustomerInfoFieldName enum (51b3b49)
api: add identifier and idType fields to customers create (21e8cea)
api: add payment rail enum values to transfer-out operations (c4a11cd)
api: add PENDING_AUTH state to cards (225d436)
api: add phoneNumber field to customers create/update/response (7c9470b)
api: add processorRef field to cards (83719ec)
api: add receiptDeliveryConfirmedAt to transaction responses (c6d1dba)
api: add remittanceInformation param to transferOut and agents.me methods (9bd9746)
api: add settlement timing and rail fields to outgoing transactions (ee77680)
api: add SMS_OTP credential type to auth credentials (0b35a73)
api: add SWIFT account type, update COP/EGP account requirements (23edde7)
api: add total field to exchange rate fees (c0d40f5)
api: add totalBalance field to internal account responses (1e47f85)
api: manual updates (bcb7d4c)
api: manual updates (605f969)
api: manual updates (96b093a)
api: manual updates (3e10796)
transfers: allow selecting payment rail on transfer-out destination (11e1ce3)

Bug Fixes

client: send content-type header for requests with an omitted optional body (4b556f3)
types: make address optional, countryOfResidence required in EUR beneficiary (901d0c4)
types: make bankName optional in sgd_account (f51e638)
types: remove PENDING_AUTH state from cards model and list params (df34d0f)
types: rename PENDING_ISSUE to PROCESSING in cards state enum (a295fca)
types: require bankName field in BDT/COP/EGP/GHS/PKR external account types (f9c3f11)

Chores

internal: regenerate SDK with no functional changes (857b039)

Documentation

api: add KYB requirements to verifications submit method (8cac5e8)
api: clarify otpEncryptionTargetBundle behavior in auth credentials EMAIL_OTP flow (0695f3c)
api: clarify passkey challenge encoding in auth credentials (fdecfc0)
types: document passkey assertion in auth credentials (4bbc90c)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

stainless-app · 2026-05-28T22:43:36Z

🧪 Testing

To try out this version of the SDK:

npm install 'https://pkg.stainless.com/s/grid-typescript/21e8cea7d288781bfdf73750b14be044def415ff/dist.tar.gz'

Expires at: Sat, 01 Aug 2026 16:14:05 GMT
Updated at: Thu, 02 Jul 2026 16:14:05 GMT

…tion

greptile-apps · 2026-06-02T21:47:06Z

Greptile Summary

This is the automated 1.9.0 release PR generated by Stainless, bundling approximately 25 commits of API additions, type reshaping, and bug fixes since 1.8.0. The release introduces encrypted SMS/OTP flows, CNY account support, payment-rail selection on transfer-out, new transaction fields, and a content-type header fix — but it also carries a significant volume of breaking TypeScript changes across public-facing resource types.

New features: SMS_OTP credential type with HPKE-encrypted OTP flow; CNY_ACCOUNT external account support; paymentRail selection and remittanceInformation on TransferOutCreateParams; direction and receiptDeliveryConfirmedAt fields on transaction types; SWIFT and CNY PaymentInstructions variants; FAMILY_SUPPORT/SALARY_PAYMENT quote purposes.
Breaking type changes (multiple files): CredentialVerifyParams.AuthCredentialVerifyRequest narrowed from unknown to SMS_OTP-only interface (blocks EMAIL_OTP/OAUTH/PASSKEY callers); BusinessInfoUpdate removed from public exports; SessionRefreshParams.clientPublicKey wrapped in AuthSessionRefreshRequest; generateKYCLink renamed to createKYCLink; CardRetrieveResponse/CardUpdateResponse/CardIssueResponse removed; CustomerListResponse, CardListResponse, and VerificationListResponse repurposed as paginated wrappers; documents.upload()/replace() params wrapped in nested request objects; bankName promoted to required in BDT/COP/GHS/PKR account types; EurBeneficiary.countryOfResidence promoted to required.
Bug fixes: Content-type header now sent for requests with an omitted optional body; bankName made optional in SGD accounts.

Confidence Score: 3/5

Multiple TypeScript-breaking changes shipped in a minor version across core auth, customer, card, document, and shared-type modules — downstream TypeScript consumers will encounter compile errors without a corresponding major version bump.

The release carries a large number of incompatible public-API type changes — method renames, required-field promotions, parameter-shape wrappings, and type repurposings — in a 1.8.x → 1.9.0 minor bump. Two new breaking changes not previously flagged are present: CredentialVerifyParams.AuthCredentialVerifyRequest narrowed from unknown to an SMS_OTP-specific interface (locking out EMAIL_OTP, OAUTH, and PASSKEY callers of verify()), and BusinessInfoUpdate deleted from the public namespace. Combined with the many previously identified breaking changes, the effective churn to consumer codebases is high for a minor release.

src/resources/auth/credentials.ts (CredentialVerifyParams body type), src/resources/shared.ts (BusinessInfoUpdate removal and EurBeneficiary required-field inversion), src/resources/auth/sessions.ts (param wrapping), src/resources/customers/customers.ts (method rename, list-type repurposing), src/resources/documents.ts (upload/replace param wrapping), and src/resources/cards.ts (type removals and state-enum rename).

Important Files Changed

Filename	Overview
src/resources/auth/credentials.ts	Adds SMS_OTP credential type and encrypted OTP flow; `CredentialVerifyParams.AuthCredentialVerifyRequest` narrowed from `unknown` to SMS_OTP-specific interface, breaking EMAIL_OTP/OAUTH/PASSKEY `verify()` callers
src/resources/shared.ts	Removes publicly exported `BusinessInfoUpdate` interface; promotes `bankName` to required in BDT/COP/GHS/PKR accounts; inverts `EurBeneficiary` optionality (breaking). `EgpBeneficiary` makes address/countryOfResidence/phoneNumber optional (non-breaking relaxation).
src/resources/auth/sessions.ts	Breaking param-shape change: `SessionRefreshParams.clientPublicKey` wrapped inside `AuthSessionRefreshRequest`; existing callers silently send an empty body
src/resources/customers/customers.ts	Multiple breaking changes: `generateKYCLink` renamed to `createKYCLink`, `CustomerListResponse` repurposed as paginated wrapper, `CustomerUpdateInternalAccountParams.privateEnabled` silently dropped
src/resources/cards.ts	Multiple breaking type renames/removals: `CardRetrieveResponse`→`Card`, `CardUpdateResponse`/`CardIssueResponse` removed, `CardListResponse` repurposed as paginated wrapper, `PENDING_ISSUE` → `PROCESSING` in state enum
src/resources/documents.ts	Breaking param-shape change: `upload()` and `replace()` now extract body from nested request key; callers passing old flat shape send `body: undefined` silently
src/resources/transfer-out.ts	Adds `paymentRail` selection and `remittanceInformation` to `TransferOutCreateParams.Destination`; destination type changed from `ExternalAccountReference` to inline `Destination` with new optional fields (additive, non-breaking)
src/resources/transactions.ts	Adds `direction` and `receiptDeliveryConfirmedAt` to transaction types; `OutgoingTransaction.refund` type changed from local namespace type to `SimulateAPI.Refund` (sandbox import in production module)
src/resources/verifications.ts	`VerificationListResponse` repurposed as paginated wrapper with incompatible shape; old item-type consumers get TS compile errors
src/resources/webhooks.ts	`TestWebhookWebhookEvent` removed from public namespace and from `UnwrapWebhookEvent` union; replaced by semantically mismatched `SandboxWebhooksAPI.TestWebhookRequest`
src/resources/platform/external-accounts.ts	`bankName` promoted to required in BDT/COP/GHS/PKR interfaces; `EgpAccountInfo` drops required `accountNumber`; both are breaking TypeScript changes in a minor release
src/resources/customers/external-accounts.ts	Adds CNY_ACCOUNT support with `CnyAccount` interface; extends `ExternalAccountInfoOneOf` union; additive changes, well-structured
src/resources/quotes.ts	Adds SWIFT and CNY payment instructions, `FAMILY_SUPPORT`/`SALARY_PAYMENT` purpose enum values, and `QuoteRequest` type; additive changes
packages/mcp-server/src/local-docs-search.ts	Large churn updating embedded code examples to reflect API changes (CNY, SWIFT, SMS_OTP, remittanceInformation, payment rail selection)

Sequence Diagram

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant C as Client
    participant G as Grid API

    Note over C,G: SMS OTP / EMAIL OTP Encrypted Flow (NEW in 1.9.0)

    C->>G: POST /auth/credentials (register SMS_OTP)
    G-->>C: "202 {payloadToSign, requestId}"

    C->>C: Sign payloadToSign with existing credential keypair

    C->>G: POST /auth/credentials (signed retry + Grid-Wallet-Signature + Request-Id)
    G-->>C: "201 AuthMethodResponse {otpEncryptionTargetBundle}"

    Note over C: Generate ephemeral TEK keypair (P-256)
    C->>C: "HPKE-encrypt {otp_code, public_key} under otpEncryptionTargetBundle"

    C->>G: "POST /auth/credentials/{id}/verify {type:'SMS_OTP', encryptedOtpBundle}"
    G-->>C: "202 {payloadToSign (verificationToken), requestId}"

    C->>C: Sign verificationToken with TEK private key

    C->>G: "POST /auth/credentials/{id}/verify (signed retry + Grid-Wallet-Signature)"
    G-->>C: "200 AuthSession {expiresAt} (no encryptedSessionSigningKey — client holds TEK)"

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant C as Client
    participant G as Grid API

    Note over C,G: SMS OTP / EMAIL OTP Encrypted Flow (NEW in 1.9.0)

    C->>G: POST /auth/credentials (register SMS_OTP)
    G-->>C: "202 {payloadToSign, requestId}"

    C->>C: Sign payloadToSign with existing credential keypair

    C->>G: POST /auth/credentials (signed retry + Grid-Wallet-Signature + Request-Id)
    G-->>C: "201 AuthMethodResponse {otpEncryptionTargetBundle}"

    Note over C: Generate ephemeral TEK keypair (P-256)
    C->>C: "HPKE-encrypt {otp_code, public_key} under otpEncryptionTargetBundle"

    C->>G: "POST /auth/credentials/{id}/verify {type:'SMS_OTP', encryptedOtpBundle}"
    G-->>C: "202 {payloadToSign (verificationToken), requestId}"

    C->>C: Sign verificationToken with TEK private key

    C->>G: "POST /auth/credentials/{id}/verify (signed retry + Grid-Wallet-Signature)"
    G-->>C: "200 AuthSession {expiresAt} (no encryptedSessionSigningKey — client holds TEK)"

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
src/resources/auth/credentials.ts:802-834
**`CredentialVerifyParams.AuthCredentialVerifyRequest` narrowed to SMS_OTP-only — breaks EMAIL_OTP, OAUTH, and PASSKEY callers**

In 1.8.0 `AuthCredentialVerifyRequestOneOf` was `type AuthCredentialVerifyRequestOneOf = unknown`, so callers of `client.auth.credentials.verify()` could pass any shape (EMAIL_OTP, OAUTH, or PASSKEY payloads). In 1.9.0 it is narrowed to `interface AuthCredentialVerifyRequestOneOf { encryptedOtpBundle: string; type: 'SMS_OTP' }`. Any caller supplying a PASSKEY assertion (`{ assertion: {...} }`) or an OAUTH token payload (`{ type: 'OAUTH', oidcToken: '...' }`) now receives a `TS2345` compile error because those shapes are not assignable to `type: 'SMS_OTP'`. The parameter should accept a broader union (or remain `unknown`) to accommodate all supported credential types through the single `verify()` method.

_{Reviews (30): Last reviewed commit: "release: 1.9.0" | Re-trigger Greptile}

greptile-apps · 2026-06-03T21:08:40Z


 export interface VerificationListResponse {
  /**
-   * Unique identifier for this verification
-   */
-  id: string;
-
-  /**
-   * When this verification was created
-   */
-  createdAt: string;
-
-  /**
-   * The ID of the customer being verified
+   * List of verifications matching the filter criteria
   */
-  customerId: string;
+  data: Array<Verification>;

  /**
-   * List of issues preventing verification from proceeding. Empty when
-   * verificationStatus is APPROVED or IN_PROGRESS.
+   * Indicates if more results are available beyond this page
   */
-  errors: Array<Shared.VerificationError>;
+  hasMore: boolean;

  /**
-   * Current status of the KYC/KYB verification
+   * Cursor to retrieve the next page of results (only present if hasMore is true)
   */
-  verificationStatus:
-    | 'RESOLVE_ERRORS'
-    | 'PENDING_MANUAL_REVIEW'
-    | 'IN_PROGRESS'
-    | 'APPROVED'
-    | 'REJECTED'
-    | 'READY_FOR_VERIFICATION';
+  nextCursor?: string;

  /**
-   * When this verification was last updated
+   * Total number of results matching the criteria


VerificationListResponse repurposed with an incompatible shape

VerificationListResponse previously described a single verification record (id, createdAt, customerId, errors, verificationStatus, updatedAt). It was the item type iterated over by the list() method. In this PR it is redefined as a paginated wrapper (data: Array<Verification>, hasMore, nextCursor, totalCount) while the list() method now yields Verification items directly.

Any TypeScript consumer that referenced Verifications.VerificationListResponse as the shape of a single verification will get a compile error because the fields no longer exist. Additionally, the new type is never returned by any method on Verifications, making it a semantic orphan in the public namespace.

Prompt To Fix With AI

This is a comment left during a code review. Path: src/resources/verifications.ts Line: 157-175 Comment: **`VerificationListResponse` repurposed with an incompatible shape** `VerificationListResponse` previously described a single verification record (`id`, `createdAt`, `customerId`, `errors`, `verificationStatus`, `updatedAt`). It was the item type iterated over by the `list()` method. In this PR it is redefined as a paginated wrapper (`data: Array<Verification>`, `hasMore`, `nextCursor`, `totalCount`) while the `list()` method now yields `Verification` items directly. Any TypeScript consumer that referenced `Verifications.VerificationListResponse` as the shape of a single verification will get a compile error because the fields no longer exist. Additionally, the new type is never returned by any method on `Verifications`, making it a semantic orphan in the public namespace. How can I resolve this? If you propose a fix, please make it concise.

…count types

greptile-apps · 2026-06-23T00:30:56Z


-  data: CardStateChangeWebhookEvent.Data;
+  data: CardsAPI.Card;

  /**
   * ISO 8601 timestamp of when the webhook was sent
   */
  timestamp: string;


TestWebhookWebhookEvent removed — breaking type export and semantic mismatch in UnwrapWebhookEvent

TestWebhookWebhookEvent was a public export from the Webhooks namespace and a member of the UnwrapWebhookEvent discriminated union. It is removed here and replaced in the union by SandboxWebhooksAPI.TestWebhookRequest. Any consumer typing against Webhooks.TestWebhookWebhookEvent now gets a TS2305 compile error. Beyond the breakage, inserting a type named TestWebhookRequest (which reads as a request payload to trigger a test webhook) into a union of received webhook events is semantically misleading to readers of the public API surface.

Prompt To Fix With AI

This is a comment left during a code review. Path: src/resources/webhooks.ts Line: 240-246 Comment: **`TestWebhookWebhookEvent` removed — breaking type export and semantic mismatch in `UnwrapWebhookEvent`** `TestWebhookWebhookEvent` was a public export from the `Webhooks` namespace and a member of the `UnwrapWebhookEvent` discriminated union. It is removed here and replaced in the union by `SandboxWebhooksAPI.TestWebhookRequest`. Any consumer typing against `Webhooks.TestWebhookWebhookEvent` now gets a `TS2305` compile error. Beyond the breakage, inserting a type named `TestWebhookRequest` (which reads as a *request* payload to trigger a test webhook) into a union of *received* webhook events is semantically misleading to readers of the public API surface. How can I resolve this? If you propose a fix, please make it concise.

…me methods

greptile-apps · 2026-06-29T16:48:02Z

 export interface CredentialVerifyParams {
  /**
-   * Body param
+   * Body param: Verify an SMS-OTP credential via the same secure two-leg flow as
+   * email OTP. The client HPKE-encrypts the OTP code (together with its public key)
+   * under the `otpEncryptionTargetBundle` returned from registration or
+   * `POST /auth/credentials/{id}/challenge`, submits the result here, and receives
+   * `202` with a `payloadToSign` carrying a `verificationToken` bound to the
+   * client's public key. The client signs that token with the matching private key
+   * and retries this request with `Grid-Wallet-Signature` + `Request-Id` headers to
+   * obtain the session. Plaintext OTP codes are never sent over the wire.
   */
  AuthCredentialVerifyRequest: AuthCredentialVerifyRequestOneOf;

  /**
-   * Header param: The `requestId` returned alongside the Grid-issued `challenge`
-   * from `POST /auth/credentials/{id}/challenge`, echoed back exactly here so Grid
-   * can correlate the assertion with the pending challenge.
+   * Header param: Full API-key stamp built over the prior `payloadToSign` with the
+   * TEK (Target Encryption Key) keypair the client generated for this login.
+   * Required on the signed retry that completes an `EMAIL_OTP` or `SMS_OTP`
+   * verification. Not used by `OAUTH` or `PASSKEY` verification, which complete in a
+   * single call.
+   */
+  'Grid-Wallet-Signature'?: string;
+
+  /**
+   * Header param: The `requestId` returned in a prior `202` response from this
+   * endpoint, echoed back exactly here so the server can correlate the signed retry
+   * with the issued challenge. Required on the signed retry that completes an
+   * `EMAIL_OTP` or `SMS_OTP` verification; must be paired with
+   * `Grid-Wallet-Signature`. For `PASSKEY` verification, the `requestId` issued from
+   * `POST /auth/credentials/{id}/challenge` is echoed here instead so the server can
+   * correlate the assertion with the pending challenge.
   */
  'Request-Id'?: string;
 }


CredentialVerifyParams.AuthCredentialVerifyRequest narrowed to SMS_OTP-only — breaks EMAIL_OTP, OAUTH, and PASSKEY callers

In 1.8.0 AuthCredentialVerifyRequestOneOf was type AuthCredentialVerifyRequestOneOf = unknown, so callers of client.auth.credentials.verify() could pass any shape (EMAIL_OTP, OAUTH, or PASSKEY payloads). In 1.9.0 it is narrowed to interface AuthCredentialVerifyRequestOneOf { encryptedOtpBundle: string; type: 'SMS_OTP' }. Any caller supplying a PASSKEY assertion ({ assertion: {...} }) or an OAUTH token payload ({ type: 'OAUTH', oidcToken: '...' }) now receives a TS2345 compile error because those shapes are not assignable to type: 'SMS_OTP'. The parameter should accept a broader union (or remain unknown) to accommodate all supported credential types through the single verify() method.

Prompt To Fix With AI

This is a comment left during a code review. Path: src/resources/auth/credentials.ts Line: 802-834 Comment: **`CredentialVerifyParams.AuthCredentialVerifyRequest` narrowed to SMS_OTP-only — breaks EMAIL_OTP, OAUTH, and PASSKEY callers** In 1.8.0 `AuthCredentialVerifyRequestOneOf` was `type AuthCredentialVerifyRequestOneOf = unknown`, so callers of `client.auth.credentials.verify()` could pass any shape (EMAIL_OTP, OAUTH, or PASSKEY payloads). In 1.9.0 it is narrowed to `interface AuthCredentialVerifyRequestOneOf { encryptedOtpBundle: string; type: 'SMS_OTP' }`. Any caller supplying a PASSKEY assertion (`{ assertion: {...} }`) or an OAUTH token payload (`{ type: 'OAUTH', oidcToken: '...' }`) now receives a `TS2345` compile error because those shapes are not assignable to `type: 'SMS_OTP'`. The parameter should accept a broader union (or remain `unknown`) to accommodate all supported credential types through the single `verify()` method. How can I resolve this? If you propose a fix, please make it concise.

…ions

feat(api): manual updates

3e10796

stainless-app Bot added the autorelease: pending label May 28, 2026

feat(api): manual updates

96b093a

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 6d92ed8 to ddcf565 Compare May 28, 2026 23:17

feat(api): manual updates

605f969

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from ddcf565 to 0bb0b25 Compare May 28, 2026 23:35

feat(api): manual updates

bcb7d4c

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 0bb0b25 to ca3e49f Compare May 28, 2026 23:51

feat(api): add SWIFT account type, update COP/EGP account requirements

23edde7

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from ca3e49f to 47f7a2c Compare May 29, 2026 05:53

docs(api): add KYB requirements to verifications submit method

8cac5e8

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 47f7a2c to 58f03d2 Compare May 29, 2026 19:15

docs(types): document passkey assertion in auth credentials

4bbc90c

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 58f03d2 to 26db534 Compare May 30, 2026 00:16

feat(transfers): allow selecting payment rail on transfer-out destina…

11e1ce3

…tion

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 26db534 to d258a43 Compare June 1, 2026 21:08

feat(api): add receiptDeliveryConfirmedAt to transaction responses

c6d1dba

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from d258a43 to d09fc51 Compare June 2, 2026 21:43

greptile-apps Bot reviewed Jun 2, 2026

View reviewed changes

Comment thread src/resources/customers/customers.ts

Comment thread src/resources/customers/customers.ts

Comment thread src/resources/transactions.ts

feat(api): add ID_TYPE and ID_NUMBER to CustomerInfoFieldName enum

51b3b49

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from d09fc51 to c1ef000 Compare June 3, 2026 21:04

greptile-apps Bot reviewed Jun 3, 2026

View reviewed changes

codegen metadata

2c176a5

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from c1ef000 to 97bfb69 Compare June 3, 2026 22:00

fix(types): require bankName field in BDT/COP/EGP/GHS/PKR external ac…

f9c3f11

…count types

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 97bfb69 to 2072d7c Compare June 3, 2026 22:23

feat: Add encrypted OTP flow

948a93b

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 2072d7c to dedcdbf Compare June 4, 2026 20:08

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 48ced55 to c94a17d Compare June 23, 2026 00:26

greptile-apps Bot reviewed Jun 23, 2026

View reviewed changes

codegen metadata

2e83b69

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from c94a17d to abbf989 Compare June 23, 2026 04:24

chore(internal): regenerate SDK with no functional changes

857b039

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from abbf989 to 745f7bb Compare June 24, 2026 20:12

feat(api): add direction field to transaction responses

8eea143

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 745f7bb to 3be7dc8 Compare June 24, 2026 23:00

feat(api): add remittanceInformation param to transferOut and agents.…

9bd9746

…me methods

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 3be7dc8 to e238bba Compare June 25, 2026 19:03

feat(api): add SMS_OTP credential type to auth credentials

0b35a73

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from e238bba to 86db62b Compare June 26, 2026 20:07

feat(api): add card transaction type to transaction union responses

5f7a560

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 86db62b to be0b3b3 Compare June 27, 2026 00:32

feat(api): add processorRef field to cards

83719ec

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from be0b3b3 to 05e5310 Compare June 27, 2026 01:05

codegen metadata

aa7799d

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 05e5310 to b4db0df Compare June 29, 2026 16:42

greptile-apps Bot reviewed Jun 29, 2026

View reviewed changes

feat(api): add bankName field to GTQ/JMD external accounts

5c5c59c

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from b4db0df to a24ec24 Compare June 29, 2026 19:48

feat(api): add phoneNumber field to customers create/update/response

7c9470b

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from a24ec24 to e5a00e1 Compare June 29, 2026 19:59

feat(api): add settlement timing and rail fields to outgoing transact…

ee77680

…ions

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from e5a00e1 to f113094 Compare June 29, 2026 22:38

feat(api): add identifier and idType fields to customers create

21e8cea

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from f113094 to 3375f30 Compare July 2, 2026 16:13

stainless-app Bot added 2 commits July 2, 2026 22:29

codegen metadata

11740a7

release: 1.9.0

1707778

stainless-app Bot force-pushed the release-please--branches--main--changes--next--components--grid branch from 3375f30 to 1707778 Compare July 2, 2026 22:30

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

release: 1.9.0#20

release: 1.9.0#20
stainless-app[bot] wants to merge 46 commits into
mainfrom
release-please--branches--main--changes--next--components--grid

stainless-app Bot commented May 28, 2026 •

edited

Loading

Uh oh!

stainless-app Bot commented May 28, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Jun 2, 2026 •

edited

Loading

Important Files Changed

Sequence Diagram

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot Jun 3, 2026

Uh oh!

greptile-apps Bot Jun 23, 2026

Uh oh!

greptile-apps Bot Jun 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

stainless-app Bot commented May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Automated Release PR

1.9.0 (2026-07-02)

Features

Bug Fixes

Chores

Documentation

Uh oh!

stainless-app Bot commented May 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

greptile-apps Bot commented Jun 2, 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

Sequence Diagram

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot Jun 3, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Jun 23, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Jun 29, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

stainless-app Bot commented May 28, 2026 •

edited

Loading

stainless-app Bot commented May 28, 2026 •

edited

Loading

greptile-apps Bot commented Jun 2, 2026 •

edited

Loading