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
- 694ca838d34e99b1eaa6bb28c4339620ea280362fc106c46cc3310c7ba2efc42
- request
- ef05cb0434043105192305e24e1307c03cf9aa2ae6f9886ea369101a44795ae7
- transaction
- fbe6b05af7ddaad45b7253a7acfe0c7a7c523bc789013c41c4583b683240290fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9177
the chainentry 9177
- sealed to the entry before
- 6cea35acf512540ef361315cab687408f98b9f43a8f132014022459f5b4cb416
- this leaf
- a32fe24063995b84e91b8b699222284f0d48cb00dc96ccac32522cc6b25607fc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sDTdnFeJPS5u9riugCurY0JHus3NprTI+/JYMJo9C/Rl88W6FggCAa9Ip0RjiSQPpcl4hnWqNLG4YFg6wTprCw==