CIP FAQ - Sales Product Line & Sales Objections

1. What is ChainIT Pay?

ChainIT Pay is a digital payments platform designed to help businesses process payments securely, efficiently, and at scale. We support modern payment experiences by combining payment processing, identity verification, transaction routing, compliance support, and operational visibility into one connected ecosystem.

2. What problem does ChainIT Pay solve?

ChainIT Pay helps businesses reduce friction in how they accept, manage, and monitor payments. Many organizations struggle with disconnected systems, slow onboarding, limited visibility, fraud risk, compliance gaps, or rigid payment infrastructure. ChainIT Pay is designed to simplify those challenges and support secure, scalable payment operations.

3. Who is ChainIT Pay built for?

ChainIT Pay is built for businesses, platforms, organizations, and partners that need reliable digital payment infrastructure. This may include merchants, software platforms, service providers, referral partners, ISVs, and organizations that need payment acceptance, transaction visibility, identity verification, or payment workflow support.

4. What makes ChainIT Pay different?

ChainIT Pay is not positioned as just another payment processor. We focus on creating a connected payments ecosystem that supports secure transactions, intelligent routing, identity verification, compliance awareness, and operational scalability. Our value is in helping businesses process payments while also improving trust, visibility, and control.

5. Is ChainIT Pay only a payment processor?

No. ChainIT Pay supports payment processing, but our broader value is payment infrastructure. That includes tools and workflows around transaction routing, digital payment experiences, identity verification, risk awareness, partner support, and operational efficiency.

6. What types of payments can ChainIT Pay support?

ChainIT Pay is designed to support digital payment experiences across multiple business use cases. Depending on the customer need, this may include card payments, online payments, invoicing, payment links, recurring payments, partner-driven payments, and other modern payment workflows.

7. Can ChainIT Pay help businesses accept online payments?

Yes. ChainIT Pay can help businesses accept payments online through digital payment workflows. This can be especially helpful for businesses that want to move away from manual payments, disconnected portals, or outdated payment collection processes.

8. Can ChainIT Pay support in-person payments?

Depending on the customer’s setup and payment needs, ChainIT Pay may support or integrate with in-person payment solutions. AEs should confirm whether the prospect needs terminals, point-of-sale integration, mobile payment acceptance, or online-only payment workflows.

9. Does ChainIT Pay support recurring billing?

ChainIT Pay can support recurring billing use cases depending on the customer’s payment structure and platform requirements. This is useful for memberships, subscriptions, service contracts, monthly billing, or any business model that requires repeat payments.

10. Can ChainIT Pay support invoicing?

Yes. ChainIT Pay can support invoice-based payment workflows where customers need to send payment requests, collect funds, and track payment activity. This is valuable for service businesses, professional organizations, B2B billing, and larger invoice transactions.

11. What industries does ChainIT Pay serve?

ChainIT Pay can serve a wide range of industries where secure and efficient payment acceptance is important. This may include healthcare-adjacent businesses, professional services, insurance-related businesses, field services, associations, platforms, software companies, and other merchants or organizations that need modern payment infrastructure.

12. Is ChainIT Pay industry-specific?

No. ChainIT Pay is not limited to one industry. However, our approach is especially valuable in industries where trust, compliance, identity, payments, onboarding, and operational reliability matter.

13. Can ChainIT Pay support high-risk businesses?

Potentially, but every business must go through appropriate review. ChainIT Pay must evaluate risk, underwriting requirements, compliance considerations, sponsor bank expectations, and the nature of the business before determining whether the merchant can be supported.

14. What should I say if a prospect asks whether we approve everyone?

We do not approve everyone automatically. ChainIT Pay takes responsible onboarding seriously. Each merchant or partner must be reviewed to ensure the business model, risk profile, payment activity, and compliance expectations align with what we can support.

15. Why does underwriting matter?

Underwriting protects the merchant, ChainIT Pay, our banking relationships, and the broader payment ecosystem. It helps confirm that the business is legitimate, the risk is understood, and the payment activity can be supported safely.

