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
- 3bd852b1890638f9852d6b368991c09740435b129fb7731572633cf58b654ef7
- request
- 57e13178886bb5db6a160426dde846102e0b986df9806b3e75a7970e632a8529
- transaction
- b6880bbaf5a6e1a2970a7300ef06ffcfc50f50b38590c828a0feb9a12d0b0402computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 526
the chainentry 526
- sealed to the entry before
- 72eba6fbe92e9938dbe549772238699707853cf31ad2d039d472f73b5bb15a23
- this leaf
- d7bbff0a2e912e54bc5cc21c6c8d7981b63b0961eb782261b80e0320d2da3413
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a6+qfP4Ke7g7dWpLIR7YXSrOKz/9fFqwa6EGAh/RQAXwxnBFq1m3n5BWFcJKqf5/DWZqUOspfe2zrtiTtUNUDA==