feat(payment): PAYMENTS-11169 Add provider token fields to Orders GetTransactions API public docs#1263
Open
feat(payment): PAYMENTS-11169 Add provider token fields to Orders GetTransactions API public docs#1263
Conversation
bc-harika
force-pushed
the
PAYMENTS-11169
branch
from
290ef87 to
4e62adb
Compare
… Transactions API public docs
… in separate line for both the fields
bc-harika
force-pushed
the
PAYMENTS-11169
branch
from
8f30c2e to
f5df194
Compare
WillemHoman
reviewed
Feb 18, 2026
| provider_customer_id: | ||
| type: string | ||
| description: | | ||
| The payment provider's customer identifier associated with the stored instrument used to process this transaction, if applicable. |
Contributor
There was a problem hiding this comment.
Is it worth calling out the 1:n relationship between provider_customer_id and provider_instrument_token
WillemHoman
approved these changes
Feb 18, 2026
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.
PAYMENTS-11169
What changed?
provider_instrument_tokenandprovider_customer_id) in theOrders V3 Get Transactions APIresponse.Expose Provider Tokensfeature is enabled for the store.Release notes draft
We've added two new optional fields to the Orders V3 Get Transactions API:
These fields return the payment provider's stored instrument token and customer identifier associated with a transaction, when available.
This functionality is controlled by the Expose Provider Tokens feature flag and will only be included in API responses for stores where the feature is enabled.
Anything else?
Verified the OpenAPI spec in both Swagger UI and the Redoc previews. The syntax and the formatting is all good.
Swagger UI preview
Response Schema
Response Sample
Redoc preview
Response Schema
Response Sample
ping @bigcommerce/team-payments