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
- 71f76f1fa2b3ed717a65a7ed0471dd5aea35fe8db14490a0408f568b43d5b73d
- request
- 72eb41176b6bc8c866e3f2061a50e4150952203dddff9e10926475d95bc23e33
- transaction
- 8f4f3a1b43fa2668998720ea4252ae27755deaf7a0ab8a673ca65866f581753ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52046
the chainentry 52046
- sealed to the entry before
- a840280720b7168c17bd8c251fca03990d978ffc9e8de52431fbef9505cec849
- this leaf
- 978025ae5a17d1bc8fbc38da1cd0afcb270214bc205f7e3d3561024527724dd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d/pcYL72+vyAt8EYT1KrazgdCZLnpKBtONgYu743T0bhv9ek7yknxsZQCORPcW5tZEj276GvsXDflU/MKTB4Cg==