- PRODUCTS & FEATURES | EN
- PAYSTAR FEATURES | RU
- MERCHANT API DOC | EN
- Introduction
- Glossary
- Authorization key
- Sandbox
- Additional fields
- Currencies
- Bank names
- Telecom operators
- Callbacks
- Error descriptions
- Tech FAQ
- Events
- Payment history v2
- Integratins
- Balance H2H
- Deposit H2H - Card & P2P
- Deposit H2H - Token
- Deposit H2C - Card
- Deposit status H2H - PayStar ID
- Deposit status H2H - Merch ID
- Payout H2H
- Payout status H2H - PayStar ID
- Payout status H2H - Merch ID
PayStar in 100 Questions
Who we are and what problem we solve#
1. What is PayStar?
2. Is PayStar a PSP or an orchestration layer?
3. What core pain does PayStar solve for a merchant?
4. Who is PayStar the best fit for?
5. What are the top 3 outcomes merchants expect from PayStar?
6. Can we start small without a full migration?
7. Does PayStar mean “rewrite everything”?
8. What if we already use another orchestrator or a custom stack?
9. What do you mean by “quality management”?
10. Where does conversion improvement come from in practice?
11. What does “no vendor lock-in” mean here?
12. Which KPIs are most commonly improved with PayStar?
Products: GQI / Direct Connect / Core#
13. What are PayStar’s main merchant products?
14. How do we pick the right product in 30 seconds?
15. What is GQI in plain English?
16. When is GQI especially useful?
17. Why can GQI access be restricted and how do we get it?
18. What is Direct Connect?
19. Who is Direct Connect ideal for?
20. What is PayStar Core?
21. When do we need Core instead of Direct Connect?
22. Can we combine products?
23. Can we “start simple” and make configuration more advanced later?
24. What do you mean by “visual pipelines”?
25. What bundles do merchants buy most often?
Coverage, methods, providers#
26. What payment types can PayStar cover?
27. Can we roll out GEOs step by step?
28. What if the provider we need is not integrated yet?
29. Can we connect multiple providers for the same method?
30. Can we disable a method/provider quickly during an incident?
31. Can PayStar show where conversion drops?
32. What if a provider fails only in a single GEO?
33. Can we whitelist allowed methods only?
34. Can we separate flows by brands/projects?
35. Can we start with one method and expand later?
Onboarding, pricing, risks, processes#
36. How do we start: 4 steps?
37. What inputs do you need to estimate our case quickly?
38. Can we get a demo before signing a contract?
39. Can we start with “diagnostics” without integration?
40. How long does a pilot take?
41. How do we measure pilot success?
42. Which merchant teams are usually involved?
43. How many engineers do we need on the merchant side?
44. Do we need changes in our checkout/product?
45. Can we migrate without stopping payments?
46. Can we run two payment stacks in parallel?
47. What delivers the fastest business impact?
48. What if a provider starts mass-declining transactions?
49. How does PayStar reduce losses from provider downtime?
50. Do you offer 24/7 support?
51. Do we get an account manager / technical contact?
52. How do you communicate maintenance windows and incidents?
53. What does incident management look like?
54. How fast can we enable a new method or GEO?
55. How do new PSP integrations work?
56. What integration risks are most common?
57. What usually breaks conversion for merchants?
58. How does PayStar save money (not just improve approval)?
59. Does PayStar reduce ops/support load?
60. What does the finance team get?
61. What is reconciliation and why does the business need it?
62. Can we generate exports for accounting?
63. Can we connect BI (Power BI / Tableau / Looker / Redash)?
64. What documents are typically included in contracting?
65. Where are SLA and responsibilities defined?
66. How do you handle privacy and GDPR?
67. Does PayStar operate under PCI DSS?
68. Do we (the merchant) need our own PCI DSS?
69. What security controls are typically available?
70. Who is responsible for KYC/AML and end-user compliance?
71. Do you provide anti-fraud tools?
72. Can we limit users/amounts/frequency?
73. Can PayStar reduce chargebacks?
74. What commercial models are typical?
75. Is there a setup/onboarding fee?
76. Can we start on a minimal plan and scale up?
77. Are annual contracts and discounts available?
78. Can we get a commercial proposal for our exact case?
79. Can we brand the payment page?
80. Can we use our own domain for checkout/portals?
81. Can we split access inside our team?
82. Can we restrict access for contractors/agents?
83. How does GQI help in negotiations with PSPs?
84. Can we evaluate multiple providers in parallel?
85. Can we run A/B splits and controlled tests?
86. Who manages routing rules — us or you?
87. Can we set up an “autopilot” so ops doesn’t tweak rules daily?
88. What if we don’t have an in-house payments expert?
89. How do you accelerate a new GEO launch?
90. Can we use PayStar only for a part of our payment flows?
91. What if we have a complex structure (multiple legal entities/brands)?
92. Can we split traffic by brands with different strategies?
93. How does PayStar reduce human error in payments?
94. What reporting does C-level usually want — and how does PayStar help?
95. What will your CFO ask — and what’s the answer?
96. How do you ensure transparency of decline reasons?
97. Do you train the merchant team?
98. Where can we find docs and integration examples?
99. What’s the #1 recommendation to make integration smooth?
100. What’s the best next step today?