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
- bca01666428eb6b9f370888085e6473d1aacc4b3806220038237efa81568c515
- request
- 35afa3d532d1ba030f8d9816990fa03de834f9368a1b926cb2b2ee993180048c
- transaction
- 3e1369601d277dc6ea2c8182520543dcc980f81998b2a8933d89196f90caae2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50916
the chainentry 50916
- sealed to the entry before
- 36d20a2d6b7baf3e320cb3f11242da806158dea59692a2387d845e190b02c64d
- this leaf
- ef4700e51502d3d2edeff2788350225fe71bd35d01702b69a3fb85cbe090a861
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SNY65A3+35PWRYvgW9ATHO8PavFvtUbmMRK2+poSalGYLcYHfJpV/FP90VHPF2pZSdEJ2/WyiMBzQ8okPGO9CA==