lendler.io
Home
Partners
Investors
Product
Transparency
Pricing
Docs
EN
Partner with us
Docs
/
Banks & Custodians
Banks FAQ
Technology integration, compliance, and partnership Q&A for banking institutions
Back to Library
🟥 A. Basic Understanding (1-20)
1.
What is Lendler?
2.
What value for banks?
3.
Compete with bank APIs?
4.
Does bank transfer custody?
5.
Bank use cases?
6.
Impact on core banking?
7.
Same as crypto exchanges?
8.
Pass bank internal governance?
9.
Blockchain expertise needed?
10.
Bank-side risks?
11.
Integrate with bank KYC?
12.
Handle personal information?
13.
Which stablecoins can banks handle?
14.
Support JPY stablecoins?
15.
Compete with existing remittance systems?
16.
Need new department in bank?
17.
What should bank configure?
18.
Does bank store stablecoins?
19.
Does bank manipulate tokens?
20.
Impact on bank internal controls?
🟧 B. Regulation, Legal & Risk (21-40)
21.
FSA alignment?
22.
Exchange business registration needed?
23.
Money transfer business applicable?
24.
Relationship with Banking Act?
25.
AML/CFT?
26.
FATF compliance?
27.
Anti-social forces check?
28.
Offshore regulations?
29.
Tax matters?
30.
Contract form?
31.
Bank legal liability scope?
32.
Stablecoin collapse risk?
33.
Coordination with audit firms?
34.
Financial crime risk?
35.
US SEC risk?
36.
MiCA compliance?
37.
Consumer protection regulations?
38.
License needed?
39.
Data management regulations (GDPR etc.)?
40.
Compliance department concerns?
🟩 C. Security (41-60)
41.
Greatest security strength?
42.
Can internal architecture be disclosed?
43.
Smart contract safety?
44.
Information leakage risk?
45.
Internal network structure?
46.
Where are signatures processed?
47.
Key management?
48.
If attacked?
49.
Risk if Lendler held custody?
50.
DDOS countermeasures?
51.
Failure behavior?
52.
Fraud transaction detection?
53.
Bank API connection security?
54.
Transaction logs?
55.
Compliance logs?
56.
Do attack vectors increase?
57.
Third-party audit?
58.
Penetration testing?
59.
Application layer vulnerabilities?
60.
Chain risks?
🟦 D. Integration & Operations (61-80)
61.
Bank system integration workload?
62.
Core banking integration?
63.
Report function?
64.
Deposit confirmation method?
65.
Withdrawal approval flow?
66.
Notification method?
67.
Custom rule settings?
68.
Maintenance frequency?
69.
Failure information sharing?
70.
Batch processing needed?
71.
Operation permission management?
72.
Usage log retention period?
73.
International remittance use?
74.
Stablecoin switching?
75.
Fee settings?
76.
Erroneous transfer handling?
77.
Multi-currency support?
78.
Scrubbing (name matching) support?
79.
Comparison with SWIFT?
80.
AML alert sharing?
🟫 E. Business Model & Strategy (81-100)
81.
Bank-side revenue points?
82.
Value for bank customers?
83.
Bank branding post-integration?
84.
User growth prospects?
85.
SME provision?
86.
Large enterprise provision?
87.
Joint use with overseas offices?
88.
Must bank handle tokens?
89.
Bank competitive advantage?
90.
Long-term strategy?
91.
Market timing?
92.
Why should banks enter now?
93.
Which regions are strong?
94.
Scale limitations?
95.
Cross-sell with bank APIs?
96.
Weapon for Web3 corporate acquisition?
97.
Competitive differentiation?
98.
Bank future role?
99.
Lendler long-term vision?
100.
Top reason banks should implement?