Repository navigation
BTePOS: map the loyalty account group from Payment Integration ID - #132
Draft
rmcotton-sap wants to merge 2 commits into
Draft
rmcotton-sap wants to merge 2 commits into
rmcotton-sap wants to merge 2 commits into
Conversation
rmcotton-sap
changed the title
Map accountGroupId in the loyalty POST from the Payment Integration ID smart field and remove the GET lookup and the loyAccountGroupId custom field. Verification makes three calls instead of four. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
rmcotton-sap
force-pushed
the
btepos-use-payment-integration-id
branch
from
October 15, 2026 15:12
af1ed5f to
70b4d0f
Compare
rmcotton-sap
changed the title
rmcotton-sap
marked this pull request as draft
October 15, 2026 15:13
zeyun123
self-requested a review
October 16, 2026 08:14
# Conflicts: # postman/btepos/PAYMENT_PAGE/BTePOS_mapping_configuration.json
rmcotton-sap
marked this pull request as ready for review
October 27, 2026 16:52
zeyun123
approved these changes
Oct 28, 2026
rmcotton-sap
marked this pull request as draft
October 28, 2026 08:57
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
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.
Summary
accountGroupIdin the loyaltyPOST /opf/merchant/transactionsis mapped from the Payment Integration ID smart field (${input.paymentIntegrationId}). TheGET …&expand=accountGrouplookup and theloyAccountGroupIdcustom field are removed, so verification makes three calls instead of four.Changes
postman/btepos/PAYMENT_PAGE/BTePOS_mapping_configuration.jsonpostman/btepos/PAYMENT_PAGE/README.md: split-payment stepsTesting
A split payment (card and loyalty points) was tested against the BTePOS sandbox.
Draft: not for merge until the OPF release that includes the Payment Integration ID smart field is live.
🤖 Generated with Claude Code