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
- ec054e9ed8e00f592bc442d8536f2be5c5c115a843a9b82cdf8c965f9cc5573d
- request
- 305f5c1c6b8ecd565c3309c2092bbe7ec51b6c638ca8647ec7d45c42592d894a
- transaction
- 33ce47de6234715e732976dbd07c96f34bcbd6d8c8d55eeaeb1c0215aee2cedacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38402
the chainentry 38402
- sealed to the entry before
- b176b8484b271d98df79d364819840eaeb720ebf80117b4195279ec637e015be
- this leaf
- 5b3d78173924d1741371cdd59bde9a3625696169dfbea4a88288d9b57ba3903d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hIS8Cdf+0+DTtkQOqoEVtZlOCoJoFV3NpuaAuSUMzAxYfdhhIJRahbJunLbhAs6alCTrJVevouPzx0GUhsNQAA==