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
- 5cf498abb259074d80e33a90ec459d4323d34b5a2a5e60acc2bf21cf52e308b0
- request
- cb6af50297b4664cb20d16d55e1bd795eaae91137dca7270fa55b2ec502e0abe
- transaction
- 5835e7d6f965d01ba112155af0f0b8839fbbd2610716f6aa5e2e14e9c85f451bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43610
the chainentry 43610
- sealed to the entry before
- 8d80ce43475b553e0396f9c6158321514237ef5cbcbf31cb9065aa1ce75fe11e
- this leaf
- 716c2466da5e5d580bcfb306703343b2af424bd3b945777de07e986ffab12c17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 86lDC68CL7TY2AqGt/a3PTo9f7WQ1GvJQbwpD51HcVGLPaO2XI0nuuGBaktLA1ddTLZKmUM9VZBvyHkkLjHwDw==