Developer
  • Getting started keyboard_arrow_down

    Discover

    • arrow_forward
      EV Charging

      Discover our unattended POS solution for the ev market

    Our solutions

    • arrow_forward
      CCV Terminal

      Integrate with a CCV Terminal

    • arrow_forward
      SoftPOS

      Turn your own device into a payment terminal

    • arrow_forward
      CCV Online Payments

      Accepting online payments in your platform without technical knowledge

    • arrow_forward

    • arrow_forward

    Connect to the CCV Platform

    Integrate our products into your software. Let's make payment happen together!

    Look at all the possibilities
  • Documentation
  • API Reference
menu
    • expand_less Payment API
      • expand_more General
        • Communication
        • Environments
        • Authentication
        • Idempotency
        • Transaction Types
        • Webhooks
        • Notifications
        • Error Handling
        • Security & Privacy
        • Return URL
      • expand_less Online Payments
        • expand_more Quick Start
          • Initial Setup
          • Create Payment
        • expand_less Basic Operations
          • Create A Payment
          • Refund A Payment
          • Authorise & Capture Payments
          • Query The Payment Status
        • expand_more Payment Features
          • expand_more 3D-Secure 2
            • SCA And 3D-Secure 2
            • Compliance Guide
            • Out Of Scope Transactions
            • Exemptions
          • Payment Links
          • Merchant Initiated Payments
          • Embedded Card Payments
          • Mandates
          • Customers & Loyalty
          • Partial Payment
        • expand_more Payment Methods
          • American Express
          • Apple Pay
          • Google Pay
          • expand_more Bancontact
            • Bancontact Walled Initiated Payments (WIP)
            • Bancontact Deferred Sales
          • Bancontact Mobile
          • Banktransfer
          • IDEAL
          • Klarna
          • Landingpage
          • Maestro
          • Mastercard
          • Payconiq
          • Paypal
          • Visa
        • expand_more Payouts
          • Split Payout
          • Test Payout
        • expand_more Developer Resources
          • Currencies
          • Languages
          • Payment Testing
          • Test Cards
      • expand_more In-person Payments
        • expand_more SoftPOS
          • expand_more General
            • Getting Started
            • Device Requirements
            • SoftPOS TerminalIds
            • SoftPOS Errors
            • Currencies
            • Languages
            • Network And Connectivity
            • Release Notes
          • expand_more Basic Operations
            • Install A Terminal
            • Make A Payment
            • Handling Receipts
          • expand_more API Reference
            • SoftPOS - API Reference
    • expand_more Board Your Merchants At CCV
      • expand_more General
        • Getting Started
        • Authentication
      • expand_more Boarding API
        • StartOrder
        • AddSalesPackage
        • AddProductPSPStandalone
        • AddProductPSPSubmerchant
        • AddTerminalPackage
        • SetShoppingCartPricingDetails
        • SubmitOrder
        • Boarding
      • API Reference
    • expand_more Android Rest Beta API
      • expand_more General
        • Getting Started
        • Brands
        • Supported Languages
      • expand_more Basic Operations
        • Make A Payment
        • Cancel A Payment
        • Handling Receipts
        • Show Display Messages
        • Recover A Payment
      • expand_more Payment Features
        • Authorise & Capture
        • Capture
      • expand_more Terminal Features
        • Transaction Overview
        • Brands
        • Period Closing
        • Terminal - Status
      • expand_more Tokenization
        • Tokenization - Get A Card Token
        • Read A Mifare Card
        • Custom Text On Terminal
      • expand_more API Reference
        • API Reference
    • expand_more Android SDK
      • expand_more General
        • Getting Started
        • Demo Application - Android SDK
        • Result States
        • Language Codes
        • Error Handling
        • Logging
        • EP2
        • Download SDK
        • Release Notes
      • expand_more Basic Operations
        • Make A Payment
        • Stop Ongoing Payment
        • Recover A Payment - Android SDK
      • expand_more Payment Features
        • Account Selection - Android SDK
        • Additional Receipt Text - Android SDK
        • Allow Or Deny Card Brands - Android SDK
        • Authorisation By Voice - Android SDK
        • Authorise - Android SDK
        • Capture - Android SDK
        • Card Detection - Android SDK
        • Card Detection Deprecated - Android SDK
        • Card Token - Android SDK
        • Card Validation - Android SDK
        • Customer Display - Android SDK
        • E-Receipt - Android SDK
        • Manual Card Information Entry - Android SDK
        • Payment Reversal - Android SDK
        • Refund - Android SDK
        • Request Transaction Information - Android SDK
        • Reservation - Android SDK
        • German Eichrecht - Android SDK
      • expand_more SDK Guides
        • Activate Terminal - Android SDK
        • Card Circuits - Android SDK
        • Card Reader Status - Android SDK
        • Card Reader Status - Android SDK
        • Check Password - Android SDK
        • Factory Reset - Android SDK
        • Get Config - Android SDK
        • Get Status - Android SDK
        • Mobile Phone Prepaid - Android SDK
        • Online Agent - Android SDK
        • Partial Period Closing - Android SDK
        • Period Closing - Android SDK
        • Possible Transaction Types - Android SDK
        • Retrieve Last Ticket - Android SDK
        • Retrieve Open Pre Authorisations - Android SDK
        • Startup - Android SDK
        • Taxfree - Android SDK
        • Terminal Administration - Android SDK
        • Terminal Discovery - Android SDK
        • Ticket Reprint Period Closing - Android SDK
        • Transaction Overview - Android SDK
        • Check Password - Android SDK
      • expand_more Hardware Access
        • Getting Started
        • NFC - Android SDK
        • Printing - Android SDK
        • QR And Barcode Scanner - Android SDK
      • expand_more API Reference
        • API Documentation
    • Android App Requirements
    • expand_more Certification
      • Introduction
      • expand_more Attended Certification Tests
        • expand_more Aborting
          • F1A - Regular Abort By Merchant
          • F1B - Failing Abort By Merchant
          • F1D - Hammering Abort By Merchant
        • expand_more Allowed Amounts
          • S1A - Transaction With Amount Of EUR 0,00
          • S1B - Transaction With Negative Amount
          • S1C - Transaction With Highest Possible Amount
          • S1D - Over-Amount Transaction
        • expand_more Connection Lost
          • Q1B - Manual Transaction Recovery
          • Q1C - Ethernet Connection With ITS Fails
          • Q1F - Device Unavailable
          • Q1G - Terminal Not Responding
          • T1A - Automatic Transaction Recovery
        • expand_more E Journal
          • M1A - Store E-Journal
          • M2A - ECR/POS Print Journal Receipts
          • M3A - ECR/POS Storing Journal Receipts
        • expand_more Reprint Ticket
          • L1A - Reprint Ticket
          • L1B - Reprint Ticket Declined Transaction
          • L2A - Reprint Ticket No Printer Available
          • L2B - Reprint Ticket Declined Transaction No Printer Available
        • expand_more Tickets
          • U1A - Request For Identification
          • U1B - Request For Signature
          • U1C - Request For Signature And Identification
          • U1D - Failing Transaction No Receipt
          • U1E - Split Payment
        • expand_more Time Out
          • R1A - Time Out On Presenting A Card
          • R1B - Time Out During Pin Entry
        • expand_more Transactions
          • C1A - Happy Flow
          • C1B - Happy Flow Contactless
          • C1D - Happy Flow Magnetic Stripe
          • C1E - Declined Transaction By Host
          • C1E - Transaction Aborted By Cardholder
          • C1F - Absence Of Thousand Separator
          • C1G - Cashier Display Messages
        • expand_more Validation
          • H1A - Too Many Fingers
          • H1B - Not Removing Card
          • H2A - Power Loss Or Closing Of ECR/POS During Transaction
      • expand_more Unattended Certification Tests
        • expand_more User Guidance
          • C1 - Successful Payment
          • C2 - Next Cardholder
          • C3 - Abort On PIN Entry
          • C4 - Time Out During PIN Entry
          • C5 - No Amount Entered
          • C6 - Language Selection
          • C7 - Amount To Authorise
          • C8 - Available Funds
        • expand_more Device Selection
          • D1 - Device Selection
          • D2 - Invalid Device
          • D3 - Charger Selection Abort
          • D4 - No Charger Selected
          • D5 - Authorisation With No Free Devices
        • expand_more Product Delivery
          • E1 - Product Selection
          • E2 - Enabled Products
          • E3 - Invalid Product Entered
          • E4 - Product Selection Aborted
          • E5 - No Product Selected
          • E6 - Max Delivery Time
          • E7 - Abort Session
          • E7 - Abort By POS
          • E9 - Not Started Charging In Time
          • E10 - Take More Fuel Than AVF
          • E10 - Multiple Sessions Mixed
          • E12 - Postpone Card Financial Advice On New Cardholder Card
          • E13 - Abort Session On Card Reinsert
        • expand_more Receipts
          • F1 - Cardholder Retrieve Receipt Info
          • F2 - Cardholder Receipt Retrieval
          • F3 - Reprint Ticket
          • F4 - F8 - Ticket Printing And Content
          • F9 - TrackingToken Deleted
          • F10 - Printer Paper Low
          • F11 - CardPayment Erased From Storage
          • F12 - E-Receipt Received By Cardholder
          • F13 - E-Receipt Failure
        • expand_more Transaction Limit Handeling Maestro
          • G1 - Maestro CardPayment 1 Euro
          • G2 - Maestro CardPayment 30 Euro
          • G3 - Maestro CardPayment 60 Euro
          • G4 - Maestro CardPayment 500 Euro
        • expand_more Transaction Limit Handeling Mastercard
          • H1 - Mastercard CardPayment 1 Euro
          • H2 - Mastercard CardPayment 30 Euro
          • H3 - Mastercard CardPayment 60 Euro
          • H4 - Mastercard CardPayment 500 Euro
        • expand_more Mifare Handling
          • I1 - Happy Flow Mifare
          • I2 - Unknown Mifare Card
          • I3 - No Mifare Card Presented
          • I4 - Mastercard Presented
        • expand_more Card Circuits
          • L1 - Available Card Circuits
        • expand_more Reconciliation
          • M1 - Reconciliation As Function
          • M2 - Reconciliation By New Shiftnumber
          • M3 - POS Auto Triggers Reconciliation With Closure
        • expand_more Journal
          • N1 - Journal Accessible By Authorized Employees
          • N2 - Journal Cannot Be Altered
        • expand_more Exception Flows
          • O1 - Unknown Card Session
          • O2 - Maximum Time Out
          • O3 - Device Unavailable
          • O4 - Time Out Card-Type Fallback
          • O5 - Time Out On Presenting Card
          • O6 - App Stability
          • O7 - Automatic Startup
          • O8 - Sleep Mode Not Supported
          • O8 - Sleep Mode Supported
        • expand_more Recovery
          • X1 - Recovery After Communication Failure
          • X2 - Recovery After CCV Component Update
          • X3 - Recovery After 24 Hour Reboot
          • X4 - Recovery After CCV-Fusion Client Restart
          • Y1 - Recovery After Power Failure With No Battery Backup
          • Y2 - Recovery After Power Failure With Battery Backup
      • expand_more SoftPOS Certification Tests
        • expand_more Success Scenarios
          • Installation Success - SoftPOS Certification Test
          • Payment Success - SoftPOS Certification Test
        • expand_more Failed Scenarios
          • Installation Failed - CCV SoftPOS App Not Installed - SoftPOS Certification Test
          • Payment Failed - Declined - SoftPOS Certification Test
          • Payment Failed - CCV SoftPOS App Is Closed During Payment - SoftPOS Certification Test
          • Payment Failed -CCV SoftPOS App Is Killed During Payment - SoftPOS Certification Test
          • Payment Failed - SoftPOS App Not Installed Anymore - SoftPOS Certification Test
        • expand_more Other Scenarios
          • Other Scenario - Data Cleared Of The CCV SoftPOS App - SoftPOS Certification Test
    • expand_more Development Kits
      • SoftPOS Dev Kit
      • IM30 Dev Kit
    • Glossary