16. What information is usually needed for onboarding?

Typical onboarding information may include business name, legal entity details, ownership information, tax identification, business address, website, bank account details, processing history, expected transaction volume, average ticket size, and information about the products or services being sold.

17. How long does onboarding take?

Onboarding time depends on the completeness of the information provided, the risk profile of the business, and whether additional review is needed. Clean, complete applications generally move faster. Missing documentation, unclear business models, or higher-risk activity may extend the review process.

18. Can ChainIT Pay help merchants get set up faster?

Yes. We can help streamline the onboarding process by making sure the merchant understands what information is needed upfront. AEs should encourage prospects to provide complete and accurate information early to avoid delays.

19. What is KYB?

KYB stands for “Know Your Business.” It is the process of verifying a business’s identity, ownership, legitimacy, and risk profile. KYB helps ensure that businesses using payment services are properly reviewed and validated.

20. What is KYC?

KYC stands for “Know Your Customer.” In payments, this often refers to verifying the identities of individuals associated with a business, such as owners, controllers, or authorized representatives. KYC helps reduce fraud and meet compliance expectations.

21. Why does ChainIT Pay care about identity verification?

Identity verification helps reduce fraud, protect the payment ecosystem, and ensure that businesses and individuals are who they say they are. It is an important part of building trusted payment experiences.

22. Does ChainIT Pay help with fraud prevention?

Yes. ChainIT Pay is designed with fraud awareness and risk controls in mind. While no payment system can eliminate fraud entirely, our approach supports better visibility, verification, monitoring, and responsible transaction management.

23. What is intelligent payment routing?

Intelligent routing refers to using payment logic to help transactions move through the most appropriate payment path based on performance, reliability, cost, risk, or operational needs. The goal is to improve payment success and reduce unnecessary friction.

24. Why does payment routing matter?

Payment routing matters because poor routing can lead to failed transactions, higher costs, poor customer experience, and operational inefficiency. Better routing can help improve authorization performance, reliability, and payment outcomes.

25. Can ChainIT Pay improve payment approval rates?

Potentially, yes. Approval rates depend on many factors, including card issuer behavior, merchant category, transaction type, fraud controls, customer information, and routing logic. ChainIT Pay can help businesses evaluate and improve payment workflows that may affect payment success.

26. Does ChainIT Pay replace my existing payment provider?

It depends. In some cases, ChainIT Pay may replace an existing provider. In other cases, we may support a specific payment use case, improve part of the payment workflow, or work alongside existing systems depending on the business need.

27. What if a prospect already uses Stripe, Square, PayPal, or another provider?

That does not automatically mean ChainIT Pay is not a fit. AEs should ask what is working, what is not working, where the business feels friction, whether they need more control, whether pricing is an issue, whether onboarding or support is a problem, and whether they need more advanced payment, compliance, or identity capabilities.

28. How should I position ChainIT Pay against Stripe?

Stripe is a strong self-service payment platform. ChainIT Pay should be positioned around consultative support, payment workflow design, partner alignment, risk awareness, and business-specific payment infrastructure. The conversation should focus on the prospect’s needs, not simply “Stripe versus ChainIT Pay.”

29. How should I position ChainIT Pay against Square?

Square is commonly used by small businesses for simple point-of-sale needs. ChainIT Pay may be a better fit when a business needs more tailored payment workflows, online payment infrastructure, partner support, business-specific underwriting, or a more scalable payments strategy.

30. How should I position ChainIT Pay against PayPal?

PayPal can be useful for simple consumer-facing checkout experiences. ChainIT Pay should be positioned as a more business-focused payment infrastructure option for organizations that need greater control, visibility, support, and scalable payment workflows.

31. Does ChainIT Pay offer better pricing?

Pricing depends on the merchant’s business model, volume, risk profile, transaction type, and required services. ChainIT Pay aims to provide competitive, transparent, and value-aligned pricing, but AEs should avoid promising lower pricing before reviewing the full opportunity.

