Naateq
  1. Home
  2. Learning Centre
  3. Money
  4. Activating a payment gateway — with the fields as the gateway names them

Activating a payment gateway — with the fields as the gateway names them

Every gateway names its keys its own way. Where to find each of them, and the difference between a test key and a live key.

Money · 7 min read

The Payment gateways screen in the Naateq dashboard: Moyasar, Paylink and Tap, each with an activation switch and credential fields under their correct names.
The fields are written as the gateway names them in its own documentation — not as it would suit us to unify them. That is what makes copy-and-paste work the first time.

Open this screen in demo mode

Every Saudi payment gateway names its keys its own way, and asks for a different number of them. The gateways screen writes them as the gateway names them in its documentation not as it would suit us to unify them — so copy-and-paste works the first time.

This lesson tells you where to find each gateway's keys, the difference between a test key and a live key, and why the system never gets to set an amount.

Always start with test

Activate with the test key, issue a link, and open it yourself. Then switch to the live key — not the other way round.

Keys

Exactly what each gateway asks for

Credential fields per payment gateway
GatewayFieldsNote
MoyasarSecret keyUsed as the username, with an empty password
PaylinkapiId and secretKeyExchanged for a short-lived token before each request
TapSecret keySTC Pay runs through it as a payment method

The remaining Saudi gateways are shown on the screen with their correct mechanics so you know what awaits — and they get wired up when you ask for them.

Activation

Five steps from zero to a working link

  1. 1
    Open the gateway's dashboard and copy the test keys.

    They usually sit under «Developers» or «API keys». And note: some gateways show the secret key only once.

  2. 2
    Paste them into the gateway row and switch it on.

    The fields carry their original names, so you never have to guess which key goes where.

  3. 3
    Approve a test contract.

    Do not issue the link by hand — let it come out of its natural path, because that is what you are actually testing.

  4. 4
    Open the link on your phone.

    And check that the amount, the description and your business name appear the way you want your customer to see them.

  5. 5
    Switch to the live key.

    The system asks for an explicit acknowledgement before saving it — because what follows charges a real card.

The guard

The system has no tool that accepts an amount

This is the most important line in the lesson. There is no function in the system called «create a payment link for amount X» that the model can call. The amount is read from the payment schedule of the contract you approved, and the code composes the link message and sends it.

The reason is that a model able to set an amount is a model holding a card reader: one cleverly worded message from a customer would issue a one-riyal link against a twenty-thousand-riyal contract.

And a payment confirmation in a message is never believed.

A customer saying «I transferred it» is not evidence, and neither is a photo of a receipt. A payment is recorded when the gateway itself confirms it — and then the gateway is asked again before it is recorded. Verify, do not trust.

What happens after that is in tracking payments.

Frequently asked

What is the difference between a test key and a live key?

A test key produces payment links that work in form and move no riyal — that is what you test with. A live key actually charges the customer's card, which is why it asks for an explicit acknowledgement before it is saved.

Can the system decide the amount itself?

No, and there is no tool that would let it. The amount is read from the payment schedule of the contract you approved, and the code composes the link message. A model that can set an amount is a model holding a card reader.

Next lesson

All Learning Centre lessons