Menu
Talk with sales

Integration questions? [email protected]

A direct payment processor company built for EU, UK and Commonwealth merchants.

BazPay is the operating brand of NEWERA PAYMENT TECHNOLOGIES LTD, a direct regional payment processor company. Card and APM authorisation, tokenisation, hosted checkout, recurring billing, payouts, fraud controls and reporting are built and operated by the same entity — one contract, one MID, one platform.

Built for EU, UK and Commonwealth e-commerce sellers, subscription software firms and professional-services companies. No aggregated MID, no reseller in the chain, no downstream partner sitting behind an opaque relationship.

Talk with sales About the company

Why the processor company behind the platform matters

The company that operates a payment platform shapes every downstream decision — who underwrites your merchant application, who owns the roadmap, and who your on-call speaks to during an incident. Four properties matter more than a marketing brochure.

  • A named entity you contract with

    The counterparty on your merchant agreement is NEWERA PAYMENT TECHNOLOGIES LTD, operating BazPay. Not a reseller. Not an aggregator. Not a marketplace of third-party PSPs.

  • Direct regional acquiring, no middle layer

    The same company that runs the processor also holds the acquiring relationship. Authorisation and settlement live under one legal entity, so there is no downstream bank behind an opaque partnership.

  • One book, one underwriting policy

    The company boards a single regional book. Underwriting policy is published; approval decisions come from an in-house team, not from a bank that only sees a summary of your file.

  • Product ownership across the stack

    The processor company also owns the gateway API, the vault, the fraud engine and the dashboard. A change your team asks for lands on one roadmap, not four.

What kind of payment processor company BazPay is

Four cards below describe the corporate shape of the platform — the legal entity, the operating model, the merchant scope and the product ownership. Each shapes what boarding with the company will feel like in practice.

  • Legal

    Legal entity and operating brand

    The processor company is NEWERA PAYMENT TECHNOLOGIES LTD, a locally registered entity operating the BazPay platform. All merchant agreements, KYC evidence and settlement instructions reference the same legal counterparty.

    • NEWERA PAYMENT TECHNOLOGIES LTD
    • BazPay platform

  • Model

    Direct processor and acquirer

    BazPay authorises card traffic on its own regional acquiring licence. There is no third-party processor upstream and no reseller in the chain; the merchant contract sits with the company that runs the platform.

    • Named MID
    • Interchange++
    • Regional settlement

  • Scope

    Merchants across the EU, UK, Australia, Canada and New Zealand

    The company underwrites e-commerce sellers, subscription software firms, professional-services businesses and digital publishers based in-region. It does not board restricted verticals.

    • in-region
    • Defined book

  • Product

    One platform, end to end

    Acceptance, recurring billing, payouts, fraud controls, hosted checkout and reporting are built and operated by the same company — one API, one dashboard, one signed event stream.

    • Acceptance
    • Billing
    • Payouts
    • Fraud
    • Reporting

More on the operator on the about NEWERA PAYMENT TECHNOLOGIES LTD page. Buyer's shortlist of processor types on payment processors. The acquiring contract itself on merchant acquiring.

How a merchant engages with the payment processor company

Six stages describe the relationship from first enquiry to steady-state operations. Each stage has a named owner on the BazPay side, and each stage change is visible in the dashboard.

  1. Enquire

    You share business model, volumes and markets. The processor company confirms boarding fit before any paperwork is exchanged.

  2. Contract

    The merchant agreement names BazPay operated by NEWERA PAYMENT TECHNOLOGIES LTD as the counterparty. No downstream party is inserted.

  3. Provision

    KYC completes, a named MID opens with the schemes and sandbox plus live API credentials are issued for your engineers.

  4. Integrate

    One REST endpoint and hosted fields for the checkout. Existing plugins cover common regional commerce stacks so the effort is calibrated to the delta.

  5. Authorise

    Each charge posts against your MID with the authentication result bound to the transaction. Interchange++ line detail lands on every settlement.

  6. Settle

    Funds settle from the acquirer to your named local settlement account per scheme cycle, with a signed payout event per settlement for automated reconciliation.

