Authorizations

CLOWD9 will receive Authorization Information from the Network during the transaction process. For Off-Ledger and On-Ledger Customers, CLOWD9 will carry out Card and Cardholder verifications, for example:

• Card Status
• Expiry and CVV2 validation
• PIN validation
• Behaviour checks (limits, usage rules, Merchant Category Code, Country restrictions)
• ARQC validation

Where one or more of the validations CLOWD9 perform are unsuccessful, CLOWD9 will

• Provide the appropriate decline response to the Network, and
• Provide you with the Authorization Notification web hook

Authorization Request

Where you are managing the Cardholder balance (Off-Ledger) and authentication has been succesful, CLOWD9 will forward the Authorization Request to your configured Authorization endpoint to decide the outcome.

• Approved: CLOWD9 will require an approved response with the relevant approval response code populated
• Declined: Where the transaction outcome is not succesful, CLOWD9 will require a decline responsewith the response code and reason populated

CLOWD9 will provide the response to the Network which is then provided to the Merchant / Card Acceptor via their Acquirer.

• Mastercard Authorization Request Examples
• Visa Authorization Request Examples

Authorization Notification

Where CLOWD9 are managing the Cardholder balances (On-Ledger) and / or the card holder verification has not been succesful, CLOWD9 will forward the Authorization outcome your configured Authorization endpoint. You will not be required to provide a response as the outcome cannot be changed; instead you will be required to acknowledge the message.

• Mastercard Authorization Notification Examples
• Visa Authorization Notification Examples