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
- fdbdf55bcd0460d3d9d128ada6dde08bc8dace5f5757987b6e6752181d9c90ca
- request
- 8671499a85db962ec762a74fe4033d487ff37e427e7c948634d8ee979f060ac4
- transaction
- f8c80e6c152b4bb605a127699f6fa40b3e79e266d918be9593f6f007a786c413computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46118
the chainentry 46118
- sealed to the entry before
- 5f685860582560e7c4f7535cad19dc5efb5601793136ab09ab853ab0e31f6a6c
- this leaf
- bbc4c3790af4e7ee581e91aab6c323bc83eae914ac43956b6068ec221fc2379f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6V3nlrQbvm+FfI8a7tjk5J+Cig6gC1o/ovMhoRM18knChPclvjojaXdnIR/yskTljCQW6+h1HSWuIlDfDG3aBQ==