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
- 49c08978912a29c1da369580c232f7fb7031b3916c9b347a29ffeab497996a11
- request
- 3e3368bab796873a1a91b6b617a244011125d5c5b8f9f770a7711a7491d14e73
- transaction
- b5197632d1c58e90aafae69a1c15aa66f928b4c3dfba1d13547986045c97a891computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17918
the chainentry 17918
- sealed to the entry before
- af7f67ec970b194a83c6f4283d838cf318e8d814adba49c27b259217397b00a8
- this leaf
- 2af987ca2baa1f0fb3ab5ba9d6c9d4f8a5b082658130207d89d86d63934c5767
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AH3QgutvohapfRAc3pMRaTaebainqyF5T8ZZRUfozmHhuf4sAPMRcbqGJjnXe0tBfnaOVJmviJhdQjsbmPqyCg==