Transactions

A transaction on ShopWired Payments occurs when a visitor pays, or attempts to pay you, for an order through your website or when you key in their card details yourself by creating an order through your ShopWired account.

Transactions can therefore either be successful or unsuccessful.

Transactions are linked to orders; it's not possible for a transaction to be created without a corresponding order. Whether the order is complete/successful or incomplete/unsuccessful is determined by the transaction status. When a transaction succeeds, the payment is received, and the order is marked as complete.

Viewing transactions

You can view transactions on your ShopWired Payments account by:

Navigating to ShopWired Payments > Payments & transactions
Viewing the corresponding order and selecting the transaction ID displayed (which will open the corresponding transaction information)

The payments & transactions page displays all the ShopWired Payments transactions on your account:

You can use the search box to search by customer surname, postcode, order reference, or transaction ID
You can use the From date and To date filters to filter by the date the transaction was created
You can use the filters to view all transactions, unsuccessful or successful (when the page loads, only successful transactions will be displayed)

Viewing a transaction

The full details of a transaction can be displayed by clicking on the specific transaction (either from the 'view order' page or the transactions page).

The transaction information page displays all of the information that ShopWired Payments holds about the transaction:

The risk evaluation displays ShopWired Payments' assessment of how likely the transaction is to be fraudulent:
Normal means the transaction has a normal/standard likelihood of being fraudulent
Elevated means that there is a higher likelihood that the transaction is fraudulent
Highest means that the transaction is likely to be fraudulent (ShopWired Payments automatically declines these transactions)

The payment details section displays additional information about the transaction:

The total value of the transaction
The processing fees charged by ShopWired Payments
The net amount (which is total - processing fees)
The corresponding order reference

The payment method section displays information about the payment method used by the customer:

Information about the card used (the last 4 digits and expiry date) are displayed as well as the Origin (which is the country that the card issuing bank has informed ShopWired Payments that the card is registered to)
The results of the CVC check and Postcode check are also displayed in this section
Read more details about the CVC check and postcode check

3D Secure (3DS) result

If the transaction was authenticated through the and the transaction was successful, the fact that the transaction was authenticated through 3DS will be displayed in the Payment method section under the heading 3DS check.

Marking a payment method as fraudulent

A payment method can be manually marked by you as 'fraudulent' if you suspect that the card has been used fraudulently.

To mark a payment method as fraudulent, select the mark this payment as fraudulent option. This will prevent the same card from being used on your website again.

Marking a payment method as fraudulent does not automatically refund the transaction, which you will need to do separately.

Capturing a transaction

Depending on your account settings, your account will either automatically capture funds from a cardholder's account to your ShopWired Payments account as soon as the transaction is placed, or alternatively, you'll have indicated that you want to manually capture funds at a separate time.

If your account is set to capture the funds later, you'll be able to capture funds in the capture funds section on the page by entering an amount and selecting the capture funds option.

You can only initiate one capture on a transaction; multiple captures are not permitted or available.

If you don't need to capture any funds and want to void the transaction completely, you should select the void transaction option. This process is irreversible.

You must capture funds within 7 days of the transaction being initiated by the customer. If you need a longer period of time to capture funds, we'd recommend using ShopWired's pre-order app.

Refunds

For ShopWired Payments transactions, refunds can only be created on the transaction page. Learn how to create refunds here.

Declined / unsuccessful transactions

If a transaction attempted by a visitor was declined, and therefore unsuccessful, you can view details about the reason for the decline on the transaction information page.

