On This Page

{#jumplink-list}  
[Markdown](/docs/cybs/en-us/level-2-3/developer/smartpay/rest/level-2-3/l23-intro-overview/l23-intro-about-data-processing.md)  
Filter  
FILTER BY TAG

`Cybersource` Level II and Level III Data Processing {#l23-data-processing}
===========================================================================

`Cybersource` does not store Level II and Level III data. Rather, it functions as a pass-through service for the data. Thus, if you request multiple partial captures or credits for an order, you must include the Level II and Level III data in each request.  
During data processing, minimal validation is performed in order to minimize interference with business policies between the merchant and customers.  
If Level III transactions produce batching errors while data is transmitted to the processor, the Level III processing field is disabled (value set to `N`) and the merchant is sent a message showing the change in status. When this happens, the request is not rejected, and the disabled processing field is included in the status message.

* For credits and captures, the disabled field is orderInformation.invoiceDetails.level3TransmissionStatus

For example, when a capture transaction produces batching errors, the orderInformation.invoiceDetails.level3TransmissionStatus field is set to `N`.  
`Cybersource` recommends that you include the total order amount in the authorization request, when authorizing Level III transactions. Doing so ensures that your total order amount is used and that the capture or credit request total amount matches the original authorization total amount.
IMPORTANT If you omit required Level II and Level III fields from a request, the transaction does not fail. It is processed successfully. This could result in higher fees or penalties assessed against your account. Contact your processor to ensure that you understand your processor's specific requirements for Level II and Level III transactions.  
RELATED TO THIS PAGE