UnoSumoQ: Payment gateways in canada
Hi Yuumi,
I haven't chosen a payment gateway to use yet. The Canadian payment getways I'm interested in include:
*Moneris
*Nuvei
*Fiserv Clover (You should consider Clover. They recently announced a partnership with TD bank - huge in canada.)
1) I know it was mentioned that Moneris and Nuvei payment gateway are on your shortlist/roadmap for Canada, but from what I understand from what you said --- if the local processor provides standard APIs we can connect them to Unibee.
I imagine the ones integrated with Unibee are easier to activate, but are their any difference in PERFORMANCE/FEATURES between payment gateways integrated directly with unibee and payment gateways connected to unibee via api?
Yuumi
Dec 17, 2025A: Thank you for the insight on the Clover and TD Bank partnership! That is huge for the Canadian market, and I've passed this feedback directly to our product team to prioritize.
Regarding your question: "Are there differences between Native Integration vs. Connecting via API?"
The short answer is: Yes, the difference is significant, especially regarding setup and complexity.
Since Unibee is designed to be secure and PCI-compliant, we strictly do not store raw credit card information. We rely on "Tokenization" (exchanging card details for a secure token from the gateway).
Here is how that impacts your choice:
The "Tokenization" Hurdle (Frontend):
Native Integrations (e.g., Stripe, and future Moneris/Nuvei): We provide the ready-made checkout interfaces (Unibee.js or Hosted Pages). You simply plug it in, and we handle the secure exchange of card data for a Token automatically.
Custom API Connections: Because every gateway (like Clover) has a different way of collecting card data securely, we cannot provide a pre-built checkout form for non-native gateways. If you use a custom API connection, you would need to develop your own frontend to securely collect the card, get the token from Clover, and then pass that token to Unibee via API. This requires significant development effort.
Subscription Logic (Backend):
Native Integrations are mapped to handle complex recurring scenarios: Auto-refunds, specific decline reasons (e.g., "insufficient funds" vs. "stolen card"), and webhook updates all work out of the box.
Custom Connections usually only support basic charges. Features like handling disputes or automated subscription modifications often require building your own "middleware" code.
My Recommendation: For a smooth, no-code experience, I highly recommend waiting for the Native Integrations (Moneris/Nuvei) on our roadmap.
If Clover is essential for you right now, please vote for it on our roadmap! We prioritize integrations based on user demand, and the TD Bank context definitely adds weight to it.