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
- ca1312b5f7172798fe7c8727eeb67fc44ff8e4c396ee949f05181d6666a9b5b0
- request
- 5138e5e6a26907c83843668f40472be8ba82a5d0a9138a753b1482f4a9a0953d
- transaction
- 7a69177c10dacf6d52453255e3d17fbcc20717378c556b5075e2ef796d779c93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31828
the chainentry 31828
- sealed to the entry before
- 5008270e819a9ea97e45e01ba186a085340d934ab15a394d9cbfb00e5aa0c9bb
- this leaf
- 6d4f51c02e20e555715c592724bcd5a14e3a8a93b6e884202e3befd0ee796ad7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UXUCDBEkXKIY3tdcAtDehqSJxDsrrl0aR/IzDPRQZmJVVb+TsGFEEgrT+BVD+S4tIMe6AH5Kpu0zldHKOiUJCQ==