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
- 1213bad3de530717a021dec0771cd47ceb918535c9cce174d9aeec6da2b9ae8f
- request
- 89cd72b6637e43eaaac5bcf976493451e11b8663dac62c1bd6b5510f206408de
- transaction
- 7a870ac702c8dd1fc2e6fb56d09507bfc28d3800ec46bbbc285b90e18ba51115computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45369
the chainentry 45369
- sealed to the entry before
- e7e4177f3d4b13a37f0239bed5cdf2819ac629347ea4c68379b2b02a9dad1f05
- this leaf
- 59b17b580736b45f10c98740d9805a241409541b9908fe77c55a667bf4eb7681
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f+nkb7jtsTdO0W9DH8kgY1gaDDMIOVqg3Sh/zfledt47nCAmP2RLAnJIDDg/hP82CV+jbngh/2KEj0YAIwfDCQ==