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
- 0f77e432a86f973e1d99f98f08ad8626b1d26fed9f1a4d4cb3db3cf0029675cc
- request
- badc4d0dc0c91fb369e866bf97ba0d7e694cad7cd406d37390511bcbb9130e0e
- transaction
- 2d35c146ed519588dc9e3f74a096d7fa3e18b7b46b6764d4294f3379d33ed53acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20726
the chainentry 20726
- sealed to the entry before
- b02625bd3c6ceaf929f18438a5c9669402d2b036ec3fe15f6b23f0841bcdf4ac
- this leaf
- a6d35f0c06a8601639ac6031eb71dc053334e8cae2c61c8bfbd5e2c186c8a09d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zO5pXCkkjko/nPJXM7M862F+y69hPYcEPGi3LIGB2BBd1AWAcSEQ7pz0nzvpxPzDeMZ/lJWJ8JbmaomvEsCuAg==