LogoLogo
BlogLogin
English
English
  • An Introduction to Saferpay
    • Licensing
      • Legacy licensing
    • Reconciliation
    • Acquirers & Payment Methods
    • Web Shop Plugins and certified partners
      • ePages Beyond
      • ePages NOW
      • Magento 2
      • Odoo
      • PrestaShop
        • PrestaShop User Guide
      • Salesforce Commerce Cloud
      • SAP Commerce Cloud
      • Shopware 6
        • Shopware 6 User Guide - German
        • Shopware 6 User Guide - English
      • WordPress WooCommerce
      • Shopify
    • Supported Languages
    • Common Saferpay terms - Glossary
  • News
    • Changes for transactions without customer presence
    • Changes for the Saferpay Hosted Forms, Fields and Payment Page
  • Quick Links
    • Web Shop Plugins and certified partners
    • Secure PayGate
    • User Administration
    • Payment Page Configuration
    • Risk Management
    • API Authentication
  • Interfaces
    • Payment API (aka JSON API)
    • Management API
    • Backoffice
      • The Home screen
      • Batch Processing
      • Transactions
        • Transaction Details
        • Batch Close
        • Declined transactions
        • Pending authorizations
        • Analytics
        • SEPA Refunds Export
        • Authorization & Payment
        • Credit
      • Risk Management
      • Secure PayGate / Payment Links
      • Secure Card Data
        • Secure Card Data Details
      • Settings
        • JSON API basic/Client Certificate authentication
        • User Administration
        • Payment Page Configuration
      • Online Support
      • User Profile
    • Saferpay OnSite
    • Feedback
  • Integration Guide
    • Integrating Saferpay
    • Ways of integration
      • General Information
        • Data Security and PCI DSS
        • Versioning
        • 3-D Secure
        • PSD2
        • Dynamic Currency Conversion
        • Iframe Integration and CSS
        • Fraud Intelligence
          • Silver
          • Fraud Intelligence Integration
      • Payment Page
        • Payment Page checklist
      • Transaction Interface
        • Recurring Payments
        • Refunds
          • SEPA Refunds
      • Capture and Daily Closing
        • Partial Captures
          • Marketplace
      • Secure Card Data - Tokenization
      • Saferpay Fields
      • Inquire Interfaces
      • Mobile Integration
      • Omni-Channel
      • Mail Phone Order
      • Error Handling
      • API Health Check
      • Saferpay API Specification
    • Payment Methods & Wallets
      • General and special cases
      • Account-to-Account Payments
      • Alipay+
      • Apple Pay
      • American Express
      • Bancontact
      • Billie
      • blik
      • Click to Pay
      • Diners Club International & Discover Card
      • eps
      • giropay
      • Google Pay
      • iDEAL 2.0
      • JCB
      • Klarna Payments
      • Maestro International
      • Mastercard
      • paydirekt
      • PayPal
      • PostFinance Pay
      • Przelewy24
      • Reka
      • SEPA Direct Debit
      • Sofort by Klarna
      • TWINT
      • UnionPay
      • Visa & V PAY
      • WeChat Pay
      • WL Crypto Payments
    • Testing
    • Go-Live
    • Frequently Asked Questions
    • Saferpay Demo
      • Saferpay Demo Environment
      • Saferpay Demo Shop
    • Support
    • Changelog
Powered by GitBook
On this page
  • Capture
  • Capturing a different amount and Multipart Captures
  • Cancel
  • Reservation times
  • Smart decision-making
  • Daily Closing
  • Triggering the Batch Close via API

Was this helpful?

  1. Integration Guide
  2. Ways of integration

Capture and Daily Closing

PreviousSEPA RefundsNextPartial Captures

Last updated 4 months ago

Was this helpful?

These two features are extremely important Saferpay features. Depending on the means of payment, the two can be directly associated with each other, and they must be carried out for the cash flow to be initiated to the merchant’s account. If no capture and batch has been executed, no money will be transferred.

This is why this dedicated chapter is so important. Here, we'll cover, what the capture is, how it is triggered and how you know, that it must be triggered.

Capture

The serves to book and thus to conclude/finalize a payment. As long as a transaction has not passed through the capture, the amount is merely reserved (“authorized”), but it will not be transferred to the merchant account. This is, why the capture is so important.

On the API side, you receive information about the transaction via the Transaction.Status parameter, e.g. through the , or . Transactions which have not yet been booked are visible in Saferpay Backoffice as "Reservation", Reservations are marked as "AUTHORIZED" on API-level and have to go through the , to be finalized:

"Transaction": {
  "Type": "PURCHASE",
  "Status": "AUTHORIZED",
  "Id": "MUOGAWA9pKr6rAv5dUKIbAjrCGYA",
  "Date": "2015-09-18T09:19:27.078Z",
  "Amount": {
    "Value": "100",
    "CurrencyCode": "CHF"
  },
  "AcquirerName": "AcquirerName",
  "AcquirerReference": "Reference"
}

