FILTER BY TAG
Deprecating September 2026: HTTP Signature Messaging

Create a Shared Secret Key Pair

You must create a shared secret key pair to use HTTP signature message security. How you create your shared secret key pair is determined by your
National Australia Bank
account type.
Transacting merchant account users can create their own unique shared secret key. Portfolio and merchant account users must create a
meta key
of a shared secret key. Meta keys enable an organization administrator to create a single shared secret key. That key is assigned to some or all transacting merchants in their organization. The purpose of a meta key is to reduce the time needed to manage an organization's keys. For example, by assigning the same meta key to all of your transacting merchants, you need to update only one key when it expires instead of having to update each transacting merchant's key when it expires.
For more information about meta keys, see the Meta Key Creation and Management section in the
Creating and Using Security Keys User Guide
.

Figure:

Account Type Overview
Portfolio
A portfolio account represents the partner user. This account type can create and manage merchant accounts in the test and production environments. To create a shared secret meta-key as a portfolio user, see Portfolio User: Create a Meta Key.
Merchant
A merchant account represents the merchant user. This account type can create and manage multiple transacting merchant accounts within their organization. To create a shared secret meta-key as a merchant user, see Merchant Account User: Create a Meta Key.
Transacting Merchant
A transacting merchant represents the merchant user who is processing transactions. This account type is typically the account that sends API requests. To create a shared secret key pair as a transacting merchant, see Creating a Shared Secret Key Pair.