CoreviaFlowCOREVIAFLOWDIGITAL PROJECT COMPANY Leave a request
EN UA RU
Payments & POSUA

Portmone integration & automation

Card payments that reach the client's order the moment they clear — without card data ever touching your server

Portmone takes the card payment so your server never has to touch the card number itself — the card data gets locked with a public key right on the client's device before it goes anywhere. We connect the result to your order: a payment that clears updates the order's status and can set off the next step, like a confirmation to the client, on its own.

What we connect

  • A payment that clears updates the order's status in your system automatically — no manager has to check a separate payment page.
  • Card details are locked with a public key right on the client's own device before they go anywhere, so your server never handles the card number itself.
  • When a payment succeeds, the next step — a confirmation message to the client, moving the order forward — can happen on its own instead of waiting for someone to notice.
  • Test payments — both a successful one and a failed one — can be run with preset test card details before going live.
  • Switching the connection's test mode on or off goes through a written request to Portmone rather than a settings toggle, and we handle that step.
  • This direct connection variant is built for businesses that already meet the card-data security requirement PCI DSS; for a simpler setup, Portmone also offers a ready payment page or button, which we can connect instead.

Automation scenarios

01

A client pays for an order online

Before someone checks a separate payment system to see whether the money actually arrived.

After a cleared payment updates the order's status in your system on its own.

02

A payment succeeds

Before a manager remembers to send the client a confirmation.

After the confirmation goes out on its own the moment the payment clears.

03

The team needs to test the connection before going live

Before real card details get used just to check that the flow works.

After preset test card details cover both a successful and a failed payment, with no real money involved.

04

Test mode needs to be switched on or off

Before expecting a simple settings toggle, like on most services.

After knowing it takes a written request from the registered email to Portmone's managers — and having that request handled as part of the setup.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

  • Portmone's payment gateway connection is built on a transparent integration approach that uses client-side encryption (CSE).

    Source: docs.portmone.com.ua ↗ checked 2026-09-25
  • With this approach, card data is locked with a public key right on the client's own device before it reaches the merchant's server at all — the merchant's side has no way to unlock it, because it never holds the matching private key.

    Source: docs.portmone.com.ua ↗ checked 2026-09-25
  • Locking the card data on the client's device relies on a dedicated script with its own set-key and encrypt actions.

    Source: docs.portmone.com.ua ↗ checked 2026-09-25
  • Turning the connection's test mode on or off isn't self-service — it needs a written request sent from the registered email address to Portmone's managers.

    Source: docs.portmone.com.ua ↗ checked 2026-09-25
  • Portmone provides two ready-made test scenarios — a successful payment and a failed one — each with its own preset test card details.

    Source: docs.portmone.com.ua ↗ checked 2026-09-25

Limits

This direct connection variant is meant for businesses that already meet the PCI DSS card-data security requirement — turning its test mode on or off isn't self-service and takes a written request to Portmone's managers first.

Screenshots

Portmone payment gateway API documentation for partners
Payment gateway API Source: docs.portmone.com.ua ↗

How to start

Three steps from a first message to work on your project.

  1. 01

    Leave a request

    Describe the task in the form — in text or by voice. Budget and timing are optional.

  2. 02

    We review and estimate

    A developer studies the brief, asks about anything unclear and sends an estimate.

  3. 03

    We start

    Once scope and price are agreed, the work begins.

or write to info@coreviaflow.space

Questions

Does your server ever see the client's card number?
No — the card data is locked with a public key right on the client's device before it's sent anywhere, so the merchant's side has no way to read it.
Can we switch test mode on ourselves whenever we need to?
No — turning it on or off takes a written request from the registered email address to Portmone's managers; it isn't a self-service setting.
How do we test the connection before going live?
Portmone provides two ready test scenarios — a successful payment and a failed one — each with its own preset test card details, no real money involved.
Is this connection open to any online store?
This direct variant is built for businesses that already meet the PCI DSS card-data security requirement; Portmone also has simpler options, like a ready payment page, which fit stores that don't need this level of direct connection.

Tell us what needs to be connected

Describe the task in text or a voice message. We look at your setup and reply with a plan.