We should consider a ClaimCheckRepository API (or potentially allow to reuse aggregate repository) and add into the DSL to make it easy to store / claim.
And the eip
Likely the aggregator repository is the best suited to reuse/extend from as its to store with a key -> exchange. And have apis to remove as well.
But we need to give it a bit more thought. The idea is for the implementations to make them reusable so we do not have to implement this again for JDBC, hazelcast and what else we have today for repositories.