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
- d1428deb4608fd14fddc65e16be0046d41089b05b83c6ee5600c6568ac0b1849
- request
- ecd399c7d8b9b08036ed197576d14922ef0db3ebd5413fb2e158fb93d46be68b
- transaction
- a303708eaffd50f10cd42ce4d03a324f11304b3f3d12d2f19b1b5ccbfd7b11c3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60716
the chainentry 60716
- sealed to the entry before
- bac1726a5336d41ca7a6a1dd1d22984c7a3cd343ac40a9e5d6bf6df014458fb4
- this leaf
- ae687c05ad3621909b819498e9d6a44a7f1e65248302a1c84d68f0998744f389
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WzMA9EP3M+KTo37InUuOWviI9YHC/qz43EbGW1xs4qI10U7gB25Tstv3ILarX5ZLuhquT8+JkCUD60XCwD3tBg==