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
- 4eb39a8fb016fbe051a3d8c33c4f932bc2041fcccbd36af454d728330c7b11c3
- request
- 0a1bb550174e09ec0f7f3bb164f4a5c99f22ee2679dd7cb5d6bedb60d2af079e
- transaction
- 4ec913b428603916974f05814c0cb4fad67ffe36216645cc569c75b9d9c27a5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 751
the chainentry 751
- sealed to the entry before
- 8879878e8a38e307e50a17d1e46d5ca640b96a5019a55f6b9dbad656b4c8b58d
- this leaf
- fd7baceb2be56b4a225910e5d2a34a2ad65e8f909a70794a27ead74b37825502
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +lZ1wCi/9mrU532DPOMkugiFEKXLncLLZiYVIF4g8yVTFbeAABgZP3U33+9z68yKDWHsAfJ2y0IxAWkH/ZgXAA==