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
- 0630e98fd0eb7f84a23784b9f998fefffd9d6d1856f62cd1013ac23049e726be
- request
- ac530593efb9933488033f73b15c9a375b77df477914730ffe14feb3cac81373
- transaction
- 7b60232cfa66c47c568937a6dc57f511ade6ad00086538b06638edf8d05de1c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51537
the chainentry 51537
- sealed to the entry before
- 7de4044d90b335cdf370b5c55773a0f383ace48e71159dbe1a7032257b6d133e
- this leaf
- df81db82a82a3b129fedb668346594119b96f4f83543b81d0a38ae6983a6459c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XDvdXKnfFfadqENTJ38iVCCGp/LoNUCQhITO4rFNAhAmmjEomyJPMXPX04UA8juEARTnI6EUJTnjsf/fm80UDg==