If a transaction has already passed through, or does not need the capture, the status is changed to “CAPTURED”:

"Transaction": {
  "Type": "PURCHASE",
  "Status": "CAPTURED",
  "Id": "MUOGAWA9pKr6rAv5dUKIbAjrCGYA",
  "Date": "2015-09-18T09:19:27.078Z",
  "Amount": {
    "Value": "100",
    "CurrencyCode": "CHF"
  },
  "AcquirerName": "AcquirerName",
  "AcquirerReference": "Reference"
}
{
  "ResponseHeader": {
    "SpecVersion": "1.14",
    "RequestId": "93388d85dc4519ea37595121dd8bd4ae"
  },
  "Behavior": "ABORT",
  "ErrorName": "TRANSACTION_ALREADY_CAPTURED",
  "ErrorMessage": "Transaction already captured"
}

Note, that this error doesn't mean, that this transaction has failed. It simply means, that the capture has already been executed, so the transaction is already finalized and the money will be transferred to your bank account.

Payment methods, that do not need the capture, will return the status "CAPTURED" right away.

Capturing a different amount and Multipart Captures

Cancel

Reservation times

Smart decision-making

Just capturing every transaction, may not be the smartest thing to do for your business. Remember: A capture not only initiates the money-flow, it also is you -the merchant- accepting this transaction and everything, that comes with it.

There are multiple things, that should be considered, when making this decision, like:

  • Do I trust this customer?

  • Some countries even prohibit a capture, before the goods have been shipped to the customer. So the capture may only happen, if the goods are shipped to the payer.

These are just the most important things to consider, so please be smart about this and make the decision to capture wisely, to minimize fraud and legal troubles in certain countries.

Daily Closing

The daily closing follows the capture once daily, automatically at 22h CEST. During this process, all transactions that have passed through the capture are filed with the payment method processor in order. Depending on the payment processor, this is also the point, where all captured transactions are paid out onto the merchant's bank-account. Please contact your processor for the given payment method, if you need more information.

Triggering the Batch Close via API

A Batch Close must be carried out only once a day. It is possible to do it multiple times, but it is only recommended to do so, if really needed.

If you deactivate the batch close, but then do not trigger it via API, it will lead to some transactions not being paid out, so make sure, that either one, or the other is being done.

A may only be executed once! Should a second be attempted, the API will throw an error, informing you, that the already happened:

Not all payment methods need a separate capture to trigger the cash flow. The respectivechapter will give you the necessary information, if a is needed. However, dynamically reacting on the Transaction.Status parameter is the preferred method, as this enables you to also react to more payment methods, that will be added to your account, down the line, with no, or just minimal code-changes.

The can also be used to change the amount of the transaction. It is generally possible to capture less, than initially authorized. So applying things like voucher codes, or similar, is possible. Capturing more than initially authorized, however, may result in an error and is not recommended and sometimes downright blocked. This however depends on your processor/used payment method.

It is important to note, that a can only be performed once. The rest of the authorized amount will be released and can no longer be captured, if you capture less.

However, certain payment methods do support , which allow you to claim the money in multiple, smaller chunks. Please refer to the given , to see, if are supported.

A is the direct opposite of a capture. Instead of claiming the money, it releases the authorized amount. A should always be performed, if you no longer want to the money of a given transaction.

Note, that this does not apply, if you intend on using , as those do work in a different way, also in terms of releasing money! Please read the chapter there, on how to handle .

This is also important to understand, because the and the are in direct relationship to one another. Generally

If a is available, a can also be performed.

If a has been performed, a can no longer be issued. A has to be executed instead.

If a has been executed, you can no longer the transaction and thus claim the money.

Please refer to the given for more information, as there may be special cases.

A reservation, made through a certain payment processor, may only last for a limited time only. If this timeframe is exceeded, the authorized amount is released and becomes available to the account holder again. This may have the result that the amount can no longer be claimed. We recommend to an authorization as soon as possible. Either by direct API call, or manually via Saferpay Backoffice. If this is not possible, the nonetheless must be done as soon as possible.

The time-frame depends on the given payment method and your contract with your processor. Please ask there for further information. In case of Worldline (e.g. credit cards), please contact your account manager or .

Do I have Liability Shift through ?

It also serves as a "collecting" step, where all captured transactions are filed together, which then can be

If desired, this step can also be triggered via the Saferpay API. The request necessary for this is called .

However, before you can use the API, you need to disable the daily closing in the Saferpay Backoffice via "" for the respective terminal.

Capture
PaymentPage Assert
Transaction Authorize
Capture
Capture
Capture
Capture
Payment Method
Capture
Capture
Capture
Multipart Captures
payment method chapter
Multipart Captures
Cancel
Cancel
Capture
Partial Captures
Partial Captures
Capture
Cancel
Capture
Cancel
Capture
Cancel
Refund
Cancel
Capture
payment method chapter
Capture
Capture
3D Secure
viewed inside the Backoffice.
Batch Close
Settings -> Terminals
our sales department