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
- c4e90fa33fc5603cdb889ebffc345aca05b28622bca3c601781a42c4f0f9407d
- request
- aad6a0c9932fffc997d49d990793412bb3b0a4bf4a755dc9ccdeb8aefce87af6
- transaction
- ce6b7a26b16a1995df4b9d547fc693b94185e07171583d2279e48d9fe57534cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42552
the chainentry 42552
- sealed to the entry before
- d71ec7b86ba6dd3df265d4e3575bd7ef8d39f1ca42e5b71480aa07291fe271a9
- this leaf
- dd4aef6d28123da07035b903ba21bbce86e08ae3c839c3413f3ec8a1bd396b6c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- upNohWkSYn1lWJwV7DGTSzu6/XKj17g3Hi5OVgcK94qpt3laijCnAC9q7chABykb7vXTv8tkEP/t9NMiYR0ZDQ==