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
- 72b6518f00d2a97d4946ee37e6519788ce885b5b4ed8ed533f315f3a779c0c20
- request
- e6a5573bd7c50cb18c3022b20383f27b5423876d304ce056ed4b076ed555e68c
- transaction
- 9e470c6ba29366f26342e158c1a232735bfe3978dc14d652fb76e9fa520287c4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43542
the chainentry 43542
- sealed to the entry before
- 28ad7c0fd873b559c0698e89fe7819d069c01c117d84a9b60cb02d060b938eb5
- this leaf
- 024b048db19e8f21cb2e652e5214f552c7e8dc8a84af33bab422306c30a1abf4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pYai/UK+bY7dy3wFtcXMKtOSyp3jtFg9gDPmUYfrj9TZfcN6O57MfYPFTTv22R9V6mdoUhxAK+QJrIhoDmvjBw==