Level 2 & level 3 Data Processing
level 2 and level 3 (l2/l3) data processing allows you to send enriched transaction data to stripe when processing single card payments via stripe connect by including additional details at the payment and line item level, you can help stripe classify transactions more accurately and potentially reduce interchange fees this feature is particularly relevant for us based organisations , where l2/l3 data has a direct impact on card processing costs this feature is available starting in v2 37 0 (winter '26) single time payments and v2 38 0 (spring '26) for recurring payments (payments processed via authorisations) how it works by default, only level 1 (basic) payment data is passed to the psp however, you can also send line level information to stripe such as product name product code tax amounts unit cost quantity unit of measure this feature uses the payment line item object (api name asp04 paymentlineitem c ), which is a child of the unaric payment object the level of data sent to stripe depends on whether the payment line item object exist on the payment if payment line items exist , level 2 / level 3 data is sent to stripe if no line items exist , payment is processed as level 1 only no system error is generated when line items are missing this feature also has its own permission set, unaric payments line level data , which provides access to payment line item records, including detailed line level charge breakdowns for individual payments automation for the certinia connector is not supported the certinia connector does not create payment line items automatically hence, if you use certinia, you must populate payment line items using flow or custom automation enable level 2 & level 3 data processing this feature must be enabled by your customer success manager contact support at payment support\@unaric com mailto\ payment support\@unaric com for more information prerequisites before enabling and using this feature, be aware of the following this is a premium feature l2/l3 data processing is only available for card payments processed via stripe connect stripe does not clearly surface l2/l3 data usage or benefits in the stripe dashboard clients should work directly with stripe to confirm which data is being received how their transactions are classified what discounts may apply stripe does not clearly display the value of l2/l3 data inside the dashboard, so coordination with stripe is essential