docs(changelog): add August 2026 entry and expand July 2026 - #838
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Contributor
Greptile SummaryThis PR adds an August 2026 changelog entry and expands July's entry to describe recently added API capabilities.
Confidence Score: 1/5This PR should not merge until the inaccurate platform-fee, EDD, Travel Rule, and transaction-failure documentation is aligned with the current API contract. The changelog currently directs integrators to nonexistent routes and fields and tells them to remove handling for transaction failure values that the API contract still permits. Files Needing Attention: mintlify/changelog.mdx
|
| Filename | Overview |
|---|---|
| mintlify/changelog.mdx | Adds extensive release notes, but documents multiple fields, endpoints, statuses, webhooks, and failure values that are absent from or contradict the current API contract. |
Prompt To Fix All With AI
### Issue 1
mintlify/changelog.mdx:19-20
**Platform fee field is invalid**
When a platform follows this entry, it sends `transactionFeeConfigs` even though `PATCH /platform/config` exposes `feeConfigs`, causing the standing fee configuration to be rejected or ignored; the entry also omits that fee configurations and per-quote overrides currently require a USD source currency.
### Issue 2
mintlify/changelog.mdx:46-47
**EDD endpoint does not exist**
When an integrator follows this entry, it calls `POST /customers/edd`, but EDD is represented as patchable attributes on an individual customer and has no separate resource, causing the submission to target a nonexistent route.
### Issue 3
mintlify/changelog.mdx:67-73
**Travel Rule lifecycle is absent**
When a platform implements this flow, the documented challenge and verify routes are absent from OpenAPI, as are the `PENDING_OWNERSHIP_VERIFICATION` and `UNVERIFIED` states and `EXTERNAL_ACCOUNT.STATUS_UPDATED` webhook, causing requests to fail and generated clients to lack the announced lifecycle.
### Issue 4
mintlify/changelog.mdx:100-103
**Failure-reason contract is reversed**
When an integrator follows this breaking-change notice, it removes handlers for four values that remain in `OutgoingTransactionFailureReason`, while the newly advertised payout reasons, `pendingReason`, and limit codes are absent from the current schemas, causing deserialization failures or missed transaction handling.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.Reviews (1): Last reviewed commit: "docs(changelog): add August 2026 entry a..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
pengying
force-pushed
the
docs-changelog-august-2026
branch
from
August 14, 2026 20:56
b21db20 to
787e6c2
Compare
Covers the API surface merged since mid-July, framed by what each change
lets a platform do rather than by the fields it adds.
August 2026: platform fee assessment (standing config, per-quote override,
fee breakout on quotes and transactions), end-user terms consent, programmatic
KYC/EDD, EU groundwork (SCA session expiry and error codes, Travel Rule
ownership verification), stablecoin mint/burn, new networks and corridors,
and reworked payout failure reasons.
July 2026: card transaction webhooks and the full sandbox simulate set,
plus refund events on incoming payments.
Deliberately omitted: spec surface whose backend is not live yet
(POST /transactions/{id}/cancel, base-transaction field additions, Plasma
as a standalone announcement), CLI/sample/demo work, and docs fixes.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
pengying
force-pushed
the
docs-changelog-august-2026
branch
from
August 14, 2026 21:02
787e6c2 to
580d3ce
Compare
shreyav
approved these changes
Aug 14, 2026
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Covers the API surface merged since mid-July, framed by what each change
lets a platform do rather than by the fields it adds.
August 2026: platform fee assessment (standing config, per-quote override,
fee breakout on quotes and transactions), end-user terms consent, programmatic
KYC/EDD, EU groundwork (SCA session expiry and error codes, Travel Rule
ownership verification), stablecoin mint/burn, new networks and corridors,
and reworked payout failure reasons.
July 2026: card transaction webhooks and the full sandbox simulate set,
plus refund events on incoming payments.
Deliberately omitted: spec surface whose backend is not live yet
(POST /transactions/{id}/cancel, base-transaction field additions, Plasma
as a standalone announcement), CLI/sample/demo work, and docs fixes.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com