Direct processor company vs reseller PSP or aggregator

Not every "payment processor" you see on a shortlist is the same kind of entity. The comparison below explains where the difference actually shows up in a merchant relationship — from contract to reporting to underwriting.

BazPay as a direct processor company compared with a reseller PSP or aggregator
Dimension BazPay (direct processor) Reseller PSP or aggregator
Legal counterparty NEWERA PAYMENT TECHNOLOGIES LTD (direct) Reseller PSP or aggregator
MID structure Named MID per merchant Shared or aggregated MID
Acquiring regional acquiring licence held in-house Downstream acquirer, hidden partner
Underwriting In-house team, published policy Passed through the reseller
Product ownership One roadmap across acceptance and billing Multiple vendors, independent roadmaps
Support surface Named integration manager Ticketing queue
Underwriting book Regional only, explicit scope Broad, few exclusions

Rate structure on the pricing page. Plugin coverage on integrations. Operational envelope on payment gateway services.

The product surface the processor company operates

Everything below ships on the standard integration. Turn features on with a request flag or a dashboard toggle — no premium tier that unlocks the primitives.

  • REST API

    One endpoint creates a charge across cards, wallets, local APMs and SEPA Instant — the response object shape does not change between rails.

  • Hosted fields

    Card, expiry and CVC inputs served from our PCI environment inside your checkout, keeping your annual return at merchant SAQ A.

  • Gateway vault + network tokens

    Store credentials once for card-on-file. Network tokens refresh through Visa and Mastercard token services when a card is reissued.

  • 3-D Secure 2.2

    Authentication with automatic exemption logic — TRA, low-value, trusted-beneficiary and MIT — so most checkouts stay frictionless.

  • Signed webhooks

    HMAC-signed, replay-protected events for every state change across every rail — one signature scheme end to end.

  • Interchange++ reporting

    Every settled transaction breaks out interchange, scheme fees and processor margin for line-level reconciliation.

  • Payouts

    SEPA and SEPA Instant merchant payouts to your named local settlement account. SWIFT and push-to-card available on approved corridors.

  • Recurring billing

    Card-on-file, dunning-aware retries and MIT exemptions on renewals — subscription billing native to the platform.

One API from the company that operates the platform

The gateway processor endpoints and the acquiring settlement stream belong to the same company, so there is no coordination between two vendors on your side. Charges, settlements, refunds and disputes all pass through one signing secret and one webhook envelope. 

POST /v1/charges
Idempotency-Key: 8f1c-2b3a-9e4d
{
  "amount": 4990,
  "currency": "EUR",
  "payment_method": "card",
  "capture": "auto",
  "three_d_secure": "required_if_needed",
  "descriptor": "ACME EU LTD",
  "metadata": { "order_id": "ORD-10842" }
}

The response returns the canonical charge object with the authorisation code, the MID it posted against, and any exemption applied. Read the complete schema in the API reference and handler samples in the developer docs.

Merchants the processor company underwrites

BazPay is a regional payment processor company. Underwriting is scoped to four merchant profiles with predictable chargeback ratios and clean AML posture.

  • E-commerce sellers

    DTC brands and multi-country storefronts on Shopware, Magento 2, WooCommerce or PrestaShop. One processor company across every regional storefront.

  • Subscription software

    SaaS teams billing monthly and annual plans with card-on-file renewals, dunning-aware retries and MIT exemptions.

  • Professional services

    Agencies, consultancies and B2B service firms invoicing recurring retainers with named-payer trust lists and enforced 3-D Secure 2.

  • Digital publishers

    Membership renewals, single-issue purchases and paywall unlocks reconciled per SKU on one MID.

