why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- d1ad209e5d977bc4d6833a6c301c317aafb92197114b0e6e41e714680971be21
- request
- 6331388c5f405a851ac32d56a6d7819a68fa5e7669dcaf565cf900c36b21f6af
- transaction
- 942aee95a8494d1bb50bcaa93f7bc48902213c9f149f89377acc5e431796c9accomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70644
the chainentry 70644
- sealed to the entry before
- c97a4002cc39b63655d3fe96378d4ecf4a10dfa06085902ecad158c3f950436d
- this leaf
- 122439bef8d3246da00e3d209034428f194367003b656a663ad97dc7affdf370
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IiE9gOU76WUD2Ur/M122WesCw2Hh7tFrJh8JjR/+YeR9IgjNwtZR9rjmH3GkEYxVQOOQEfoS+GHHVBU8gF5GBg==