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
- 0f2b08abf25063f2e2ef57189581b6401c3ec51e2669fc0366d24570746c3554
- request
- 2e59d866560dfc1758e2aa0dca18702dfc70e1f687f7f6d3c6df855a0c938e23
- transaction
- 5a26548cd86a467eecdb1cefe7d7d5abb003986092de7377993e725df6d24a96computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28027
the chainentry 28027
- sealed to the entry before
- 7c255e5fa7663a1d1620b37ee755147954df9f14444d1a0e0387d9b2bf750e60
- this leaf
- 5dcbd723e58fdeb2521e7474285df4e8fe9a877e7bf0ff354de7b0ea169ecc46
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F8fijF/pg8VbaVDSP65ySrGuI6rKPx2KkeIImeyBgANq4mV9uazLP72Pq1Lw3L7koXSg6dxgVFLilbY0acgJCQ==