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
- afb21ff7e717a38564fcc91b3a54ec1126673c37e913cd5faba44b0fb959904d
- request
- 32b26972cdbe6c851f953d6beb3e7ac665828c25b2419100313e56534a863d80
- transaction
- 6c15c944ccc4ef7405fb45537217690655d180426dccbd955c3deec6d20b6959computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45298
the chainentry 45298
- sealed to the entry before
- a70069d1bad9623cdb36bbaf5a05663dcd124085a7685ed5cf0dab22c0621a93
- this leaf
- fb274d171dfbdf4a75fe2f1fec21fe3988b14cff286dd1d09d9f21411e48f04e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qlqubDwtztff0xlMwATAJk/GPoExv37d8qZouISj2SSGzxpUhHV0/gLZj/YrXBeqSpzkjHJoh/z4D0LMLBN1Bg==