We discussed the usage of header and content enrichers—they add additional information. However, in some circumstances, it might be a valid use case to hide the data—the simplest one can be a heavy payload. It's not a good idea to move the whole message around while most of the channels might be using just a subset or even just a pass-through! Enter a claim check pattern, which suggests storing data in accessible storage and then passing only the pointers around. Components that need the data to process can retrieve it using the pointer. Spring integration provides two components to accomplish this: Incoming claim check transformer and Outgoing claim check transformer. The incoming claim check transformer can be used to store the data while the outgoing one can be used to retrieve it.