chore(sample): update the Kotlin sample to Grid SDK 2.0.0

[pengying]

What changed

Updates samples/kotlin from Grid Kotlin SDK 1.7.1 to 2.0.0, which is now on Maven Central. The routes change only where the SDK's types changed:

• Quotes: source and destination variants use the 2.0.0 names, such as QuoteSourceOneOf.ofAccount instead of ofAccountQuoteSource. QuoteCreateParams keeps its 1.7.1 setters.
• Customers: the request is an IndividualCustomerCreateRequest, passed directly to createCustomerRequest.
• External accounts: accountInfo, currency, and customerId are set on ExternalAccountCreateParams directly. The ExternalAccountCreate wrapper is gone, and ofEthereumWalletExternal is now ofEthereumWallet. The INR route no longer sets bankName, which InrExternalAccountCreateInfo dropped.
• Sandbox: fund and send-funds requests pass a FundRequest and a SendRequest body.
• Auth credentials: passkey create and verify use PasskeyAttestation and PasskeyAssertion, and resendChallenge is now challenge.

The end-to-end test now gives each customer an email, which the API requires when creating a customer.

Tests

• Compiles against lightspark-grid-kotlin:2.0.0 resolved from Maven Central, with no local Maven repository.
• ./gradlew test: all 8 end-to-end tests pass against the dev sandbox.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated
grid-cards-demo	Ignored	Preview	Oct 7, 2026 6:11pm UTC
grid-flow-builder	Ignored	Preview	Oct 7, 2026 6:11pm UTC
grid-wallet-demo	Ignored	Preview	Oct 7, 2026 6:11pm UTC

[pengying]

• chore(sample): update the Kotlin sample to Grid SDK 2.0.0 #1136 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 4/5

[Medium risk] Updates Kotlin sample code to a new SDK major version.

The PR appears safe to merge, with a non-blocking request to test the changed passkey calls.

Findings

1.  Passkey changes lack tests ▶

Fix with agent prompt

### Issue 1
samples/kotlin/src/main/kotlin/com/grid/sample/routes/AuthCredentials.kt:247
The SDK migration changes passkey creation, challenge, and verification, but none of the eight end-to-end tests call these routes. Verification now passes `PasskeyAssertion` directly where the old code built a request containing `type` and `assertion`.

Add tests that check the outgoing JSON for all three calls, including a challenge without `clientPublicKey`. Compilation and the payout tests cannot catch an incorrect credential request body.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Updates the Kotlin sample to Grid SDK 2.0.0 and adapts customer, account, quote, sandbox, and credential calls to its new types.

• Adds email addresses to customer test requests.
• Adds no tests for the changed credential request bodies; targeted coverage would help protect passkey flows.

_{Reviews (1) · Last reviewed commit: "chore(sample): update the Kotlin sample ..." · Reviewed by Greptile}

[greptile-apps]

Passkey changes lack tests

The SDK migration changes passkey creation, challenge, and verification, but none of the eight end-to-end tests call these routes. Verification now passes PasskeyAssertion directly where the old code built a request containing type and assertion.

Add tests that check the outgoing JSON for all three calls, including a challenge without clientPublicKey. Compilation and the payout tests cannot catch an incorrect credential request body.

Prompt To Fix With AI

This is a comment left during a code review.
Path: samples/kotlin/src/main/kotlin/com/grid/sample/routes/AuthCredentials.kt
Line: 247

Comment:
**Passkey changes lack tests**

The SDK migration changes passkey creation, challenge, and verification, but none of the eight end-to-end tests call these routes. Verification now passes `PasskeyAssertion` directly where the old code built a request containing `type` and `assertion`.

Add tests that check the outgoing JSON for all three calls, including a challenge without `clientPublicKey`. Compilation and the payout tests cannot catch an incorrect credential request body.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.