Payment API

  • General
    • Communication
    • Environments
    • Authentication
    • Idempotency
    • Transaction Types
    • Webhooks
    • Notifications
    • Error Handling
    • Security & Privacy
    • Return URL
  • Online Payments
    • Quick Start expand_more
      • Initial Setup
      • Create Payment
    • Basic Operations
      • Create A Payment
      • Refund A Payment
      • Authorise & Capture Payments
      • Query The Payment Status
    • Payment Features expand_more
      • 3D-Secure 2 expand_more
        • SCA And 3D-Secure 2
        • Compliance Guide
        • Out Of Scope Transactions
        • Exemptions
      • Payment Links
      • Merchant Initiated Payments
      • Embedded Card Payments
      • Mandates
      • Customers & Loyalty
      • Partial Payment
    • Payment Methods expand_more
      • American Express
      • Apple Pay
      • Google Pay
      • Bancontact expand_more
        • Bancontact Walled Initiated Payments (WIP)
        • Bancontact Deferred Sales
      • Bancontact Mobile
      • Banktransfer
      • IDEAL
      • Klarna
      • Landingpage
      • Maestro
      • Mastercard
      • Payconiq
      • Paypal
      • Visa
    • Payouts expand_more
      • Split Payout
      • Test Payout
    • Developer Resources expand_more
      • Currencies
      • Languages
      • Payment Testing
      • Test Cards
  • In-person Payments
    • SoftPOS expand_more
      • General expand_more
        • Getting Started
        • Device Requirements
        • SoftPOS TerminalIds
        • SoftPOS Errors
        • Currencies
        • Languages
        • Network And Connectivity
        • Release Notes
      • Basic Operations expand_more
        • Install A Terminal
        • Make A Payment
        • Handling Receipts
      • API Reference expand_more
        • SoftPOS - API Reference

