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
- d4faad0a0860d99067a7746e874f9aa744d7947f98063f8b9d219c791570a224
- request
- 42e5d4802797580f9775d0a5b3fe7704ca12857a8043a20aeb3b54ce14938ad5
- transaction
- 0cb120183434f3692679f86b51ddbc2e8e20a2099bdbaea497b853b2128530f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68123
the chainentry 68123
- sealed to the entry before
- ec6de6e17b66e20d06aa8fe9e0a23b7ea78724f918a41a81fe10c479e9281e50
- this leaf
- 81cdf17d2e3023b5c27351b5aaecb4c8d8141fb6e122b943a18e4f50c1fd75f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ec6lRRbZNQqLL+O3Ku6GHSyOYaPB3DhtZxxkZyYLBbeFCDWFuYmHuGXLGlkzoK7WgG0B7V8bHaUFuNX8/+uPBQ==