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
- e7d0f19648500466e299f241e603b31f1b5d740ddb9b3c98b67629a239963da8
- request
- ad21386a8637edda58f29cbc1d7837f37c78ef574260cb6ac13bf5fc0604d0c2
- transaction
- 65e468bccc3223cb5c74e82ea3e5853b30100e608a26b2e01c02380969031cd5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1565
the chainentry 1565
- sealed to the entry before
- fbe21e343955ae0ea75d06e5df25133463705077db78546f610124a2f65b4fd3
- this leaf
- 01d05766d375112535077e6c95e1cceeb64a96a172cb36d7edfefe62809b7281
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CLZVCFZS2TFY9TS+Is/pPVd2LkDRcDPeVXKYIF4u4dXCav+FjQQD51QLApEta5WvTZGx7gbSoAzGMMl771doBg==