Payment card fail to authorize

hi all,
the sales order fail to rise authorization check when saving. i found the possible reason, the Next service/delivery (FPLAA-LEIWR) and next date (FPLAA-CMNGV) in payment card tab were not filled with any value. but i can saw values in the material availability date and order value fields.
when billing, the system doesn't create accounting document, and gives warning, the order need authorize again. when i reopen the order, i find the two fields all filled with values. and when i save it, the authorization raised normally.
who can help to tell me what's wrong indeed?
thanks a lot.
Daniel

Hi
See Note 914603 - FAQ/Collective note for payment cards (Consulting/modif). Be careful with legal requirements related with encryption of this data in sales documents and master data. (see 836079 FAQ: Credit card encryption and master data)
Regards
Eduardo
Edited by: E_Hinojosa on Feb 15, 2011 10:10 AM

Similar Messages

  • Payment Card Funcionality With authorization from financing Company NOT CC

    Hello Gurus,
    My Client is into distibution business and has Customers which pay their bills via financing companies.
    Currently they are using legacy But they authorize the amount for the total order once but if it is expired they look for new authorization. This is very close to payment card functionalty.
    I am looking for some info if i can avoid insufficent authorization errors for further processeing of sales orders??
    Or anyway i can spilt the authorization once it is recieved and not spltting it when i send it to financing company for approval.
    Regards,
    Niks

    Hi Renan,
    Let me explain the issue with an example:
    Example -
    1     01          21000491     XXX Technologies     435.00
    2     50          400000     Sales     400.00-
    3     50          220900     Use Tax     29.00-
    4     50          220900     Use Tax     4.00-
    5     50          220900     Use Tax     2.00-
    6     15          21000491     XXX Technologies     435.00-
    7     40          120010     Visa Receivable Clg     435.00
    Lines 1 to 5 are the ones that post normally without payment card. Line 6 and 7 are posting because the sales order has been authorized by a payment card. Although I am using the payment card functionality, I do not want to post lines 6 and 7 as the payment is going to come from the Financing company on due date.
    I hope this will help to understand the issue at hand.
    Thanks,
    FP

  • Payment Card processing- Manual Authorization

    Hi Experts,
    We are on CRM 4.0.
    Wanted to have an input on the Manual Authorization process for Payment card processing.
    Can someone guide as to how this can be achieved?
    thanks
    Yash

    df

  • To Remove Payment Card Authorization Block from Sales Order

    Hello All,
    I have a Scenerio of Payment Card Authorization where system receives authorization for Payment Cards and if authorization is Denied, Authorization Block Check is Set at Header of Sales Order in Payment Card Tab.
    Now if the Client Requirement is to Create a Z Program to Remove only the Check of Authorization Block in Open Orders.
    I have tried all the ways, unless we give Manual Authorization in payment Card Tab of Sales Order the Block cannot be removed.
    Can you provide a Way Out in Order to only Remove the Authorization Check without Manual Authorization in Sales Order.
    Looking Forward to your Views on the Same.
    Best Wishes,
    Onkar Khedekar

    Hi,
    MV45AFZH is the Standard User Exit that Runs when the order is Saved in Order Creation Mode.
    I wish to know a way out to remove Authorization Block in already Created Open Orders whose Payment Card Authorization is Denied.
    Regards,
    Onkar Khedekar

  • Custom screen for Payment card information in Sales Order

    Hi All,
    I want to know if its possible to develop a custom screen to accept multiple payment card information in Additional data tab and save it in normal payment card information at the time of saving sales order. This sounds little
    Nilesh

    Hi Nilesh,
    Please, see SAP Note 914603 - FAQ/Collective note for payment cards (Consulting/modif). Here you have the relevant notes related with this topic, so, in point 4, the note says:
    4. Payment cards in the order (with billing plan)
    - 914811 FAQ: Authorisation Problems - Why?
    - 915193 No authorization in the order
    - 313416 Installment plan payment with payment cards
    - 361790 No Authorization or only pre-authorization executed
    - 701569 Incorrect value to be authorized in the order
    I hope this helps you
    Regards
    Eduardo

  • SD payment card processing module

    Hi to every one ,
    what is SD payment card processing module.
    any have any idea plz give some idea. if u have any documentation plz send me.
    Murli.

    Hi Murli,
    I have pasted below the payment card configuration document.If it is not clear please send me your e-mail id i will send the document across to you.
                                   SAP Credit card configuration
    <u>Set Up Credit Control Areas:</u>
    Define Credit Control Area
    Transaction: OB45
    Tables: T014
    Action: Define a credit control area and its associated currency.  The Update Group should be ‘00012’.  This entry is required so the sales order will calculate the value to authorize
    Assign Company Code to Credit Control Area
    Transaction: OB38
    Tables: T001
    Action: Assign a default credit control area for each company code
    Define Permitted Credit Control Area for a Company Code
    Transaction:
    Tables: T001CM
    Action: For each company code enter every credit control area that can be used
    Identify Credit Price
    Transaction: V/08
    Tables: T683S
    Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax.  Make the following entries:
    Sub to:          “A”
    Reqt:          “2”
    AltCTy:          “4”
    Automatic Credit Checking
    Transaction: OVA8
    Tables: T691F
    Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed.  You need to mark the field “no Credit Check” with the valid number for sales documents.
    <u>Set Up Payment Guarantees</u>
    Define Forms of Payment Guarantee
    Transaction: OVFD
    Tables: T691K
    Action: R/3 is delivered with form “02” defined for payment cards.  Other than the descriptor, the only other entry should be “3” in the column labeled “PymtGuaCat”
    Define Payment Guarantee Procedure
    Transaction:
    Tables: T691M/T691O
    Action: Define a procedure and a description.  Forms of Payment Guarantee and make the following entries
    Sequential Number      “1”
    Payment Guarantee Form     “02”
    Routine Number           “0”    Routine Number can be used to validate payment card presence.
    Define Customer Payment Guarantee Flag
    Transaction:
    Tables: T691P
    Action: Define a flag to be stored in table.
    Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment Cards)”.
    Define Sales Document Payment Guarantee Flag
    Transaction:
    Tables: T691R
    Action: Define the flag that will be associated with sales document types that are relevant for payment cards
    Assign Sales Document Payment Guarantee Flag
    Transaction:
    Tables: TVAK
    Action: Assign the document flag type the sales documents types that are relevant for payment cards.
    Determine Payment Guarantee Procedure
    Transaction: OVFJ
    Tables: T691U
    Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
    <u>Payment Card Configuration</u>
    Define Card Types
    Transaction:
    Tables: TVCIN
    Action: Create the different card types plus the routine that validates the card for length and prefix (etc…)
    Visa , Mastercard, American Express, and Discover
    Create the following entries for each payment card
    AMEX          American Express     ZCCARD_CHECK_AMEX     Month
    DC          Discover Card          ZCCARD_CHECK_DC          Month*****
    MC          Mastercard          ZCCARD_CHECK_MC          Month
    VISA          Visa               ZCCARD_CHECK_VISA          Month
    The Routines can be created based on the original routines delivered by SAP. 
    *****SAP does not deliver a card check for Discover Card. We created our own routine.
    Define Card Categories
    Transaction:
    Tables: TVCTY
    Action: Define the card category to determine if a payment card is a credit card or a procurement card.
    Create the following two entries
    Cat     Description          One Card          Additional Data
    CC     Credit Cards          No-check          No-check
    PC     Procurement Cards     No-check          Check
    Determine Card Categories
    Transaction:
    Tables: TVCTD
    Action: For each card category map the account number range to a card category.  Multiple ranges are possible for each card category or a masking technique can be used.  Get the card number ranges from user community.  Below is just a sample of what I am aware are the different types of cards. 
    Visa Credit          Expires in 7 days.
                        400000       405500
                        405505       405549
                        405555       415927
                        415929       424603
                        424606       427532
                        427534       428799
                        428900       471699
                        471700       499999
         Visa Procurement          Expires in 7 days.
                        405501       405504
                        405550       405554
                        415928       415928
                        424604       424605
                        427533       427533
                        428800       428899
         Mastercard Credit     Expires in 30 days
                        500000       540499
                        540600       554999
                        557000       599999
         Mastercard Procurement     Expires in 30 days
                        540500       540599
                        555000       556999
         American Express Credit     Expires in 30 days
                        340000       349999
                        370000       379999
         Discover Card Credit     Expires in 30 days
                        601100       601199
    Set Sales Documents to accept Payment Card Information
    Transaction:
    Tables: TVAK
    Action: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each type which can accept a payment card
    Configuration for Authorization Request
    Maintain Authorization Requirements
    Transaction: OV9A
    Tables: TFRM
    Action: Define and activate the abap requirement that determines when an authorization is sent.  Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
    Define Checking Group
    Transaction:
    Tables: CCPGA
    Action: Define a checking group and enter the description.  Then follow the below guidelines for the remaining fields to be filled.
    AuthReq     Routine 901 is set here.
    PreAu          If checked R/3 will request an authorization for a .01 and the authorization will be
    flagged as such. (Insight does not use pre-authorization check).
    Ahorizon     This is the days in the future SAP will use to determine the value to authorize
                                 (Insight does not use auth horizon period).
    Valid          You will get warning message if the payment card is expiring within 30 days of order
                                 entry date.
    Assign Checking Group to Sales Document
    Transaction:      
    Tables: TVAK
    Action: Assign the checking group to the sales order types relevant for payment cards
    Define Authorization Validity Periods
    Transaction:
    Tables: TVCIN
    Action: For each card type enter the authorization validity period in days.
    AMEX     American Express     30
    DC     Discover card          30
    MC     Master card          30
    VISA     Visa               7
    Configuration for clearing houses
    Create new General Ledger Accounts
    Transaction: FS01
    Tables:
    Action: Two General Ledger accounts need to be created for each payment card type.  One for A/R reconciliation purposes and one for credit card clearing.
    Maintain Condition Types
    Transaction: OV85
    Tables: T685
    Action: Define a condition type for account determination and assign it to access sequence “A001”
    Define account determination procedure
    Transaction: OV86
    Tables: T683 / T683S
    Action: Define procedure name and select the procedure for control.  Enter the condition type defined in the previous step.
    Assign account determination procedure
    Transaction:
    Tables:
    Action: Determine which billing type we are using for payment card process.
    Authorization and Settlement Control
    Transaction:
    Tables: TCCAA
    Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
    Enter Merchant ID’s
    Transaction: 
    Tables: TCCM
    Action: Create the merchant id’s that the company uses to process payment cards
    Assign merchant id’s
    Transaction:
    Tables: TCCAA
    Action: Enter the merchant id’s with each clearinghouse account
    Reward if useful.
    Regards,
    Pramod.

  • PAYMENT CARD GREEN FLAG MISSING

    Its an order wherein payments is made through Payment cards:
    No green flag appearing beside order to release fraud block
    We are creating a debit note in order to charge a customer''s payment card. As the order is over our ''fraud'' limit we expect green flag to appear next to order we would then click the green flag to release  fraud block .....
    Please helpfull suggestion ...
    Thanks

    Hi Mohammed Arshad
    Set Up for Credit Card Payment Processing
    Given below is the set up for credit card payment processing:
    Set Up Credit Control Areas:
    Define Credit Control Area
    Transaction: OB45 
    Tables: T014
    Action: Define a credit control area and its associated currency.  The Update Group should be ‘00012’.  This entry is required so the sales order will calculate the value to authorize
    Assign Company Code to Credit Control Area
    Transaction: OB38
    Tables: T001
    Action: Assign a default credit control area for each company code
    Define Permitted Credit Control Area for a Company
    Code
    Transaction: 
    Tables: T001CM
    Action: For each company code enter every credit control area that can be used
    Identify Credit Price
    Transaction: V/08
    Tables: T683S
    Action: Towards the end of the pricing procedure, after all pricing and tax determination, create a subtotal line to store the value of the price plus any sales tax.  Make the following entries:
    Sub to:  “A”
    Reqt:  “2”
    AltCTy:  “4”
    Automatic Credit Checking
    Transaction: OVA8
    Tables: T691F
    Action: Select each combination of credit control areas, risk categories and document types for which credit checking should be bypassed.  You need to mark the field “no Credit Check” with the valid number for sales documents.
    Set Up Payment Guarantees
    <b>Define Forms of Payment Guarantee</b>
    Transaction: OVFD
    Tables: T691K
    Action: R/3 is delivered with form “02” defined for payment cards.  Other than the descriptor, the only other entry should be “3” in the column labeled “PymtGuaCat”
    <b>Define Payment Guarantee Procedure</b>
    Transaction: 
    Tables: T691M/T691O
    Action: Define a procedure and a description. 
    Forms of Payment Guarantee and make the following entries Sequential Number  “1” 
    Payment Guarantee Form “02”
    Routine Number   “0”    Routine Number can be used to validate payment card presence.
    <b>Define Customer Payment Guarantee Flag</b>
    Transaction: 
    Tables: T691P
    Action: Define a flag to be stored in table. 
    Create Customer Payment Guarantee = “Payment Card Payment Cards (All Customers can use Payment Cards)”.
    <b>Define Sales Document Payment Guarantee Flag</b>
    Transaction: 
    Tables: T691R
    Action: Define the flag that will be associated with sales document types that are relevant for payment cards
    <b>Assign Sales Document Payment Guarantee Flag</b>
    Transaction: 
    Tables: TVAK
    Action: Assign the document flag type the sales documents types that are relevant for payment cards.
    Determine Payment Guarantee Procedure
    Transaction: OVFJ
    Tables: T691U
    Action: Combine the Customer flag and the sales document flag to derive the payment guarantee procedure
    Payment Card Configuration
    Define Card Types
    Transaction: 
    Tables: TVCIN
    Action: Create the different card types plus the routine that validates the card for length and prefix (etc…) 
    Visa , Mastercard, American Express, and Discover 
    Create the following entries for each payment card 
    AMEX  American Express ZCCARD_CHECK_AMEX Month
    DC  Discover Card  ZCCARD_CHECK_DC  Month*****
    MC  Mastercard  ZCCARD_CHECK_MC  Month
    VISA  Visa   ZCCARD_CHECK_VISA  Month
    The Routines can be created based on the original routines delivered by SAP. 
    *****SAP does not deliver a card check for Discover Card. We created our own routine.
    Define Card Categories
    Transaction: 
    Tables: TVCTY
    Action: Define the card category to determine if a
    payment card is a credit card or a procurement card.
    Create the following two entries
    Cat Description  One Card  Additional Data
    CC Credit Cards  No-check  No-check
    PC Procurement Cards No-check  Check
    Determine Card Categories
    Transaction: 
    Tables: TVCTD
    Action: For each card category map the account number range to a card category.  Multiple ranges are possible for each card category or a masking technique can be used.  Get the card number ranges from user community.  Below is just a sample of what I am aware are the different types of cards. 
    Visa Credit  Expires in 7 days. 
        400000   405500
        405505   405549
        405555   415927
        415929   424603
        424606   427532
        427534   428799
        428900   471699
        471700   499999
    Visa Procurement  Expires in 7 days.
        405501   405504
        405550   405554
        415928   415928
        424604   424605
        427533   427533
        428800   428899
    Mastercard Credit Expires in 30 days
        500000   540499
        540600   554999
        557000   599999
    Mastercard Procurement Expires in 30 days
        540500   540599
        555000   556999
    American Express Credit Expires in 30 days
        340000   349999
        370000   379999
    Discover Card Credit Expires in 30 days
        601100   601199
    Set Sales Documents to accept Payment Card Information Transaction: 
    Tables: TVAK
    Action: Review the listing of Sales Document types and enter “03” in the column labeled “PT” for each type which can accept a payment card
    Configuration for Authorization Request
    Maintain Authorization Requirements
    Transaction: OV9A
    Tables: TFRM
    Action: Define and activate the abap requirement that determines when an authorization is sent.  Note that the following tables are available to be used in the abap requirement (VBAK, VBAP, VBKD, VBUK, and VBUP).
    Define Checking Group
    Transaction: 
    Tables: CCPGA
    Action: Define a checking group and enter the
    description.  Then follow the below guidelines for the remaining fields to be filled.
    AuthReq Routine 901 is set here.
    PreAu  If checked R/3 will request an authorization for a .01 and the authorization will be flagged as such. (Insight does not use pre-authorization check).
    A horizon This is the days in the future SAP will use to determine the value to authorize
    (Insight does not use auth horizon period).
    Valid  You will get warning message if the payment card is expiring within 30 days of order entry date. 
    Assign Checking Group to Sales Document
    Transaction: 
    Tables: TVAK
    Action: Assign the checking group to the sales order types relevant for payment cards
    Define Authorization Validity Periods
    Transaction: 
    Tables: TVCIN
    Action: For each card type enter the authorization validity period in days.
    AMEX American Express 30
    DC Discover card  30
    MC Master card  30
    VISA Visa   7
    Configuration for clearing houses
    Create new General Ledger Accounts
    Transaction: FS01
    Tables: 
    Action: Two General Ledger accounts need to be created for each payment card type.  One for A/R reconciliation purposes and one for credit card clearing.
    Maintain Condition Types
    Transaction: OV85
    Tables: T685
    Action: Define a condition type for account determination and assign it to access sequence “A001”
    Define account determination procedure
    Transaction: OV86
    Tables: T683 / T683S
    Action: Define procedure name and select the procedure for control.  Enter the condition type defined in the previous step.
    Assign account determination procedure
    Transaction: 
    Tables:
    Action: Determine which billing type we are using for payment card process.
    Authorization and Settlement Control
    Transaction: 
    Tables: TCCAA
    Action: Define the general ledger accounts for reconciliation and clearing and assign the function modules for authorization and settlement along with the proper RFC destinations for each.
    Enter Merchant ID’s
    Transaction: 
    Tables: TCCM
    Action: Create the merchant id’s that the company uses to process payment cards
    Assign merchant id’s
    Transaction: 
    Tables: TCCAA
    Action: Enter the merchant id’s with each clearinghouse account
    Reward if useful to u
    Message was edited by:
            narendran vajravelu

  • Payment cards : authorization not received on certain days

    Dear fellow SAP users,
    We use the payment cards feature but we do not need to connect to a clearing house because we know that the credit cards are actually valid.
    In order to by pass the connection to a clearing house, we copied the standard CCARD_AUTH_SIMULATION function and kept only the "approved" part.
    This works fine except for the sales created on certain days (namely Saturdays).
    For these orders, it looks as if no call is even made to the function module because the call status in the sales order is blank ("Not relevant").
    Could this be due to the factory calendar (Saturday is not a workday in the calendar we use) or something similar ?
    Your help is highly appreciated because I am getting crazy with this issue !
    VQ.

    Hello Vincent
    Check how you have set up any  Authorization  Horizon or Requirements.
    SPRO/IMG/Sales and Distribution/Billing/Payment Cards/Authorization and Settlement/Specify Authorization Validity Periods
    or
    SPRO/IMG/Sales and Distribution/Billing/Payment Cards/Authorization and Settlement/Maintain Authorization Requirements
    Hope this helps, let me know.

  • Payment cards authorization

    hai everybody
    can anybody tell me the functionality of the following fields in authorization config
    Initialization Authorization SET
    Result Authorization (SET)
    thank you

    hi colleague;
    I would like to kindly ask you to please check note 633462 (as well our FAQ note regarding Credit Card data       
    encryption, no. 766703).                                                                               
    Note 633462, from point 6 to 11, describes what you have to check and also how you can encrypt all the credit card numbers saved in the system using the CCARDEC_TRANSFORM_SD and the CCARDEC_TRANSFORM_FI       
    reports.                                                                               
    The reports within note 1046649 should also help you with the encryption process in tables VCNUM / VCKUN.                                                                               
    Depends of your support package, the following notes should also correct some details in the Payment Cards functionality. Please check if they are applied to your system:                                                                               
    - 1138689 -> Change documents for encrypted credit card in order         
    - 1140797 -> Encryption: Card not masked                                                                               
    Afterwards you can still run the report from note 1180185 in order to ensure that the Credit Cards are also masked in the Sales Documents  change log.                                                                               
    Please also check note 1029819 for further details about how to enable the encryption in your system.                                                                               
    Just to summarize:                                                                               
    Basically, to activate the encryption you have to follow the steps from note 766703. Please ensure this information is also taken into account:                                                                               
    "... the system displays the payment card number in unencrypted format if you have the authorization for activity 'C4' in the V_VBAK_AAT authorization object. If you do not have this authorization, the system  
    returns a masked number."                                                                               
    This note also asks you to first install and configure the SAPCryptoLib and then follow the steps from note 633462. You can also refer to note 510007 to find more information on how to correctly enable the  SAPCryptoLib in order to use it together with the Payment Cards functionality.                                                                               
    After everything is correctly customized, you can run the report  CCARDEC_CHECK to ensure that the encryption tool is working correctly.                                                                               
    Then, after that, you can run the report CCARDEC_TRANSFORM_VCKUN_VCNUM to encrypt the Credit Cards which are still not encrypted in the system. 
    I hooe it can explain the functionality.
    regards
    Ruy Castro

  • Payment Cards - Orders with Billing Plan - Authorization Logic

    Hello Experts,
    Generally, payment card authorization requests are triggered when an order is saved.  How does authorization work for orders with Billing Plans?  Thanks.
    Regards,
    Jess A.

    Hello Jess,
    If you have access to SAP notes please review note 313416. It should explain the system design with regard to payment cards and billing plans.
    I hope this helps.
    Best regards,
    Ian Kehoe.

  • Payment card authorization

    hai everybody
    while i m working sales orders with payment cards after saving sales order i m not getting the authorization responce
    can u pls send me the info regarding the authorization of payment cards
    thank you in advance
    sudheer

    Check following links for your query:
    - [Payment Card Authorisation|http://help.sap.com/printdocu/core/print46c/en/data/pdf/SDBILIVPC/SDBILIVPC.pdf]
    - Credit card payment
    - [Set Up for Credit Card Payment Processing|http://www.sap-img.com/sap-sd/set-up-for-credit-card-payment-processing.htm]
    Thanks & Regards
    JP

  • What is the field for checking authorization block in payment card

    Hi experts,
    I am using BAPI_SALESDOCU_CREATEFROMDATA to create debit memo requests.My requirement is to check the checkbox 'authorization block in VA02 ->header->payment cards.But i could not find that field in BAPI as well as in this table.I am picking credit card data from FPLTC table,
    There is one field called checkbox in BAPI.Is it the same field im in search,the what is the corresponding field in FPLTC table.
    Please advice,
    Thanks and regards,
    Meena

    Meena,
    As I recall the Authorization Block field (FPLA-AUST5) is set based on a response code field in field CC_REACT_T.  If you set this value to 'C' (which stands for "Unsuccessful: set authorization lock") then SAP will set FPLA-AUST5 to 'X' in FORM ZAHLUNGSKARTEN_AUTHORISIEREN in program MV45AF0Z_ZAHLUNGSKARTEN_AUTHOR in the following section of code:
    Stop-Flag setzten
          IF DA_XFPLT_AUTH_NEW-REACT = REACT_STOP.
            XFPLA-AUST5 = 'X'.
          ENDIF.
        ENDLOOP.
    Eric Bushman
    [Paymetric|http://www.paymetric.com]

  • "Amount you own" due to credit card failed authorization. Please help

    I was using a prepaid creditcard on my iTunes account but I didnt know it ran out, I downloaded Angry Bird Space HD from the app store after that and now I have a certain amount I own apple because it failed to authorize the prepaid credit card yet allowed me to install the app. I'm going to buy an iTunes gift card tonight, will that allow me to repay the amount due? Because I don't want to get banned or anything bad like that.
    Also if anyone else has had this happen to them before please tell me what you did. Thanks!

    Yes, just enter the new card details and click done when finished. It will then charge the new card for the amount owed.

  • TS3297 I Cannot update or purchase from itunes because of this error " We were unable to authorize your payment card for this purchase please update your billing info " this error is beacuse my brother tried to purchase some game worth 38$ which i dont ne

    I Cannot update or purchase from itunes because of this error " We were unable to authorize your payment card for this purchase please update your billing info " this error is beacuse my brother tried to purchase some game worth 38$ which i dont need it and i want to report a problem for this issue and able to get update my apps

    Welcome to the Apple Community.
    Apple's policy on sales of digital content is that all sales are final. If however you wish to appeal to Apple, select the content which is causing a problem and use the 'Report a problem' button in Your Purchase History.

  • We were unable to authorize your payment card for this purchase. Please update your billing info.

    we were unable to authorize your payment card for this purchase. Please update your billing info.
    I am currently on holiday and do not have access to my credit cards security code can i update it when i get back from holiday?

    Hello
    thank you for your reply
    However now i have another problem, it seems that my account has been charged by apple through a app purchase despite my credit card details not being complete
    i went to reportaproblem but the 'i would like to cancel this purchase' option is not here'

Maybe you are looking for

  • Upgradtion from oracle 8.1.5 to oracle 8.1.7 on win2k server

    hi, In order to upgrade my database from oracle 8.1.5 to 8.1.7 on same win2k server I performed the following steps but not sure what exactly happened, whether I have upgraded or not: 1. Installed 8.1.5 in e:\oracle\ora815 and test database on same d

  • Upon rebooting my left and right external monitor on my Snow Leopard Macbook Pro switch sides, right to left.

    I'm using two plugable UGA-2K-A ( http://plugable.com/products/UGA-2K-A/ ).  They work great for USB graphics, but how can I stop the configuration changes?

  • SSRS rendering error

    I am running SSRS reports from a PowerShell script. I have it working great on our development server. I had it deployed out test server and it is throwing this error. I can't figure out what would be different between the enviroments that would caus

  • I can´t pair my Brookstone headphones with my Ipad 3

    I can´t pair my Brookstone headphones with my Ipad 3, the Ipad simply doesn´t detect the device. I was using these headphones with my old Ipad 2. The device Manual of Instructions says it works with all Ipads. Any suggestions to solve the problem?

  • Content Viewer Issue

    Hi! I can't log in in the Content Viewer. Well, I can, but nothing happens when I do. There's no updates or anything. Anyone's having this issue or know how to address it? Thank you?