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
- 183a9d2fbde03c7524a77a48d21139ffe23740ebea8e42d157d7052cd1fdb022
- request
- b51daf9099e6a7065a1c7b4a00187716a54eb321e7152e7bcf25e0f3f6e8d17f
- transaction
- bbc67e54166fff73f8c389d7d2fbbe4ac937afbb4b7a5ed342793277b456f962computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20272
the chainentry 20272
- sealed to the entry before
- fee69e208e4febab5cbfd665e8be6df3e35f27e0400befde3868a7bbc1efd43d
- this leaf
- 0ca41412fd30f47bb408d265ddb9e902dd9e84e35214bc9ccf7883e3ee31da12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NnVxgiISjpYbTzHb1VrYDu0RaMqzwTgihqpVuxjPW1/zh7H4tw9+JVMgcuh4pfrNQgJz725UEFE3FXPNNygrCQ==