What's on this page

  • Authorise and Capture
    • Available Methods
    • Knowledge Base
    • Typical Transaction Flow
      • Authorise
      • Capture or Reversal
    • Authorise the payment
    • Capture
    • Reversal
  • FAQ
    • Can I capture an authorisation multiple times?
    • Can I capture an authorisation partially?
    • Can I reverse an authorisation after I have captured it?
    • Can I reverse an authorisation multiple times?
    • How long is an authorisation valid?
    • Can I capture an authorisation after it has expired?
    • Can I reverse an authorisation after it has expired?
    • Can I capture an authorisation after I have reversed it?
Online Payments / Basic Operations / Authorise & Capture Payments

Authorise and Capture

An authorise allows a merchant to reserve money from the customer without withdrawing the money from the customers account. When you want to withdraw the money later on, you can send a capture request. If you decide to not withdraw the money, you can send a reversal request to release the reserved money on the customers account.

This can be useful in cases where

  • you want to authorise a payment, but only capture it once the order is ready to be shipped.
  • you want to authorise a fixed amount for fueling to reserve the funds, and capture the actual amount once the fueling is completed.
  • you want to authorise a fixed amount for EV charging to reserve the funds, and capture the actual amount once the charging is completed.
  • you want to authorise a fixed amount on hotel check-in, and capture the actual amount on check-out.

