NomuPay supports Non-Payment Authentication (NPA) which can be enabled via the npa_enabled gateway setting. When enabled, verify operations use a zero-amount authorization instead of the standard authorize-void flow.
NomuPay uses Bearer token authentication with an access token for secure communication. The access_token is used in the Authorization header for all API requests.
Your NomuPay entity identifier (merchant entity ID)
access_token (Required)
Your NomuPay access token is used for Bearer token authentication
npa_enabled (Optional)
Set to true to enable Non-Payment Authentication for verify operations (default: false). When enabled, verify uses a zero-amount authorization instead of authorize-void flow.
Merchant-provided reference number, should be unique for your transactions.
merchant_invoice_id
Merchant-provided invoice number, should be unique for your transactions, if not passed it will be mapped with order_id
merchant_customer_id
An identifier for this customer. Typically this is the ID that identifies the shopper in the shop's system.
merchant_memo
Merchant-provided additional information. The information provided is not transaction processing relevant. It will appear in reporting only.
promotion_code
Discount code applied at the Order level. There will be 1 Promotion Code per order.
transaction_category
The category of the transaction, possible values are :
EC - eCommerce MO - Mail order TO - Telephone order PO - pos PM - mpos MOTO - Mail order Telephone order
tax_amount
Indicates the tax amount of the payment request.
discount_amount
invoice level discount amount
locale
Sets the language/country. Examples : "de-AT", "en-US". etc
shipping_cost
The total amount of the shipping costs.
create_registration
If true, the payment details will be stored with the request. As part of the response, you will receive the parameter registration.id which you can use to reference the registration for later payments.
recurring_type
Indicates the type of a recurring MIT agreement. values - STANDING_ORDER | SUBSCRIPTION
industry_practice
The MIT types defined under this category are performed to fulfill a business practice as a follow-up to an original cardholder-merchant interaction that could not be completed with one single transaction.
Indicates the minimum number of days between authorizations.
number_of_installments
Indicates the maximum number of authorizations permitted for installment payments.
merchant_name
normally make up the first line of the card holder statement.
merchant_phone
Merchant contact number
merchant_url
test_mode
It is important to note that there are two test modes available to cause requests to be sent to Nomupay simulator or to the acquirers/APM/partner own test platform, as required:
testMode=EXTERNAL causes test transactions to be forwarded to the processor's test system for 'end-to-end' testing
testMode=INTERNAL causes transactions to be sent to our simulators
An internal unique identifier for the request in Nomupay.
build_number
for Nomupay support purposes.
result_code
Result code from NomuPay (e.g., '000.000.000' for success).See the result codes for more detailed information.
registration_id
Registration ID for stored payment methods
result_details
Additional result details from the gateway
parameter_errors
Parameter validation errors, if any
Stored Credentials
For NomuPay, sending stored credential fields can be done using Spreedly’s first class support. For any Authorize or Purchase request, you need to include two fields which tell Spreedly a little bit more about the nature of the transaction:
