Creatio to InterWeave Payment Gateway FAQs
1. What is InterWeave Payment Gateway (or Smart Payment Gateway)?
The InterWeave Payment Gateway (sometimes called InterWeave Smart Payment Gateway, ISPG) is a solution that integrates your CRM, website, or business system with one or more merchant service providers (MSPs) to process credit cards, ACH, electronic checks, recurring billing, and subscription payments. A
It handles:
- Real-time (immediate) credit card or eCheck authorizations
- Scheduled payments (deferred single payments)
- Recurring / subscription payments
- Routing of transactions to the merchant processor(s)
- Syncing of transaction results back into your CRM or accounting system
2. Which merchant service providers / gateways does it support?
InterWeave typically supports many major and specialized merchant service providers / payment gateways. Examples listed include: Authorize.Net, First Data, PayPal, iCash, Cybersource, Banktec, Vanco, PaymentXP, Chase Paymentech, and many more.
If you have a specific MSP in mind, you should confirm with your InterWeave implementation team whether that MSP is supported or can be custom-integrated.
3. How are pricing and licensing structured?
- The gateway (or Smart Payment Gateway) is typically licensed as part of or as an add-on to InterWeave’s Smart Solutions / integration platform.
- In the Creatio marketplace listing, the subscription was shown as $300/month, billed annually (i.e. $3,600/year) for the Creatio integration version.
- Taxes, discounts, MSP costs, and implementation costs may not be included in the base price.
- Often there is a “grandfathering” period if pricing changes.
You should ask your implementation team or vendor for full breakdowns (licensing, monthly vs. annual, included support, etc.).
4. How is security and compliance handled?
Because payment data is sensitive, a gateway like this must comply with PCI-DSS (Payment Card Industry Data Security Standard). The InterWeave product claims to use secure hosting and safeguards to protect data transmission.
Additionally, InterWeave does not store sensitive card data in your CRM or in plain form — instead, it acts as a conduit or connector to the payment processor, keeping sensitive data off your primary systems.
You should confirm which parts of your payment flow (tokenization, encryption, vaulting) are handled by InterWeave vs. by the payment processor.
5. What payment / billing modes are supported?
InterWeave supports multiple billing modes:
Mode | Description |
Real-time (Accept / Decline) | Immediate authorization of a transaction (card or eCheck) |
Scheduled / Deferred Payment | A payment is scheduled for a future date (for example, balance due) |
Recurring / Subscription Billing | Automated repeated billing on a schedule (e.g. monthly, annually) |
These modes may be used individually or in combination depending on your business need.
6. How does the payment flow / transaction routing work?
A typical flow:
- Customer submits payment data (credit card or eCheck) via your site, CRM, or portal.
- InterWeave routes the transaction to the chosen merchant service provider (MSP) via secure connection.
- The MSP (or acquiring bank) processes the transaction through card networks or banking rails.
- The result (approved/declined) is communicated back via the same chain to InterWeave, which then records it in your CRM or accounting system.
- Funds (for approved transactions) are settled into your merchant bank account via the processor/bank.
This end-to-end flow is designed to occur in a few seconds in most cases.
7. Can I integrate InterWeave Payment Gateway with my CRM or accounting software?
Yes — one of the core purposes of the solution is to tightly integrate payment and billing transactions into your CRM or financial software so you maintain a unified data flow.
Examples:
- The Creatio version integrates with Creatio as the front end and routes transactions behind the scenes.
- InterWeave’s Smart Payment Gateway helps connect CRM to merchant processors and sync results.
If your CRM or accounting system has an API or connector, InterWeave can likely be configured to integrate with it (via its hub/spoke or connector architecture).
8. What happens if a payment fails or is declined?
When a transaction fails or is declined, the response is routed back through the gateway and logged. Your system (CRM, accounting, or billing module) can be configured to notify the customer or to retry based on your rules (e.g. for recurrent payments).
You should define “failure handling” policies:
- Notification / alert to customer or internal users
- Retry logic (how many times, intervals)
- Handling expired cards, chargebacks, insufficient funds
- Logging and reconciliation
You’ll want to coordinate with your implementation team to set up those policies and workflows in your system.
9. What reporting, dashboards, or reconciliation tools are available?
InterWeave’s platform usually feeds transaction data into CRM or financial dashboards, enabling real-time visibility of payments, subscription metrics, accounts receivable status, etc.
You should ask about:
- Transaction-level reporting (approved, declined, refunds)
- Summary metrics (daily totals, settled vs unsettled, chargebacks)
- Reconciliation tools (matching payments to invoices)
- Export / integration (CSV, API) for your accounting systems
10. How do refunds, voids, and chargebacks work?
- Refunds: You should be able to issue a refund (full or partial) through the InterWeave front-end or via your CRM integration, which then routes the refund request to the MSP.
- Voids: If a transaction has not yet settled, you may be able to void (cancel) it.
- Chargebacks: If a customer disputes a charge, the chargeback is handled via your merchant account. The gateway should log the dispute and allow you to respond with evidence.
Implementation specifics (timing, restrictions, fees) depend on your MSP and contract.
11. Can I customize the payment workflow or logic?
Yes. One of the selling points of InterWeave is configurability. You can tailor flows, rules, field mappings, schedules, connectors, retry logic, etc.
During implementation, your team can define which modes to enable (real-time, recurring, scheduled), how failures should be handled, which fields map to which system, and so on.
12. What if I need a merchant provider that is not currently supported?
In many cases, you can request a custom integration. Because InterWeave is built to support many protocols and connectors, new MSPs can often be added via configuration or custom connector work. Confirm with your vendor whether the needed MSP is feasible for integration.