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
- b080ee75a16c4832148475a19471ac7e680ce9b5b6b13ca6758114c6cb2d4d44
- request
- f680a5e46c84e421ce0394098f7f01488b9a618fab7a1c65ef3437696c92f79b
- transaction
- 463aad13a4f0cfa0b751c78364585bb9d9fa0c259b30ce24342c47ba7965c882computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47673
the chainentry 47673
- sealed to the entry before
- 6797944e3b0f14b6d2cc3c5713d9f21ea5ee62eece113fdcf2075e82b80e4cef
- this leaf
- ce2ee88ab2c9064d7dbd34f6b9956517e097a559eb6951a048269ff9ceb874c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rNVksnyQu81v4AP+ZZunajTTD2AB18lTW6sNXeZ7P7Abe8P1m5JnZMCdvovG6Kr/T7EN1ObkqRNSCq5KxrrXAA==