Skip to content
EasyPay logo

Payments

easypay integration

Connects the easypay API 2.0 to your system to create charges, handle notifications and keep subscriptions and direct debits in order.

Overview

EasyPay

easypay is a Portuguese payment institution whose API distinguishes single payments, frequent payments and subscriptions. It supports Multibanco, MB WAY, cards, direct debit and more, depending on the contract.

Tejobit handles easypay notifications the way the documentation advises: take the notice, read the payment ID and confirm the status through the API before touching any order. A spoofed or duplicated notification never marks anything as paid.

For recurring billing, such as monthly fees or retainers, the connection follows each subscription cycle and flags a failed debit before a customer falls months behind.

Use cases

What it is for

  • A gym or pilates studio collecting monthly fees by direct debit
  • A software company billing monthly retainers by card
  • A language school issuing Multibanco references per student and term
  • An online shop taking MB WAY and capturing the payment only when the order ships
  • A service provider that wants overdue payments visible inside its own CRM
IN

What the connection listens to

  • easypay generic notification on payment status changes
  • Authorisation notification for single and frequent payments
  • A paid Multibanco reference or a completed checkout
  • A new customer or a new billing period in the source system
OUT

What the connection does

  • Create single payments, frequent payments or subscriptions through the API
  • Check each payment's status in the API before trusting it
  • Capture authorised payments when the order ships
  • Update the CRM, shop or back-office with the charge status
  • Send the receipt details to the invoicing program

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • An easypay account with API 2.0 access, the account ID and API key
  • Notification URLs set in the backoffice (Web Services, API 2.0 configuration)
  • The rules for each charge: amounts, frequency and retries after a failure
  • Access to the system that holds customers and orders

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • Each notification type has its own URL, and all of them must be set
  • An MB WAY request only stays open for a few minutes
  • Direct debit depends on the customer's mandate and the bank's response, so it is not instant

Frequently asked questions

Before you start

What is the difference between frequent payments and subscriptions?

With frequent payments the business decides when to charge, under an authorisation already given. With subscriptions easypay charges on a fixed schedule. The connection supports both and uses whichever fits.

Can I test before going live?

Yes. easypay offers a test environment, and the connection is validated there with simulated payments before switching to production.

What happens when a direct debit bounces?

The easypay notification updates the status, the connection marks that period as unpaid and either alerts the team or sends the customer another way to pay.

Set up the EasyPay integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.