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
- 4d58b6cf18bcc0e4186e28dd60727440a50123b932bfa71174e24e8f91c8c6b2
- request
- dc3fed618b579887662d4c8fb1b688020657891c26f3cde3bfff00b564e674b9
- transaction
- ecd47a6a0159347f1e294195143a85c0c2c42bb3ac025151f29400a2968b474ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15936
the chainentry 15936
- sealed to the entry before
- 81d432e4469ae8bf58ba4c087296471bdfb95d76d30105c208a3db122e1a58d6
- this leaf
- f1983e2889dd7ace1c811d661531a965387ca2eb986f6fcb055682b1d8fb5ffd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7pEdRYjF15hNQcEmS/TTeUTFQCPcLeUsmBaEACgJcX0r6Nhm19D87m4I1JaKopDgDXYOf0rMvodloYZLPuldCQ==