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
- 37f0e77553f0c67d37b30890f43844b8262d1491aec58b37ba4d055c694637b7
- request
- be162014a310087fd6b52b081fcc587669795f33ba49b8d003e44d4631a9a409
- transaction
- 32fe5dfda29144e4c2c6b615ea86f87fd01a7698e935179afb2c793e4eb028e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 47172
the chainentry 47172
- sealed to the entry before
- 6aa6d037746891b465b38dd5ac40091145f03cbed55bdd4be6a39fcfa6c36cf9
- this leaf
- beca6e42d8b3d79dcadd0f1095c312d6bd6973fb5c0ed80892676229d7ff27a6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I7Bn1zHsZNtDywrQ7yiuOWKhG9Byp6SLxNM0F24umFrN/eDWu+FSi2Kch3WXIzsKt1gISSe7hlEQFLmmKRF0Dg==