32. What should I say when a prospect asks, “What are your rates?”

A good answer is: “Pricing depends on your business type, transaction volume, average ticket, risk profile, and the payment workflows you need. If we can understand your current setup and goals, we can review the best structure and determine whether we can create a better overall solution.”

33. What information do we need to quote pricing?

AEs should gather current processing volume, average transaction size, monthly transaction count, current provider, current effective rate if available, card-present versus card-not-present mix, chargeback history, industry, payment methods needed, and any special requirements such as recurring billing, invoicing, or platform payments.

34. Can ChainIT Pay save merchants money?

Potentially. Savings depend on the merchant’s current provider, rate structure, transaction volume, risk profile, and operational needs. However, the value of ChainIT Pay should not be limited to price alone. We also help with payment experience, reliability, visibility, support, and scalable infrastructure.

35. Why should we avoid selling only on price?

Selling only on price turns ChainIT Pay into a commodity. Our stronger value proposition is secure, scalable, reliable payment infrastructure with support, risk awareness, and operational value. Price matters, but it should be part of a broader business conversation.

36. What is the ideal first discovery question?

A strong opening question is: “How are you accepting payments today, and what part of that process creates the most friction for your business, your team, or your customers?”

37. What are the best discovery questions for AEs?

AEs should ask:

How do you accept payments today?
What provider are you currently using?
What is working well?
What is frustrating or slowing you down?
What is your monthly processing volume?
What is your average transaction size?
Do you process mostly online, in person, or both?
Do you need recurring billing or invoicing?
Have you experienced chargebacks or fraud issues?
Do you need payment reporting or reconciliation support?
Are you looking for lower cost, better experience, better support, or all three?

38. What is a good short elevator pitch for ChainIT Pay?

ChainIT Pay helps businesses build secure and scalable payment experiences. We support digital payment acceptance, identity verification, payment routing, and operational visibility so organizations can process payments more efficiently and with greater control.

39. What is a more consultative pitch?

ChainIT Pay helps businesses modernize how they accept and manage payments. Instead of only looking at rates, we look at the full payment workflow, including onboarding, payment acceptance, fraud exposure, reporting, customer experience, and long-term scalability.

40. What is the main value proposition for business owners?

ChainIT Pay helps business owners reduce payment friction, improve control, support secure transactions, and build a payment process that can scale with the business.

41. What is the main value proposition for operations leaders?

For operations leaders, ChainIT Pay helps create cleaner workflows, better visibility, fewer manual steps, more reliable onboarding, and improved payment process control.

42. What is the main value proposition for finance leaders?

For finance leaders, ChainIT Pay can support better transaction visibility, cleaner reporting, improved reconciliation, predictable payment workflows, and a clearer understanding of payment costs.

43. What is the main value proposition for technology leaders?

For technology leaders, ChainIT Pay offers payment infrastructure that can support digital workflows, integrations, intelligent routing, and scalable payment experiences.

44. What is the main value proposition for partners or referral sources?

For partners, ChainIT Pay provides a way to offer payment solutions to their customers while supporting revenue opportunities, customer retention, and stronger business relationships.

45. Can ChainIT Pay work with referral partners?

Yes. ChainIT Pay can work with referral partners depending on the relationship structure, compliance requirements, and business model. Partner opportunities should be reviewed carefully to ensure operational clarity and alignment.

46. Can ChainIT Pay work with software platforms?

Yes. ChainIT Pay may support software platforms that need embedded payment capabilities, payment workflows, or payment-related support for their customers. AEs should determine whether the platform needs payment acceptance, onboarding, revenue share, reporting, or integration support.

47. What is an ISV?

An ISV is an Independent Software Vendor. In simple terms, it is a company that builds software for a specific industry or business function. ISVs often need payment capabilities inside their platforms so their users can accept or manage payments.

48. Why are ISVs important to ChainIT Pay?

ISVs can create scalable payment opportunities because one software platform may serve many merchants or end users. If ChainIT Pay supports the platform, it may create ongoing payment volume, partner revenue, and long-term growth opportunities.