Out of scope for BazPay: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay does not operate as a cryptocurrency processor and is not a marketplace of third-party PSPs.

Company credentials, security and change management

The processor company runs the platform inside a PCI DSS Level 1 environment assessed each year. Hosted fields and gateway-side vaulting keep your annual return at merchant SAQ A. API changes ship behind a version header with a documented deprecation window so an integration built against a stable contract stays stable.

PCI DSS Level 1
Annual assessment on the acquiring and gateway environment
Merchant SAQ A
Hosted fields and gateway vault keep card data out of your stack
Authentication
3-D Secure 2.2 with automatic exemption logic on every card charge
GDPR
In-region data residency; DPA on request
Scheme registrations
Visa VIRP and Mastercard SPoC/PCI-CP where required
Change management
Versioned API, published deprecation policy, audit-logged dashboard actions

Questions merchants ask about the processor company

Who is the payment processor company behind BazPay?

BazPay is operated by NEWERA PAYMENT TECHNOLOGIES LTD, a locally registered entity. The same company runs the gateway API, holds the acquiring relationship for the regional book and signs the merchant agreement — there is no reseller or aggregator between the merchant and the platform operator.

What is the difference between a payment gateway and a payment processor?

A payment gateway is the software layer that carries authorisation traffic between a merchant, the card networks and the issuers. A payment processor is the entity that operates that layer and settles the merchant. Some companies do only one; some do both. BazPay is both — the payment gateway and payment processor are operated as one platform by the same company, which is why merchants get a single contract and one MID rather than two.

Is BazPay a cryptocurrency payment processor?

No. BazPay is not a cryptocurrencies payment processor and does not board crypto-exchange merchants, crypto marketplaces or consumer wallet operators. The platform is scoped to card, device wallet, local payment method and instant rails for merchants across the EU, UK, Australia, Canada and New Zealand.

How is BazPay different from a merchant processor reseller?

A merchant processor reseller places its brand on top of a downstream acquirer, and the merchant sits on a shared MID. BazPay holds the acquiring relationship directly, issues a named MID and signs the merchant agreement as the counterparty. That means chargeback attribution, settlement reporting and underwriting decisions are attributed to your entity, not diluted across a pool.

What do I do if the payment processor is down?

Rail-level health per network is published on the BazPay status page, and signed platform.maintenance and platform.incident webhooks fire into your webhook stream so your on-call sees them next to your existing alerts. Support and escalation paths are documented on day one; a named integration manager owns the operational relationship for boarded merchants.

Do you publish payment processor market share statistics?

No, and any figure you see about market share is worth checking. BazPay does not publish approval-rate percentages, customer counts or market-share numbers in marketing copy because none of those are stable, comparable metrics across processors. Underwriting fit, rate structure and product scope are the numbers that matter, and those are published on the pricing page and confirmed during boarding.

How would a merchant become a payment processor themselves?

Becoming a full payment processor requires an acquiring bank relationship (or a licence) with the card networks, membership with each scheme, ongoing PCI DSS Level 1 assessment and the operational surface to settle funds. It is a multi-year regulated build. The reason most merchants pick a processor company rather than becoming one is that the entry cost — capital, licensing, engineering, compliance — dwarfs the cost of a well-scoped processor contract.

Which merchants can this processor company board?

Merchants across the EU, UK, Australia, Canada and New Zealand: e-commerce sellers, subscription software firms, professional-services businesses and digital publishers. Out of scope: adult, gambling, CBD, nutraceutical, forex, CFD, crypto-exchange, debt-collection and MLM. BazPay is not a merchant of record and does not act as a marketplace of third-party PSPs.

Talk to the payment processor company directly

Share your business model and volumes and NEWERA PAYMENT TECHNOLOGIES LTD will confirm boarding fit and likely rate structure within one working day. See also payments solutions, payment gateway services, payment infrastructure and the wider network payment gateway.

Talk with sales Company profile