3D Secure is the cardholder authentication step on a payment link, payment page, invoice, recurring payment, or contract when Enable 3D Secure is on, or when the business is forced. It is not the same as an approved payment.
No. After authentication, open Transaction History. Only APPROVAL or Approved (AA) means the card payment succeeded.
Open Report, then Transaction History. Status APPROVAL, or a row found with Approved (AA), is a successful card payment. ND is a decline.
Confirm the business, then Transaction History, then Payment Attempts on the link, page, or checkout. Do not charge again while an APPROVAL may already exist.
Transaction History can show Declined (ND) or another non-approval code. Virtual Terminal can also say the service is not allowed. That row did not capture the sale.
Business name, channel, amount, currency, time and timezone, and the transaction id or link id. Never send the full card number, security code, password, or API key.
Only when the row is response code AA, the batch is still open, and Void is offered. After that, use Refund if the row offers it.
Transaction History, source API. API keys themselves are under Developers and are limited to a super admin.
Approval is the card result. Settlement is closing the wallet or the terminal batch. An approved sale can still be in an open wallet.
The dashboard does not show the bank deposit date. Check that the sale is APPROVAL and whether the wallet is OPEN or CLOSED. Then check the bank.
If the wallet is OPEN, it has not been closed. Settle is available only when your user can settle and manual closure is allowed. A decline is never settled.
No. There is no expedite control and no funding-date promise on the wallet screen.
An invoice filter of Pending, or a checkout session of Pending, means the payment is not complete. It is not an APPROVAL.
For a Castle terminal business, open Terminal, then Terminal Transaction History. Other businesses do not see that menu.
On a terminal payment, the approved amount is less than the amount requested. Check the amount before you complete the order.
No. 3D Secure does not remove chargebacks, and this dashboard does not include a chargeback case screen.
You do not. The inspected menus do not include a chargeback case file. Use Transaction History for the payment result.
Saved Payment Methods on a customer, or Saved cards in Virtual Terminal. The full card number is not shown.
Open the payment link, payment page, or checkout session, then Payment Attempts. Attempts are not a left-menu item. Blocked and Allowed are device decisions, not card approvals.
Fraud prevention stopped that try. It is not an approved payment. You cannot edit the fraud rules in the dashboard.
Open Settings, Notifications, and turn the row on. Then confirm the payment in Transaction History. The checkbox does not prove the email was delivered.
The row named payment link paid. Turning it on subscribes your user. The customer can still get their own message.
The company must be connected, the payment must be response code AA, and QuickBooks Desktop must not be the active connection. Read Logs. A decline is not synced.
On QuickBooks Online, the Connection tab shows Company, Realm ID, and Last sync. Sandbox is a test company. Production is live books.
You download a .qwc file and run Web Connector. Saving settings does nothing until that run. Payments sent this way are approved payment-link invoices that are mapped.
Settle closes the open wallet when you are allowed to do it. It does not fix a declined checkout and it does not show a bank date.
Sale, Pre-auth, and Return. Pre-auth is captured later with Force. Return is not the same button as Refund on an old sale.
Open Invoices, Create Invoice, save, then Send Invoice. Sending the email does not mark it paid.
You copy the link and the customer opens it. You do not see a separate social-network button. Expired links do not take payment.
Yes on a payment link. The payment type can be Single, Split, or Partial. The link can show paid and remaining amounts.
A super admin or an admin. The tabs are Configurations, Notifications, Business Logo, MFA, and terminal tabs when the business is a Castle terminal.
Open Settings, MFA, Enable 2FA, enter the phone number, and save. There is no control to skip MFA.
The header shows the DBA and email. Use Switch business if it is the wrong one. Records belong to that business only.
Employees and Permissions is shown to a super admin. Roles hold permissions. A terminal PIN must be 4 digits.
Submit a ticket and we’ll get back to you as soon as possible.