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
- bafeed130d1cb79e754306a7ff4e77f8a376e3a2f9e4d2646c889c45cc595fc8
- request
- a4375a021292684ac2098d34a9003e9720c18dcc848df52eb37464c4f07a8ec0
- transaction
- 01cfdff3fbabbfed7e3673b539b3ad29cab3d18f723ab4f5a5016b8769a122bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37426
the chainentry 37426
- sealed to the entry before
- 14a935356928a3c9e565ec14f154b44b1b5cdf5bf4111f3b4fe2810a8c9c77ba
- this leaf
- be70e44ba06310674efb9f1fba51c0310fa9384f38b22c520eab2c05844da9b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- M9n+L6K9MwDssFDj6LOTt1ABg5E7j+4QqD9GROtw1xlKRnnReAz0hFHTFpq85x9NEY+/BW4mfVciZwPFJRu3Aw==