PCI-DSS 4.0 by design
Customers pay on the provider's secure page — card data never touches Vendor, keeping your PCI scope minimal.
All integrations
Payments
Connect Casys (CPay) to vendor
North Macedonian card gateway (CPay / Casys) with 3-D Secure and saved cards.
What you get
Everything the Casys (CPay) integration ships with
Built once, supported forever — no extra middleware to babysit.
Refunds from the dashboard
Issue full or partial refunds in a click; the status flows back onto the order automatically.
One unified pipeline
Casys (CPay) runs through the same idempotent payment flow as every other method, so reconciliation and reporting stay consistent.
How the Casys (CPay) integration works inside vendor
Casys (CPay) is the gateway most North Macedonian banks issue, so it's often the fastest route to accepting domestic cards in denar. Vendor speaks CPay natively — signed with HMAC-SHA256 — so you can go live with your bank's merchant credentials.
Enable CPay per store with your merchant number, name, and password. Vendor builds and verifies the signed request and callback, supports installment plans where your acquirer offers them, and can store card references (CRef) for returning customers.
What gets synced
CPay handles, per order:
- Signed (HMAC-SHA256) payment initiation and callback verification.
- Card authorizations and approvals in denar.
- Installment selection where your bank supports it.
- Saved card references (CRef) for repeat customers.
- Transaction references recorded on the order.
Setup
Add your CPay merchant number, name, and password (and payment URLs) under Payments in the admin.
Most North Macedonian banks (e.g. Uni Banka, Stopanska, Komercijalna) issue CPay credentials — use the ones from your acquirer.
Limits & considerations
Currencies, installments, and limits follow your bank's CPay contract.
3-D Secure behavior depends on the issuing bank.
Pairs well with
Stack the rest of your tools
Browse adjacent integrations your team will likely use alongside this one.
