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
- d11300ffcb85bc2e9e2fd3befab86bc8f6d6f8515464ce2385d1b41153a052b9
- request
- 63662b60b578d3ee78fd10040ffd1447b6ed2d5010740a8d162d7061bd4cc1b0
- transaction
- ff54e2f8773d42d883ba22a14d014801cf2fc5a1cb1eeaec9af1e294bd7aadefcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43324
the chainentry 43324
- sealed to the entry before
- 9600d692978c5f1405bcf407ff1ed01a767f0faf3f7b7e5d2f386dc86b68cc6f
- this leaf
- 09e0e4cd0313317c1c35e270aa1b0bb4930637a0b17f74c66ffd739ca6cac8b7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DthpswhaZLNyJCGhy0Claa+amMACGgWwTck/WrAsohSo8gzT1GYQqvyk9ZC7/Ew28+Ph2j8WXtfTDQE/7M2iAQ==