Navigate to the transaction within your ShopWired account (from the Payments & transactions page
Navigate to the Payment details section
You can view the decline reason under the status heading

Not all transactions will show the exact reason for a decline; this depends on whether the cardholder's bank returned a reason and what information was provided.

When an unsuccessful transaction shows a status of requires payment method, it means that a specific reason for the transaction being declined wasn't provided by the cardholder's bank. requires payment method is a generic decline code used when a specific decline reason is not available.

Decline code	Meaning
authentication_required	The transaction requires authentication (e.g. 3D Secure) that was not initiated or completed. Ask the customer to try again. If the decline persists despite successful authentication, they should contact their card issuer.
approve_with_id	The payment can’t be authorised. The customer should try again. If it still fails, they need to contact their card issuer.
call_issuer	The card was declined for an unknown reason. The customer must contact their card issuer.
card_not_supported	The card does not support this type of purchase. The customer must contact their issuer to confirm if the card can be used for this transaction type.
card_velocity_exceeded	The customer has exceeded the balance, credit limit, or transaction limit on their card. They must contact their card issuer.
currency_not_supported	The card doesn’t support the specified currency. The customer should confirm with their issuer whether their card can be used for that currency.
do_not_honor	The card was declined for an unknown reason. The customer must contact their card issuer.
do_not_try_again	The card was declined for an unknown reason. The customer must contact their card issuer.
duplicate_transaction	The issuer detected a recent identical transaction and declined what it believes may be a duplicate. The customer should check if they’ve already made the payment and contact their issuer.
error_blocklist	The card and customer email are blocked on your ShopWired Payments account due to a previous fraudulent or refunded transaction. Contact ShopWired Payments support to remove them from the blocklist.
expired_card	The card has expired. The customer must use another card.
fraudulent	The payment was declined because ShopWired Payments suspects fraud. This reason should not be shared with the customer; they should be told the payment was declined for an unknown reason and to contact their issuer.
generic_decline	The card was declined for an unknown reason. This can also appear when Radar blocks the payment. The customer must contact their card issuer.
incorrect_number	The card number is incorrect. The customer should try again with the correct number.
incorrect_cvc	The CVC number is incorrect. The customer should try again with the correct CVC.
incorrect_zip	The postal code doesn’t match the one held by the issuer. The customer should re-enter the correct billing postcode or contact their card issuer.
insufficient_funds	The card has insufficient funds. The customer should use another payment method.
invalid_account	The card or account is invalid. The customer should contact their card issuer to check the card’s status.
invalid_amount	The amount is invalid or exceeds the allowed limit. If correct, the customer should check with their issuer whether such purchases are permitted.
invalid_cvc	The CVC number is incorrect. The customer should try again with the correct CVC.
invalid_expiry_month	The expiry month is invalid. The customer should try again with the correct date.
invalid_expiry_year	The expiry year is invalid. The customer should try again with the correct date.
invalid_number	The card number is incorrect. The customer should try again with the correct number.
issuer_not_available	The issuer couldn’t be reached. The customer can try again or contact their card issuer.
lost_card	The card has been reported lost. This reason should not be shared with the customer; they should be told the payment was declined for an unknown reason and to contact their issuer.
merchant_blacklist	The payment matches a value on your ShopWired Payments blocklist. This reason should not be shared with the customer; they should be told the payment was declined for an unknown reason and to contact their issuer.
new_account_information_available	The card or connected account is invalid. The customer must contact their issuer for more information.
no_action_taken	The card was declined for an unknown reason. The customer must contact their issuer.
not_permitted	The payment isn’t permitted. The customer must contact their issuer.
pickup_card	The card cannot be used (possibly reported lost or stolen). The customer must contact their issuer.
processing_error	An error occurred during processing. The customer should try again. If it fails again, they should try later or use a different card.
reenter_transaction	The payment couldn’t be processed for an unknown reason. The customer should try again. If it still fails, they must contact their issuer.
restricted_card	The card cannot be used (possibly reported lost or stolen). This reason should not be shared with the customer; they should be told the payment was declined for an unknown reason and to contact their issuer.
revocation_of_all_authorizations	The card was declined for an unknown reason. The customer must contact their issuer.
revocation_of_authorization	The card was declined for an unknown reason. The customer must contact their issuer.
security_violation	The card was declined for an unknown reason. The customer must contact their issuer.
service_not_allowed	The card was declined for an unknown reason. The customer must contact their issuer.
stolen_card	The card has been reported stolen. This reason should not be shared with the customer; they should be told the payment was declined for an unknown reason and to contact their issuer.
stop_payment_order	The card was declined for an unknown reason. The customer must contact their issuer.
testmode_decline	A test card was used. Test cards can’t be used in live mode; a real card must be used.
transaction_not_allowed	The card was declined for an unknown reason. The customer must contact their issuer.
try_again_later	The card was declined for an unknown reason. Ask the customer to try again. If it continues, they must contact their issuer.
withdrawal_count_limit_exceeded	The customer has exceeded their available balance or limit. They must use another payment method.

Payment timeline

At the bottom of each transaction, a timeline is shown which displays 'key events' in a transaction's history. Timeline events are always marked with the time/date that the event occurred. The timeline includes the following types of events and information:

Transaction created
Transaction captured/voided
Refunds initiated
Early fraud warnings
Dispute events