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
- e6c249a7ec8dd3b83629734130b2967756a3ab8f4215f6232d541f261fa3f8ed
- request
- dbcb4905926423f0a25a968a03aa0b719eb561c982d33202040305f9ea60768c
- transaction
- 1b6167ab6c0d16d4a98e7ed653d1642a0cd5b11c706b57a1aa71334f30497312computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70600
the chainentry 70600
- sealed to the entry before
- ab339d6030680142fc5cc3c90cc1d009dcc202191392b4c6e8a2bc3582f1eb2b
- this leaf
- 04b65925a92144f42f8a99f1d7252dc2389d529f8ca2ae1740149fed8c635897
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pbz8hSgHqS1N6oQQn4cXVnwpHEqCdbMFOZxdPE8nFBKfW3HK8hRPuLhOSyIVMrbqqm6cRxSbcqcDxrw2OLHCBA==