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
- b297d636536a1e7b6cdc8bc036faa98631bc3994e855aa3c0910524cd9e98f19
- request
- 9e0dcd0d52f82c2d99afe70423b072659017eae8dd355fc9994dac6fb95cc0d3
- transaction
- 6bfa38378fa3d5ef1b54ff87b480d0786afbf841b4026fe4432760fae5faabf9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61214
the chainentry 61214
- sealed to the entry before
- a445b9f3b63e4cb9725d7b436def1c109b180d43395f6dec100e160fbb2ea9b9
- this leaf
- 3e4a4c8c9f991b0cc0114293efbb3164e0eee12d499dbcece215aab0b0c554e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6dfGpnQ3w50S3xDQmpWsmEcRZOJlMwFatG8byldO9viKDtB7blJsdRkzOBeZZPvp6DNj3bQ9mJA/9F3quqYwBg==