The first step to set up your account is to sign up for a sandbox account. From this account you can obtain your security keys and test your implementation.

To create a sandbox account, contact customer support: https://nabgateway-developer.nab.com.au/support/contact-us.html.

A P12 certificate and its private key are used with JSON Web Token message security. To create a P12 certificate, you must download a .p12 file from the

Gateway Portal

and extract its private key.

Follow these steps to construct messages using JWTs:

Message-Level Encryption (MLE) enables you to store information or communicate with other parties while helping to prevent uninvolved parties from understanding the stored information. MLE is optional and supported only for payments services.

MLE provides enhanced security for message payload by using an asymmetric encryption technique (public-key cryptography). The message encryption is implemented with symmetric encryption using Advanced Encryption Standard (AES), Galois Counter Mode (GCM) with 256-bit key size. The encryption of keys is supported using RSA Optimal Asymmetric Encryption Padding (OAEP) with 2048-bit key size. The encryption service is based on JSON Web Encryption (JWE), works on top of SSL and requires separate key-pairs for request and response legs of the transaction.

MLE is required for APIs that primarily deal with sensitive transaction data, both financial and non-financial. These are the types of sensitive transaction data:

MLE is supported when using JSON web tokens. For more information, see Message-Level Encryption Using JSON Web Tokens.

Each of these authentication schemes uses an encrypted payload, called the

JWE

. A JWE token has these five components, with each component separated by a period (.):

JOSE header containing four elements:
"alg": "RSA-OAEP-256", //The algorithm used to encrypt the CEK
"enc": "A256GCM",  //The algorithm used to encrypt the message
"iat": "1702493653" //The current timestamp in milliseconds
"kid": "keyId" //The serial number of shared public cert for encryption of CEK
JWE encrypted key
JWE initialization vector
JWE additional authentication data (AAD)
JWE ciphertext and authentication tag

When you are ready to process payments in a live environment, you must transition your account to a live status with a valid configuration for your chosen payment processor. When live, your transaction data flows through the production

National Australia Bank

gateway, to your processor, and on to the appropriate payment network.

To transition your account:

It may take up to three business days to complete a MID activation request.