Authorization Request

CLOWD9 will transmit an authorization request to your configured endpoint, for your decision, which is provided in the Authorization response.

In the event your response is not received in time, CLOWD9 will return a 100 - Do Not Honour response to the network / scheme.


Authorization Request

FieldValue FormatMandatory
message_type“authorization”stringYes
message_qualifier“request”stringYes
sourceIdentifies the source of the message, such as the network:
visa
mastercard
clowd9
stringYes
card Contains vital information about the card as held in the CLOWD9 database
> > card_idThe Identifier of the card associated to the authorization requestuuidYes
> > card_form_factorForm factor of card. Supported values:

“physical”
“virtual”
stringYes
> > card_statusShows the current status of the card that is sent during the authorization process or following a successful status change.

Supported values for use:

"inactive"
“active”
"administrative"
“destroyed”
"fraud"
"freeze"
"lost"
“stolen”

Status values for CLOWD9 use only:
"expired"
"risk"
stringYes
customerContains vital information about the customer as held in the CLOWD9 database
> > customer_idThe Identifier of the Customer associated with the carduuidYes
> > customer_external_refExternal ID of the customer associated with the card, if heldstringNo
transaction Details of the transaction
> > auth_typeUsed to identify the type of an authorization message:
"preauth",
"incremental",
"completion",
"recurring_initial"
"recurring_subsequent", or
"anticipated_amount_verification"
stringNo
> > credential_on_fileIndicates if the transaction was a credential on file transaction, either:
“y”
"n"
stringYes
> > transaction_typeUsed to identify the type of service usedstringYes
> > transaction_idThe unique identifier of the transaction log entry in the CLOWD9 databaseuuidYes
> > system_trace_audit_numberThe System Trace Audit Number for the network message if present/applicablestringYes
> > retrieval_reference_numberThe Retrieval Reference Number for the network message if present/applicablestringYes
> > network_transaction_idThe unique identifier of the transaction assigned by the networkstringYes
> > transmission_dateThe date the message was received, as indicated in the message from the networkstring (MMDD)Yes
> > transmission_timeThe time the message was received, as indicated in the message from the networkstring (hhmmss)Yes
> > transaction_local_dateThe local date at the point of transaction originationstring (MMDD)No
> > transaction_local_timeThe local time at the point of transaction originationstring (hhmmss)No
> > transaction_amountThe amount to be authorized with the transaction. Can be “0” for non-financial messages.
Note: we only accept integers format
stringYes
> > transaction_currency_codeThe ISO currency code in which transaction_amount is represented. Note that this may have implications on the decimal placestring (3)Yes
> > cardholder_billing_amountThe amount to be billed against the cardholder’s account, if the transaction currency is different to card settlement currency.
Note: Integer format is required
stringYes
> > cardholder_billing_currency_codeThe ISO currency code in which cardholder_billing_amount is represented. Note that this may have implications on the decimal placestring (3)Yes
> > cardholder_billing_conversion_rateThe conversion rate used to calculate cardholder_billing_amount from transaction_amountstringYes
> > transaction_fee_amountThe amount of the transaction fee. Note that this is already accounted for in transaction_amountstringNo
> > transaction_fee_programName of the fee configuration that was used to calculate transaction_fee_amountstringNo
> > from_accountThe source account type of the transaction request:
“default”,
“savings”,
“checking”, or
“credit”
stringYes
> > to_accountThe destination account type of the transaction request:
“default”,
“savings”,
“checking”, or
“credit”
stringYes
> > eciE-Commerce authentication indicator. For an e-commerce transaction, when available, identifies the various security measures applied before transaction submission. Possible values:

"0" - Not applicable to the transaction
"1" - Single transaction of mail/phone order
"2" - Recurring transaction
"3" - Instalment payment
"4" - Mail/Telephone order type unknown
“5” - Fully authenticated
“6” - Authentication attempted but unsuccessful
"7" - Authentication not attempted
"8" - Non-secure transaction
stringYes
> > dcc_indicatorIndicates whether Dynamic Currency Conversion took place, either
“y”, or
“n”
stringYes
> > chip_indicatorIndicates if the Integrated Chip Card was used:
“n”,
“contact”, or
“contactless”
stringYes
> > pin_indicatorIndicates whether the PIN for the transaction was checked, its nature and the result:
“n”,
“offline_passed”,
“offline_failed”,
“online_passed”, or
“online_failed”
stringYes
> > 3ds_indicatorIndicates whether 3D-Secure Authentication took place for this transaction, either
“y”, or
“n”
stringYes
> > avs_outcomeProvides the outcome of the Address Verification Service performed by CLOWD9:
"m" Both match
"a" Address match only
"p" Post code match only
"n" Neither match
"r" Error while processing
stringYes
> > partial_approval_supportedIndicates whether Partial Approval is supported, either
“y”
“n”
stringYes
> > cardholder_conditionCardholder condition indicator provided during the authorization. Possible values are:

“00” card holder present, normal transaction
“01” card holder not present
“02” card holder present
“03” card present, suspicious activity
“05” card holder present
“08” card holder not present, mail or telephone order
“59” card holder not present, electronic order (ecommerce)
“71” card holder present (Used in US only)
stringYes
> > > > authorization_codeA six digit code generated by CLOWD9, associated with the authorization requeststringYes
>>status
> > > > response_codeResponse code numeric value used by CLOWD9 and you for the final outcome of the request.stringYes
> > > > response_sourceIndicates the source of the response_code value. Possible values:

“scheme”
“clowd9”
stringYes
> > > > response_reasonThe alpha description associated to the response_code. stringYes
acquirer Information about the Merchant and their Acquiring Institution at point of transaction capture
> > acquiring_institution_id_codeThe identification code of the Merchants Acquiring InstitutionstringYes
> > acquiring_institution_country_codeThe ISO country code of the Merchants Acquiring InstitutionstringYes
> > merchant_category_codeThe Merchant Category Code, numeric (4) stringYes
> > card_acceptor_terminal_idThe identifier of the Merchant terminalstringYes
> > card_acceptor_idThe identifier of the MerchantstringYes
> > card_acceptor_nameThe name of the Merchant stringYes
> > card_acceptor_cityThe city where the Merchant is registered stringYes
> > card_acceptor_country_codeThe country the Merchant is registered in alpha (3) stringYes
> > card_acceptor_post_codeThe Post code of the card acceptor entitystringYes