Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Process a Batch Payment

Overview

Batch Payments gives the ability to process multiple card payments simultaneously by uploading a CSV file.

This guide will run through setting up the batch template, taking the payments and the reporting methods used.

You can find the guide to Batch Requests here.

You can process batches in different currencies; the chosen currency applies to the whole batch.

We have added multiple layers of checks and security to ensure that it is fast, secure and accurate. Due to these security checks, the card must have been used previously on Blink to generate the secure key needed (Blink Unique Reference (BUR)) - a verify transaction can be done on the virtual terminal to obtain this without charging the customer.

Navigation

You can find Batch Payments under the Payments tab on the left-hand navigation bar (Payments → Process a Batch Payment).

How does it work?

Within the Batch Payment section, you can upload new Batches and view your Batch History.

Batch Upload

Select your Merchant ID from the drop-down list.

You can download a template file using the 'Download .csv Template' button. A template will download consisting of five columns - Name, Email, Blink Unique Reference, New Amount and New Ref.

Select the currency you want to charge the batch in.

Multiple currencies

You can process batches in different currencies; the chosen currency applies to the whole batch.

Blink facilitates the possibility of accepting payments in multiple currencies. When you set up a merchant account with us, you are asked in which currencies you would like to process transactions. You can request additional currencies to be added with Support.

Filling in the template

The Blink Unique Reference (BUR) is a unique and secure token that Blink creates for every transaction used to enable abilities such as refund, re-run and Batch Payments.

Finding the Blink Unique Reference

You can find this customer's BUR using one of the below methods:

Export a report

We recommend using the export CSV function on Reports to export a report containing all the information (name, email, BUR) needed to populate the template.

On the exported report, the columns needed are Customer Email (Column D), Customer Name (Column E), & Blink Unique Reference (Column S).

Once this is added, you can add the new amount to be charged and the new reference for the transaction.

Report example


Transaction details

Manually from Transaction History

Another method is to obtain this information manually via the Transaction History page by clicking on the drop-down of a specific transaction.

This can then be copied into the template alongside the name and email.

Once this is added, you can add the new amount to be charged and the new reference for the transaction.

Using your own CRM/systems

If you have your own CRM or another system, you can export a report with the name, email, amount and reference (of course, this depends on what information you are storing). The BUR can be obtained by using either of the methods above.

Upload

Your template is now ready to upload - if you wish, you can save it with a relevant name (e.g. Jan '22 Batch).

Select 'Choose file' and choose your filled-out template on the Batch Payments page, then press 'upload file'.

Reviewing your upload

Once the file is uploaded, Blink will display a batch summary showing how many transactions are to be processed and the name, email, amount and reference.

It also shows you how/if any issues have been identified and highlight the relevant row.

If you hover over a highlighted row, it will show more information on the identified issue. You are still able to process the batch despite these warnings.

Please note you cannot use the details (BUR) of payment taken on a MID that does not belong to your Blink account.

Explanation of the Warning Messages

  • The original transaction has a different name/email associated with it: This means that the BUR entered does not match the name/email of the original transaction.

  • The original transaction was made on a different Merchant account: this means that the original transaction was made on a separate account owned by you. This is to warn you that if you have more than one merchant account, the original transaction was taken on a different one (e.g. a different branch).

Should you identify an issue that you wish to change or edit the batch details, you can make the change on the original uploaded file and then use the 'Choose file' and 'Re-Upload File' buttons re-upload the corrected file to be processed.

The re-upload process takes approximately one minute, and the page will refresh once it is complete.

Should you leave the page at any point after upload, you can return to the stage you left off by going to the Batch History page, finding the batch name (the name you gave to the file uploaded), and selecting 'Preview & Charge'.

You can also cancel the batch from here.

Charging the batch

Once the batch has been reviewed and ready to be processed, select 'Charge'. Once you confirm this, Blink will process the batch, and the status will be 'pending - queued'.

This process usually takes a couple of minutes, and Blink will refresh periodically and display an update.

You can leave the page and continue using the other Blink areas during this time. You can check the progress via the Batch History page, where the status will be 'pending - queued'.

Once complete, the status on Batch History will change to finished, and you will access the full status report.


Batch Status Report

Once the batch is complete, the status report will show a line by line of each transaction with a status.

At the bottom of the page, a quick summary shows an overview of the number of successful or declined transactions.

There is also an 'Export Report' button which allows you to download a detailed report. This report serves as a merchant receipt for Batch Payments and contains all the information (and more) that would appear on your regular Blink merchant receipt.

Batch Statuses

  • Captured - the transaction was successful.

  • Declined - the transaction did not go through.

  • Finished - the BUR used did not belong to any of your merchant accounts and was therefore not processed.

The customer will receive the regular receipt as usual.

  • No labels