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
- f31da77a5b7b8d42ccc690c6dc16de9f648ec03bfd5a62c4df8527418a00a9c6
- request
- 654605dfcbaf356b90d0737427ef71b63a31f7e6a351e9765953f1256983d9db
- transaction
- 24ce08330b278e2c318bbf04341d2688e3f5735235a0eca44bad057d558695f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77500
the chainentry 77500
- sealed to the entry before
- 50537fe06e31c5d43af98cd65cf80b1ca5917f1fcc64eb5f8ac706c0bdcdb6f3
- this leaf
- 9606f6fea1c126c96992d6c6c59766d4b6384422d2754251631d748ba4563d5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zMBllHre0TtbwjkAa2ja2uO0a2Q4JsSI7gOp10N3vFYSG7ZHSxcCVsqdhmjvJKeItm5gWvUfh0TlkF73mh54CA==