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
- ad12e62b965065342991f8c8b922ccd2b7272df17a685a6eb013852618274676
- request
- 5acacd4329846ed6d4231512d7d208946c3d9b7a99506adec42487094c0a90c8
- transaction
- 8bcd0fce205bc1149ab19d1263cc44ca43cf90b4a33e0a4eebf353205f188ebdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16866
the chainentry 16866
- sealed to the entry before
- fbdeb7e9d4657ffef027093b60b2f6930d9d9c0454a5ff34ee8db0a6926f4d27
- this leaf
- f0c352337049c0cfbaafba78c8f2243cc707ab2e96baeed692944146ffddafd0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QSbaQoqj231jb3YZk9reZ0hml52sJ8fiQVN4GewWmjOfJa+B1Rbqu0lWHKODhGMt1Y6Ye6skKWzf2MoV6+m7AQ==