Available Methods

You can view the supported payment methods here.

Knowledge Base

  • An authorisation of a payment is the process of reserving the funds on the customer’s account.
  • An authorisation is valid for a certain period of time, after which it expires.
  • An authorisation can be captured at any time before it expires.
  • The expiration time is specific to the payment method and can be found in the Payment Methods documentation.
  • The funds on the customer’s account are reserved for the authorisation, and the customer cannot spend them, until you capture or reverse the authorisation or the authorisation expires.
  • The default amount for a capture is the full amount of the authorisation, but you can capture a different amount, as long as it does not exceed the authorised amount.

Typical Transaction Flow

Authorise

You want to reserve the funds on the customer’s account for a specific amount for your service you are about to deliver. Usually, the exact amount is not known at this point, so you authorise a fixed amount.

  1. You initiate a new authorisation request
  2. A transaction response is returned
  3. The customer is redirected to the payment page
  4. The customer enters their card details and completes the authentication
  5. PSP sends an authorization to the acquirer.
  6. A transaction result is sent to you (success or failure, through notification or webhook)
  7. You inform the customer of the transaction result

Capture or Reversal

After you have delivered or cancelled the service, you can either capture the authorisation or reverse it.

  1. You initiate a capture or reversal request. Optionally it includes an amount to capture or reverse.
  2. A transaction response is returned
  3. PSP sends the capture or reversal request to the acquirer.
  4. A transaction result is sent to you (success or failure, through notification or webhook) 5.You inform the customer of the transaction result

Authorise the payment

