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
- 0d9fe95ee826fe84eead00b6ad460e7401d98fe454da7bf59c0b4214e1e7d455
- request
- d80c1451994413a1fcb5106264b174606ef2c48b7c6c3859da1d7e36ce70bfe1
- transaction
- 23e666e075e642ac20623ebc0aed7c0d6b25fc0346a800507aa9e6aca4a01783computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15827
the chainentry 15827
- sealed to the entry before
- 55ad65049cf770eb7c9c761871fedb4712f9d4ff9190a3000dc5a51d6de41935
- this leaf
- 2bc10294a034114f7a4504c248c12d5b355c58b3fc3a5014577aae635daee7d2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DfzMOrbve2J7fZtcJHWM6b6srsccFPmRAgf13w885XkvQcBGn2SNe7K5nqZI0WFxgxbd2amoGglvDFP1s/0cCQ==