feat(core): Add profile-level configuration for L2/L3 data enablement#9683
Merged
likhinbopanna merged 18 commits intomainfrom Oct 16, 2025
Merged
feat(core): Add profile-level configuration for L2/L3 data enablement#9683likhinbopanna merged 18 commits intomainfrom
likhinbopanna merged 18 commits intomainfrom
Conversation
ee716e4 to
e2f9232
Compare
cb80ebb to
b4db2c9
Compare
7396d08 to
55c2b90
Compare
dab9d65 to
40eac45
Compare
ddb4bc6 to
5dacf13
Compare
5572fde to
a0c88ab
Compare
1010551 to
394f9f0
Compare
15e566d to
21d7978
Compare
e22ac95 to
92a3efc
Compare
sai-harsha-vardhan
approved these changes
Oct 14, 2025
deepanshu-iiitu
approved these changes
Oct 14, 2025
chaitak-gorai
pushed a commit
that referenced
this pull request
Oct 16, 2025
…#9683) Co-authored-by: hyperswitch-bot[bot] <148525504+hyperswitch-bot[bot]@users.noreply.github.com> Co-authored-by: likhinbopanna <131246334+likhinbopanna@users.noreply.github.com>
drdholu
pushed a commit
to drdholu/hyperswitch
that referenced
this pull request
Oct 30, 2025
…juspay#9683) Co-authored-by: hyperswitch-bot[bot] <148525504+hyperswitch-bot[bot]@users.noreply.github.com> Co-authored-by: likhinbopanna <131246334+likhinbopanna@users.noreply.github.com>
aadityaguptaa
pushed a commit
that referenced
this pull request
Nov 10, 2025
…#9683) Co-authored-by: hyperswitch-bot[bot] <148525504+hyperswitch-bot[bot]@users.noreply.github.com> Co-authored-by: likhinbopanna <131246334+likhinbopanna@users.noreply.github.com>
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.
Type of Change
Description
This PR introduces profile-level configuration for enabling/disabling L2/L3 transaction data, providing merchants with granular control over enhanced payment data collection at the business profile level.
🧩 Additional Changes
🗄️ Database & Schema
Added new column
is_l2_l3_enabledto thebusiness_profiletable.BOOLEANNULLABLE BOOLEAN)Updated L2/L3 data construction logic to check both:
state.conf.l2_l3_data_config.enabledpayment_data.is_l2_l3_enabled == Some(true)New behavior:
L2/L3 data is now included only when both flags are enabled.
⚙️ Behavior Changes
Previously:
L2/L3 data inclusion was controlled only by the global configuration flag:
Motivation and Context
How did you test it?
Flag False
Response
Payments Create +Confirm
Response
enhanced_data : None (In vantive we pass the l2_l3_data in enchanced_data field )

Prifle flag as true
Response
Pqyments Create+ Confirm
Response