This requires the payment method to support authorisations. The following request will send an authorise request for 9.99 EUR,

  1. Initiate a new payment with type authorise

    Example request

    curl --basic --user apikey: -H "Content-Type: application/json" --data '{
      "transactionType": "authorise",
      "amount": 9.99,
      "currency": "eur",
      "method": "card",
      "returnUrl": "https://shop/return?order=123456",
      "webhookUrl": "https://shop/payhook?order=123456",
      "merchantOrderReference": "123456",
      "description": "Order 123456",
      "language": "eng"
    }' https://api.psp.ccv.eu/api/v1/payment
    

    Example response

    {
        "lastUpdate": 1709620979582,
        "cancelUrl": "https://onlinepayments.ccv.eu/card/cancel/merchant?reference=C240305064258677CB87E192.G",
        "created": 1709620979582,
        "payUrl": "https://onlinepayments.ccv.eu/card/payment.html?reference=C240305064258677CB87E192.G",
        "amount": 9.99,
        "description": "Order 123456",
        "status": "pending",
        "reference": "C240305064258677CB87E192.G",
        "merchantOrderReference": "123456",
        "method": "card",
        "type": "authorise",
        "language": "eng",
        "currency": "eur",
        "returnUrl": "https://shop/return?order=123456"
    }
    
  2. In order to complete the payment, you’ll need to redirect your customer to the payment url (payUrl) as returned in the payment response.

  3. Depending on the payment method, the customer performs an authentication. In case of card payments, we use 3-D Secure to verify the customer’s identity.

  4. As a final result, we return the customer back to your shop. The shop url is provided by you as returnUrl when you initiated the request in step 1.

  5. At this point you don’t know whether the payment is successful or not.

    • You must request the status of the payment in order to complete your order correctly. See also Read a transaction.
    • You must not assume that a return of the customer is due to successful payment!

    Example request

    curl --basic --user apikey: https://api.psp.ccv.eu/api/v1/transaction?reference=C240305064258677CB87E192.G
    

    Example response

    {
      "lastUpdate": 1709621105740,
      "statusFinalDate": 1709621105740,
      "cancelUrl": "https://onlinepayments.ccv.eu/card/cancel/merchant?reference=C240305064258677CB87E192.G",
      "created": 1709620979582,
      "methodTransactionId": "tMuzqg",
      "entryMode": "ecom",
      "brand": "visa",
      "details": {
        "cardholderFirstName": "John",
        "initialTransactionId": "p3GNcBD4tLFo800",
        "qrCode": "https://shop-vpos-test.ccvlab.eu/bep/authenticate.html?secureTransferId=1d584a8f-58fc-4704-a92d-9955e678b932&trm=50",
        "maskedPan": "4111XXXXXXXX1111",
        "acquirerResponseCode": "00",
        "urlIntent": "https://shop-vpos-test.ccvlab.eu/bep/authenticate.html?secureTransferId=1d584a8f-58fc-4704-a92d-9955e678b932&trm=51",
        "authorisedAmount": 9.99,
        "acquirer": "Valitor",
        "cardholderLastName": "Doe",
        "authenticationProtocol": "3DS2",
        "authenticationStatus": "Y",
        "acquirerResponseCodeDescription": "ApprovedOrCompletedSuccessfully"
      },
      "payUrl": "https://onlinepayments.ccv.eu/card/payment.html?reference=C240305064258677CB87E192.G",
      "amount": 9.99,
      "description": "Order 123456",
      "status": "success",
      "reference": "C240305064258677CB87E192.G",
      "merchantOrderReference": "123456",
      "method": "card",
      "type": "authorise",
      "language": "eng",
      "currency": "eur",
      "returnUrl": "https://shop/return?order=123456"
    }
    
  6. As a side effect of completing the payment (successfully or not), we will notify you using the webhook provided in step 1.

Capture

  1. When later in time you know the definitive amount to charge, perform a Capture request on the previous authorise transaction. The authorisation reference must be sent in the reference field.

    Example request

    curl --basic --user apikey: -H "Content-Type: application/json" --data '{
      "amount": 5.31,
      "webhookUrl": "https://shop/payhook?order=123456",
      "description": "Order 123456",
      "reference" : "C240305064258677CB87E192.G"
    }' https://api.psp.ccv.eu/api/v1/capture
    

    Example response

    {
      "lastUpdate": 1709621334602,
      "originalReference": "C240305064258677CB87E192.G",
      "created": 1709621334478,
      "brand": "visa",
      "amount": 5.31,
      "description": "Order 123456",
      "status": "pending",
      "reference": "C240305064854420CB87E193.G",
      "merchantOrderReference": "123456",
      "method": "card",
      "type": "capture",
      "language": "eng",
      "currency": "eur"
    }
    
  2. At this point you don’t know whether the payment is successful or not.

    • You must request the status of the payment in order to complete your order correctly. See also Read a transaction.
    • You must not assume that a return of the customer is due to successful payment!

    Example request

    curl --basic --user apikey: https://api.psp.ccv.eu/api/v1/transaction?reference=C240305064854420CB87E193.G
    

    Example response

    {
      "originalReference": "C240305064258677CB87E192.G",
      "lastUpdate": 1709621334942,
      "statusFinalDate": 1709621334942,
      "methodTransactionId": "tMuzqg",
      "entryMode": "ecom",
      "created": 1709621334478,
      "details": {
        "initialTransactionId": "p3GNcBD4tLFo800",
        "acquirerResponseCode": "00",
        "authorisedAmount": 9.99,
        "acquirer": "Valitor",
        "acquirerResponseCodeDescription": "ApprovedOrCompletedSuccessfully"
      },
      "status": "success",
      "description": "Order 123456",
      "brand": "visa",
      "amount": 5.31,
      "merchantOrderReference": "123456",
      "notificationRequests": [],
      "reference": "C240305064854420CB87E193.G",
      "returnUrl": "https://shop/return?order=123456",
      "method": "card",
      "type": "capture",
      "language": "eng",
      "currency": "eur"
    }
    
  3. After effect of completing a payment (successfully or not) we will notify you using a webhook. This allows you to perform additional operations in your system like sending an email to your customer.

