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
- 5b0ab5d532bd6bf9e0c5fa18304f6433ac7863d30dee0a0bdc6891159037fa19
- request
- aa7b9fa6a41faf573cd72aa89fb8209b34531bbd9e77644008c7e141f0812d97
- transaction
- 9b278909c24496705f51ba694711de90e07651ea5f2b7239d9945db11885577ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27112
the chainentry 27112
- sealed to the entry before
- ff8e30aad9f568bd9127483f7effabbbe45194fa4671225dcfb7d1e130c9617f
- this leaf
- 1ce154b6fb0e2882a2ebda26e87828f3af44c9f05ef692561514e6cc1186452a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Mir019akK0y2sRxNBvCjNHI8rPw2Dl9wtQM/PgDxHMVVO8GKBsvYWLhaGeBm5F3MZgz3p6xLdt0ryJl/OsvRAw==