[GNC] AqBanking help for Citi CC (continued)

[Dawid Wrobel]

There was a "[GNC] AqBanking help for Citi CC" thread last October about
getting the City CC working with AqBanking. It seemed that the key was to
add a trailing space to the User ID. Specifically, the following settings
were reported to function properly by Jim Maki:

AqBanking Setup
   ==>  User Settings
   ====>  User Name - "YOURUSERID"
   ====>  User Id - "YOURUSERID " (trailing space)
   ====>  Client UID - not specified
   ==>  Bank Settings
   ====>  Bank Name - "Citi Credit Card"
   ====>  Broker Id - "Citigroup"
   ====>  FID - "24909"
   ====>  ORG - "Citigroup"
   ====>  Server URL - "
https://www.accountonline.com/cards/svc/CitiOfxManager.do"
   ==>  Application Settings
   ====>  Application ID - "QWIN"
   ====>  Application Version - "2900"
   ====>  Header Version - "103"
   ====>  No Special Settings
   ==>  Account Info
   ====>  Account Number - "YOUR CC NUMBER"
   ====>  Account Name - "Citigroup"
   ====>  IBAN - not specified
   ====>  Owner Name - not specified
   ====>  Currency - "US Dollar (USD)"
   ====>  Account Type - "Credit Card Account"
   ==>  Bank Info
   ====>  Country - "United States of America (US)"
   ====>  Bank Code - "www.accountonline.com"
   ====>  Bank Name - "www.accountonline.com"
   ====>  SWIFT BIC - not specified
   ====>  Selected User - the user you defined above

Unfortunately, this doesn't work on my end using GnuCash 3.4 on macOS – I
am getting the 403 error.

The full output:

AqBanking v5.7.8.0stable
Sending jobs to the bank(s)
Locking user *username*
Saving communication log to /tmp/ofx.log
Sending request...
Connecting to server...
Resolving hostname "www.accountonline.com" ...
IP address is "173.223.170.86"
Connecting to "www.accountonline.com"
Connected to "www.accountonline.com"
Using GnuTLS default ciphers.
TLS: SSL-Ciphers negotiated: TLS1.2:ECDHE-RSA-AES-256-GCM:AEAD
Signer not found
Certificate is not trusted
Connected.
Sending message...
Message sent.
Waiting for response...
Receiving response...
HTTP-Status: 403 (Forbidden)
Error parsing server response
Unlocking user *username*
Postprocessing jobs
Job Get Transactions: finished
Resetting provider queues

For what it's worth, I have no special characters in my credentials. I also
turned off the 2-step verification I had enabled on my account.

Can anyone please confirm the OFX connection still works for them with
Citi? I will much appreciate that.

Thanks,
Dawid