Incremental authorisations for Payment Pages

  Last updated: 

 

An incremental authorisation is used to increase the total amount to be paid by the customer, if it is not known at time of authorisation. It is an additional request submitted using Portal, which can be used to seek authorisation for additional funds, once the full amount is known. The total amount to be paid by the customer is the value from the original AUTH, in addition to amounts associated with the incremental authorisations.

 

Requirements

  You can only process incremental authorisations with Visa-branded cards.

  Incremental authorisations are supported for merchants with a Trust Payments acquiring account and supported MCC codes

Your account must be assigned one of the following Merchant Category Codes (MCC) to be eligible to use incremental authorisations:

3351-3999, 4111, 4112, 4121, 4131, 4411, 5812, 5813, 7011, 7033, 7394, 7512, 7513, 7519, 7996, 7999

If you are using a different acquiring bank, you will need to contact our Support Team to check this feature is supported before proceeding.

  A previously-authorised payment is required

Incremental authorisations require a parent pre-authorisation that meets the following criteria:

  • Parent AUTH MUST have accounttypedescription= “ECOM” or “MOTO”.
  • Parent AUTH MUST have authmethod = “PRE”.
  • Parent AUTH MUST have settlestatus = 0 (pending automatic settlement) or 1 (pending manual settlement).

 

Processing incremental authorisations

To process an incremental authorisation, you will need to sign in to Portal and perform a “Re-auth” on the original transaction, with the Auth method set to “INCREMENTAL”, using the drop-down provided.

Incremental authorisations must adhere to the following additional requirements:

  • New incremental authorisations must be processed using the same card as the parent AUTH.
  • New incremental authorisations must be processed using the same currency as the parent AUTH.
  • New incremental authorisations must be processed using the same acquirer as the parent AUTH.
  • New incremental authorisations cannot be processed using a parent AUTH that has been settled or cancelled.

CO16-EN.png

  Alternatively, incremental authorisations can be processed by submitting additional AUTH requests using our Webservices API.

 

Updating the transaction

  All updates are to be performed on the original parent authorisation.
  • By performing successful incremental authorisations, the total amount authorised for the transaction is increased.
  • At any time prior to settlement while the transaction is still pending, you can update the settle amount to be any value that is less than or equal to the total amount authorised.

Updates can be performed using Portal or by submitting a request using our Webservices API.

 

Refunds

  Incremental authorisations having been processed on a given transaction does not affect the steps needed to perform a refund.
  • Ensure you are performing the refund using the original transaction as the parent rather than trying to action any of the individual incremental authorisations.
  • When performing a refund, the system will automatically refund the customer using the total amount settled, including any additional funds added via incremental authorisations prior to settlement.

Refunds can be performed using Portal or by submitting a request using our Webservices API.

Was this article helpful?
0 out of 0 found this helpful