Ubik80 commited on
Commit
96790a5
·
verified ·
1 Parent(s): 2d049f0

Delete faq_knowledge.json

Browse files
Files changed (1) hide show
  1. faq_knowledge.json +0 -52
faq_knowledge.json DELETED
@@ -1,52 +0,0 @@
1
- [
2
- {
3
- "question": "How does our payment processing system handle real-time transactions?",
4
- "answer": "Our payment system uses an event-driven architecture that enables real-time handling. After validation, transactions are routed through our gateway and recorded in the ledger system in sub-second latency. Failover and retry mechanisms ensure high availability.",
5
- "category": "Payments"
6
- },
7
- {
8
- "question": "What are the steps involved in verifying a new customer account?",
9
- "answer": "New accounts undergo KYC: uploading ID, proof of address, and a selfie. Documents are verified via APIs and third-party services. Flags trigger manual review. Standard cases complete in under 5 minutes.",
10
- "category": "Onboarding"
11
- },
12
- {
13
- "question": "How do we detect and respond to fraudulent activity?",
14
- "answer": "We use rule-based and ML models to detect anomalies in real-time. Alerts trigger multi-factor re-authentication or account locking. All events are logged for SOC team review.",
15
- "category": "Security"
16
- },
17
- {
18
- "question": "How can customers dispute a transaction?",
19
- "answer": "Users submit disputes via app or dashboard. A case is created, and the transaction is reviewed. Temporary reversal may occur. Cases are resolved in 7–10 business days.",
20
- "category": "Support"
21
- },
22
- {
23
- "question": "What encryption methods are used to protect sensitive data?",
24
- "answer": "AES-256 is used for data at rest, TLS 1.3 for data in transit. Keys are rotated and stored via HSM. Sensitive info is tokenized and access-controlled via RBAC.",
25
- "category": "Security"
26
- },
27
- {
28
- "question": "How does our system ensure AML compliance?",
29
- "answer": "We use transaction monitoring, customer profiling, and watchlist checks. Risk scoring and SAR generation are automated. High-risk activity triggers enhanced due diligence.",
30
- "category": "Compliance"
31
- },
32
- {
33
- "question": "How does a third-party developer integrate with our APIs?",
34
- "answer": "Developers register for an API key, use HMAC-SHA256 for auth, and access sandbox & production environments. We provide RESTful APIs with Swagger docs and SDKs.",
35
- "category": "API"
36
- },
37
- {
38
- "question": "What rate limits are enforced on our public APIs?",
39
- "answer": "Default limit is 100 requests/minute per key. Headers like X-RateLimit-Remaining are included. Overages return 429 errors. Premium users may request higher limits.",
40
- "category": "API"
41
- },
42
- {
43
- "question": "How do we manage scheduled maintenance and downtime?",
44
- "answer": "Maintenance is announced 48h in advance. We use failover clusters and load balancers to avoid disruption. Status is shared in real-time on our status page.",
45
- "category": "Operations"
46
- },
47
- {
48
- "question": "What is the SLA for enterprise clients?",
49
- "answer": "99.99% uptime SLA. Includes global redundancy, fast support tiers, and SLA credits if violated. Critical issues get a 1h response window.",
50
- "category": "Enterprise"
51
- }
52
- ]