49. What is an ISO?

An ISO is an Independent Sales Organization. In payments, ISOs often help sell merchant services or refer merchants to payment providers. ChainIT Pay may work with partner organizations where the relationship is properly structured and compliant.

50. What is a merchant account?

A merchant account allows a business to accept card payments and receive funds from customer transactions. It is part of the payment infrastructure that connects the customer, card network, issuing bank, acquiring bank, and merchant.

51. What is a payment gateway?

A payment gateway is technology that securely captures and transmits payment information between the customer, merchant, and payment processor. For online payments, the gateway is a key part of the checkout and authorization process.

52. What is a processor?

A processor helps move payment transactions through the financial system. It communicates with card networks, banks, and other payment infrastructure to authorize, clear, and settle transactions.

53. What is a sponsor bank?

A sponsor bank is a regulated financial institution that supports payment activity and helps enable access to the payment networks. Sponsor bank expectations matter because payment companies must operate within approved risk, compliance, and underwriting standards.

54. Why do sponsor banks matter to prospects?

Sponsor banks help ensure the payment ecosystem is safe and compliant. For prospects, this means responsible onboarding, proper review, and payment services that are built on a regulated financial foundation.

55. What are chargebacks?

A chargeback happens when a cardholder disputes a transaction and the funds may be pulled back from the merchant while the dispute is reviewed. High chargeback levels can create risk for the merchant and payment provider.

56. How can merchants reduce chargebacks?

Merchants can reduce chargebacks by using clear billing descriptors, strong customer communication, accurate product or service descriptions, proof of authorization, clear refund policies, good customer service, and proper fraud controls.

57. Does ChainIT Pay help monitor chargeback risk?

ChainIT Pay can help businesses understand and manage chargeback exposure as part of the broader payment and risk process. AEs should avoid promising that chargebacks can be eliminated entirely.

58. What should I say if a merchant has high chargebacks?

A good answer is: “We would need to understand what is causing the chargebacks, how often they occur, what your current dispute process looks like, and whether the issue is related to fraud, customer confusion, billing practices, or fulfillment. From there, we can determine whether and how we may be able to support you.”

59. What is card-not-present risk?

Card-not-present risk applies when the card is not physically presented, such as online or phone payments. These transactions may carry higher fraud and dispute risk because the cardholder and card are not physically verified at the point of sale.

60. What is PCI compliance?

PCI compliance refers to security standards for protecting cardholder data. Businesses that accept card payments must follow applicable payment security requirements. ChainIT Pay can help support secure payment workflows, but merchants are still responsible for following applicable requirements for their business.

61. Does ChainIT Pay store cardholder data?

AEs should not answer this in technical detail unless confirmed by the product or compliance team. A safe answer is: “ChainIT Pay is designed to support secure payment workflows. For specific questions about card data handling, tokenization, storage, or PCI scope, we can involve our technical or compliance team.”

62. Is ChainIT Pay secure?

Yes. ChainIT Pay is designed with security, trust, and responsible payment operations in mind. Security is part of how we approach payment acceptance, identity verification, transaction processing, and risk management.

63. Can ChainIT Pay support enterprise clients?

Yes. ChainIT Pay is built with scalability in mind and may support enterprise clients depending on their requirements, volume, integrations, compliance needs, and operational complexity.

64. What makes an enterprise opportunity different?

Enterprise opportunities often require more detailed review, integration planning, security documentation, compliance review, pricing structure, contract review, reporting needs, and stakeholder alignment.

65. When should an AE bring in leadership?

AEs should bring in leadership when the opportunity involves large volume, complex pricing, unusual risk, enterprise requirements, legal or compliance questions, strategic partnerships, software integrations, or anything that may require special approval.

66. When should an AE involve operations?

Operations should be involved when there are questions about onboarding timelines, implementation requirements, support capacity, data migration, special workflows, partner setup, or anything that affects how the customer will actually be supported after the sale.

67. When should an AE involve compliance or risk?

