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
- 3c5259c9833f12ec428247c1bb208e025dc02802b8da71614d209c0914202f15
- request
- 16d9dd8d43c613d0dfe769734e207fb104a9c53c946ca1a1f055998941008937
- transaction
- 3ab56eb22d6530a1eb28db1046fc0d68b9cd0b1f70b28a103cdef2c90149c124computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55559
the chainentry 55559
- sealed to the entry before
- c1d680715edcf9627d2afebba0755627d50a1ff149554a80d9251c8bdb3ef9a6
- this leaf
- 10bdd3cf381f9333907999a573bdb0ee29add13690e3ab7cb75dcd2d70bb9d57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XcPbsPF5can8mk47ssNKWQVrfgcbmME9s3UvpI3X4KzGh4YRkZISAo41OvekV0H+AgvZSq/aEPlv8dBPrwIRAw==