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
- 9ecb6d306fad31b50ad674d5cd8ec50d4f4b04d7c010a76eeecaa010f651b909
- request
- 163d1076feb9bed0cdddfd66414e90967628bdb3f19b516807099f53ab1be112
- transaction
- c3932baf1ce3b9dbc200d741510554969afee6f43cf8543543346ff705e316f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53769
the chainentry 53769
- sealed to the entry before
- 5dc213f69e8134add01dae3d47304f1f71bd376251307783ec89afc63dbf2a6a
- this leaf
- 5838500a4220b28a408057ebf970f4c0d059b7b0f192d91ec553ce6af9e8c796
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XKmWUDmonXRFRADOt6iWH5ZlyjbVGi0qe2J5iZe7WUSdrUUc5hjYqAEvlIMaI+niuCnWph7kEpp8xjJsgaQLBw==