Reversal

  1. When you want to cancel the authorisation and release the reserved funds on the customer’s account, perform a Reversal request on the previous authorise transaction. The authorisation reference must be sent in the reference field.

    Example request

    curl --basic --user apikey: -H "Content-Type: application/json" --data '{
      "webhookUrl": "https://shop/payhook?order=123456",
      "description": "Order 123456",
      "reference" : "C240305064258677CB87E192.G"
    }' https://api.psp.ccv.eu/api/v1/reversal
    

    Example response

    {
      "lastUpdate": 1709621334602,
      "originalReference": "C240305064258677CB87E192.G",
      "created": 1709621334478,
      "brand": "visa",
      "description": "Order 123456",
      "status": "pending",
      "reference": "C240305064854420CB87E193.G",
      "merchantOrderReference": "123456",
      "method": "card",
      "type": "reversal",
      "language": "eng",
      "currency": "eur"
    }
    
  2. At this point you don’t know whether the reversal is successful or not.

    • You must request the status of the reversal in order to complete your order correctly. See also Read a transaction.
    • You must not assume that a return of the customer is due to successful reversal!

    Example request

    curl --basic --user apikey: https://api.psp.ccv.eu/api/v1/transaction?reference=C240305064854420CB87E193.G
    

    Example response

    {
      "originalReference": "C240305064258677CB87E192.G",
      "lastUpdate": 1709621334942,
      "statusFinalDate": 1709621334942,
      "methodTransactionId": "tMuzqg",
      "entryMode": "ecom",
      "created": 1709621334478,
      "details": {
        "initialTransactionId": "p3GNcBD4tLFo800",
        "acquirerResponseCode": "00",
        "authorisedAmount": 9.99,
        "acquirer": "Valitor",
        "acquirerResponseCodeDescription": "ApprovedOrCompletedSuccessfully"
      },
      "status": "success",
      "description": "Order 123456",
      "brand": "visa",
      "amount": 5.31,
      "merchantOrderReference": "123456",
      "notificationRequests": [],
      "reference": "C240305064854420CB87E193.G",
      "returnUrl": "https://shop/return?order=123456",
      "method": "card",
      "type": "capture",
      "language": "eng",
      "currency": "eur"
    }
    
  3. After effect of completing a payment (successfully or not) we will notify you using a webhook. This allows you to perform additional operations in your system like sending an email to your customer.

FAQ

Can I capture an authorisation multiple times?

Yes, depending on the payment method, you can capture an authorisation multiple times, as long as the total amount captured does not exceed the authorised amount.

Can I capture an authorisation partially?

Yes, you can capture an authorisation partially, as long as the total amount captured does not exceed the authorised amount.

Can I reverse an authorisation after I have captured it?

No, you cannot reverse an authorisation after you have captured it. You should refund the specific capture instead. See the Refund API for more information.

Can I reverse an authorisation multiple times?

No, you can only reverse an authorisation once, the full authorisation will be reversed.

How long is an authorisation valid?

The validity of an authorisation is specific to the payment method and can be found in the Payment Methods documentation.

Can I capture an authorisation after it has expired?

No, you cannot capture an authorisation after it has expired. You will need to authorise the payment again.

Can I reverse an authorisation after it has expired?

No, you cannot reverse an authorisation after it has expired. The authorisation will already be reversed automatically.

Can I capture an authorisation after I have reversed it?

No, you cannot capture an authorisation after you have reversed it. You will need to authorise the payment again.

Go to

Home
Documentation




Cookies Privacy Statement