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
- 84c4b558c9f964553616afcba8493486a979f792af1667a25e8a3226e8548573
- request
- 2f27d0bbab66c26e983c874c4c640a86b013ba01e9d577ec0e44d2b3f234426f
- transaction
- df983583aa9f31028689e187577d8324fe383aa48762a187d3f312ce01180e25computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45885
the chainentry 45885
- sealed to the entry before
- 59e358a0ce38216e01939a62f5dee3636cb53e2ce658bd9e77d7b95e6eb613ad
- this leaf
- 1e711a0e91c75b705cfca75f0aab3421ad7464c0b68404bcb33012d64cca26a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1SVTIDCGAcCd+rv2zR5NQ17vdocyrEqzjoGc9678k0NqAA9TVUd0owhZEYftYX3in3XP6clmhO+9VbgOsnqWDg==