Payment Scenarios
Incremental Authorisation
the incremental authorisation feature allows you to increment the value of your original pre authorisation for scenarios where you need to charge your customer a higher total amount by incrementing the pre authorisation value, you will be able to capture the total amount that you wish to charge your customer when you are ready you can be assured the total amount that will be charged to the consumer can be captured at a later stage this is because the amount is ring fenced in the consumer’s account we will describe how an original pre authorisation can be updated to include additional amounts there may be additional considerations to take into account to ensure that incremental authorisation can work with apple pay™ we will update you with any requirements, once we know more for google pay™ , currently there are no additional considerations for incremental authorisation flows, however this may change over the course of 2025 and we will update you accordingly important to consider this feature is not available with all acquirers check with our customer service team, or your account manager for your eligibility to use this you can only increment a preauth that has been set up correctly setting up the incremental authorisation an incremental authorisation can only be used in the context of an existing pre authorisation the end to end flow contains the following steps step one initial pre authorisation the initial step is to process a preauth request when submitting the preauth request, to increment a preauth set the allowincrement flag to true in the request body this ensures the acquirer is expecting the amount of the initial preauth to be amended in the future you can set the allowincrement flag in the following ways using our sdks when invoking a preauth see our sdk integration sections for more details web sdk docid 40dwe6lbub7vdkza1qydc customisation docid\ j3hohxtgwg6 vhjo9wtzc customisation docid\ prt4f78qmrsju1ghjawgm react native docid\ ur8qjj7tjdxyhf4e5aojp directly via the judopay transaction api as part of the post /transactions/preauths request body web payments docid\ glorwwwfkfqp34fykcxe8 (hosted payments) as part of the post /webpayments/preauths request body step two incremental authorisation here, the amount of the initial preauth request can be incremented make a call to the judopay transaction api using the endpoint post /transactions/incrementalauth this request must contain the receiptid of the initial preauth from incremental authorisation docid\ me2r8ndav sjjkwep2rrb new total authorisation amount the authorisation amount is the sum of the original preauth amount + the amount(s) you wish to increment the incrementalauth step can be repeated multiple times if required each new increment must reference the receiptid of the original initial preauth each new increment must take into account the total amount authorised so far the initial preauth amount + sum of all increments for the purpose of this exercise, the following example is using the request body for the post /transactions/incrementalauth endpoint example request { "receiptid" "1001131610340495360", "amount" 5 99, "yourpaymentmetadata" { "internallocationref" "example", "internalid" 99 }, "yourpaymentreference" "aa648425 2230 4e4e 8a61 27f06df54542" } step three capture the full amount to capture the full amount to collect from your customer make a call to the judopay transaction api using the endpoint post /transactions/collections the amount specified in the request should include the total amount you wish to collect this can be less than, or equal to the total amount authorised