#connor_api
safe smeltBOT
đź‘‹ Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đź”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1410328315797176442
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- connor_best-practices, 1 day ago, 22 messages
marble burrow
This is the email we received:
Starting October 17, 2025, Visa will apply stricter data monitoring standards as part of their new Commercial Enhanced Data Program (CEDP). Under the new standards, to keep your L2/L3 rates, the "unit_of_measure" field needs to be populated accurately.
The API you’re currently using doesn’t make this field available. We recommend updating your integration to the new Payment Line Items API public preview instead, which lets you customize this field.
What you need to do
1.Update your integration: We recommend using the latest version of the Payment Line Items API to send the "unit_of_measure" field.
2.Adopt a new version header: You'll need to use the version header 2025-04-30.preview or higher for API requests that make use of Payment Line Items.
3.Check your line item data quality: Visa verifies businesses for CEDP based on the quality of the data they submit. Review Visa’s best practices for data quality.
About the Payment Line Items API
As part of the public preview, we’ve added:
The "unit_of_measure" field, which will be required under CEDP
The "commodity_code" field, which is an optional field for L2/L3 programs
Support for line items specific to local payment methods, such as Klarna and PayPal, and the ability to manage them in one place
Please update your integration by October 17 to help maintain your L2/L3 rates.
If you have any questions, please contact us from our support site. We’re here to help.