Compliance or risk should be involved when the merchant has a complex business model, elevated chargeback history, regulated activity, unclear ownership, unusual transaction patterns, high processing volume, or any concern that the business may not fit standard underwriting expectations.

68. What should AEs avoid promising?

AEs should avoid promising:

Guaranteed approval
Guaranteed savings
Guaranteed approval rates
Guaranteed onboarding timelines
Guaranteed fraud prevention
Custom features without approval
Support for high-risk activity without review
Pricing that has not been approved
Integration timelines that have not been confirmed
Anything that requires legal, compliance, product, or operations approval

69. What is the best way to handle a pricing objection?

A good answer is: “Price is important, but the lowest rate is not always the lowest total cost. We should also look at failed payments, chargebacks, support issues, reporting gaps, reconciliation time, and how much manual work your current process creates.”

70. What is the best way to handle a “we already have a processor” objection?

A good answer is: “That makes sense. Most businesses we speak with already have something in place. The question is whether it is still the right fit. What would you improve about your current payment setup if you could?”

71. What is the best way to handle a “we use Stripe” objection?

A good answer is: “Stripe can be a good solution for many businesses. What we would want to understand is whether your current setup gives you the level of support, visibility, pricing structure, risk control, and workflow flexibility your business needs as it grows.”

72. What is the best way to handle a “we are not ready” objection?

A good answer is: “No problem. It may still be useful to understand your current setup, so when the timing is right, we know what would need to improve. What would have to change for payments to become a priority?”

73. What is the best way to handle a “send me information” response?

AEs should ask one more question before sending generic information. A good response is: “Absolutely. So I send the most relevant information, are you mainly interested in pricing, online payments, recurring billing, fraud reduction, reporting, or replacing your current provider?”

74. What should AEs document in HubSpot after a call?

AEs should document the current provider, payment pain points, monthly volume, average ticket, payment methods used, decision maker, timeline, objections, next step, and whether the prospect may need a quote, demo, onboarding review, or leadership involvement.

75. When should a Contact become a Lead in HubSpot?

A Contact should become a Lead when there is a real reason to work the person as a sales opportunity. This may include a referral, inbound interest, meeting request, campaign engagement, direct response, or a clear sales follow-up opportunity.

76. When should a Company become a Lead in HubSpot?

A Company should become a Lead when the business appears to be a real target account and there is enough reason for sales to actively pursue it. This could come from a referral list, campaign engagement, industry fit, existing relationship, or identified payment need.

77. When should a Lead become a Deal?

A Lead should become a Deal when there is real commercial opportunity. This means there is engagement, a known business need, a potential product fit, and a reasonable path toward a sale, quote, proposal, contract, or implementation.

78. What counts as engagement?

Engagement may include a meeting, email reply, call conversation, demo request, pricing discussion, submitted application, referral introduction, webinar or campaign response, or any meaningful interaction that shows the prospect is active and worth pursuing.

79. What should be associated to a Deal?

A Deal should be associated with the correct Company and Contact whenever possible. This keeps the sales record clean and makes it easier to see who is involved, what business the opportunity belongs to, and where the deal sits in the pipeline.

80. Why does association hygiene matter in HubSpot?

Association hygiene matters because disconnected records create confusion. If Contacts, Companies, Leads, and Deals are not connected correctly, the team may lose visibility, duplicate work, miss follow-ups, or misunderstand pipeline value.

81. What is the difference between a Contact and a Company?

A Contact is a person. A Company is the business or organization that person belongs to. For example, Jim Meadows would be a Contact, and his company or clinic would be the Company record.

82. What is the difference between a Lead and a Deal?

A Lead is a person or company that sales is actively working. A Deal is a real revenue opportunity that belongs in the pipeline. Not every Lead should immediately become a Deal.

83. What is the difference between a Company and a Deal?

A Company is the business account. A Deal is a specific sales opportunity with that business. One Company can have multiple Deals over time if there are multiple opportunities, products, locations, or expansion opportunities.

84. Why should AEs create views in HubSpot?

