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

Was this helpful?

  1. Interfaces
  2. Backoffice
  3. Transactions

Credit

PreviousAuthorization & PaymentNextRisk Management

Last updated 2 years ago

Was this helpful?

While is also possible, credit cards offer a manual way to do a refund, using the card-data directly, through the Credit option inside the Saferpay Backoffice.

This option shares a lot of similar inputs, to the normal , or , as it technically is a Payment, just in the opposite direction.

  • Card Number: This is the card number or PAN of the credit card, you want to authorize. This field is mandatory!

  • Expiry date: This is the expiration date of the card. This field is mandatory!

  • Owner Name: This is the name of the owner of the card.

  • Card Verification Code (CVC): Also called Card Verification Value (CVV), from the backside of the credit card.

  • Amount: This is the amount you want to authorize. It also includes the Currency. This field is mandatory!

  • Reference number: This is the reference number of the transaction, also called OrderId. While optional, we recommend, that you set one, as it is also forwarded to the processor and will show up on your reconciliation files.

Make sure, that the Reference Number is unique.

  • Sales Description: A simple description of this transaction.

  • Payer note on statement: This is the text, that will show up on your customers bank statement. Normally, Saferpay will use the Reference number. However sometimes, you may want to use a different text.

This feature has to be activated, before you can use it. Please contact your sales contact, for activation.

Furthermore: While Saferpay does support quite a long text, processors and banks, often do not support more, than 12 characters.

  • The purchaser's email address: If you want to, you can send a confirmation e-mail to your customer. The text is largely pre-made by Saferpay, however you can choose the language from the dropdown.

  • Your email address: Likewise, you can also send an e-mail to one of your e-mail addresses.

Authorization
Payment
(click to enlarge)
a credit from within an existing transaction