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
- 2caeb8094ed1e6e79e0606afd0ba9edca7df5040a26091f9fc800fb593469415
- request
- c301125eeb8615bff649a86a26642974b39585185002b37ee0a318ba531e9040
- transaction
- bcc8ac6d2d50a4a37e230fd55e607cde3271688aa99c9c5e3cc3ef3ac80a53dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49650
the chainentry 49650
- sealed to the entry before
- b8aa018eebc77c23c8690ea326139752b5fa328855f6b467b14bbe32373facf5
- this leaf
- a2dc615a59a92be8a94d04b21135e1a81aad8fffe53f4dd6bff375fad699e697
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A6WGxsQQxKUUvsz8qGYg3pG5urcLfWgzK5OJAZm/fj7gc1Xu0ChdkeUmP7t+wJgtvKs7OCL8fvwTtRyQpzKGCg==