Views help AEs organize their work. A view can show only the Contacts, Companies, Leads, or Deals that matter to that rep. This helps with follow-up, prioritization, and pipeline management.

85. What are useful HubSpot views for AEs?

Useful views include:

My Contacts
My Companies
My New Leads
My Open Deals
No Recent Activity
Follow-Up Needed
Recently Engaged Contacts
Companies Without Associated Deals
Contacts Without Associated Companies
Deals Closing This Month

86. What is a good daily workflow for AEs in HubSpot?

AEs should start by reviewing tasks, new leads, engaged contacts, open deals, and follow-ups due that day. Then they should work priority outreach, log activity, update lead status, create deals when appropriate, and confirm that records are properly associated.

87. What is the biggest HubSpot mistake AEs should avoid?

The biggest mistake is working outside the system. If calls, emails, notes, lead status, and deals are not documented in HubSpot, leadership cannot see the real pipeline and the team cannot support the customer properly.

88. What is the second biggest HubSpot mistake?

Creating duplicate or incomplete records. AEs should always search before creating new Contacts or Companies and should complete required fields as accurately as possible.

89. What should AEs do before creating a new Company?

AEs should search HubSpot first by company name, domain, and any known contact email domain. If a Company already exists, they should use the existing record instead of creating a duplicate.

90. What should AEs do before creating a new Contact?

AEs should search by email address first. Email is the cleanest identifier for Contacts. If the Contact already exists, update the existing record instead of creating a duplicate.

91. How should AEs talk about ChainIT Pay in one sentence?

ChainIT Pay helps businesses process payments securely and efficiently while giving them better control, visibility, and scalability across their payment operations.

92. How should AEs talk about ChainIT Pay to a business owner?

“We help businesses simplify payment acceptance, reduce friction, and build a payment setup that can grow with them.”

93. How should AEs talk about ChainIT Pay to a finance leader?

“We help improve payment visibility, cost clarity, transaction tracking, and operational control around how money moves through the business.”

94. How should AEs talk about ChainIT Pay to a technology leader?

“We provide payment infrastructure that can support digital workflows, integrations, secure transactions, and scalable payment experiences.”

95. How should AEs talk about ChainIT Pay to a partner?

“We help partners bring payment solutions to their customers while creating a stronger customer relationship and potential revenue opportunity.”

96. What is the best closing question after discovery?

A strong closing question is: “Based on what we discussed, would it make sense for us to review your current setup and see whether ChainIT Pay can improve cost, experience, or scalability?”

97. What is a good next-step question after a strong call?

A good next-step question is: “Who else should be involved in the next conversation so we can make sure we cover the business, financial, and technical requirements?”

98. What should AEs say if they do not know the answer?

AEs should say: “That is a good question. I want to make sure I give you the right answer, so I am going to confirm that with our team and follow up.” AEs should not guess on pricing, compliance, underwriting, technical integrations, or legal questions.

99. What is ChainIT Pay’s sales philosophy?

ChainIT Pay should sell through discovery, education, and fit. The goal is not to force every prospect into the pipeline. The goal is to identify where we can create real value, support the business responsibly, and build long-term relationships.

100. What is the most important thing for AEs to remember?

Do not sell what we cannot support. ChainIT Pay should grow in a way that is scalable, compliant, profitable, and aligned with the customer’s real needs. A clean, well-qualified opportunity is more valuable than a rushed deal that creates risk later.

Quick Reference for AEsBest Opening Question

“How are you accepting payments today, and what part of that process creates the most friction?”

Best Pricing Response

“Pricing depends on your volume, average ticket, risk profile, transaction type, and required workflows. Once we understand your setup, we can recommend the right structure.”

Best Objection Response

“Most businesses already have something in place. The question is whether it is still the right fit.”

Best Rule

If you are unsure, do not guess. Confirm with the right internal team and follow up.

Sales Standard

Every opportunity should be properly documented in HubSpot, associated to the right Contact and Company, and only moved to a Deal when there is real engagement and commercial opportunity.