Differenciate between the New and Legacy Repeat payments schedules

Viewing schedules 

The main table on the “Manage repeat payments” page lists all your created repeat payment schedules. 

It also displays data such as the date and time of its creation, the customer's name, email, card, reference, frequency, next payment date and total amounts of the processed payments.  

Possible schedule statuses are as follows: 

• Pending – This schedule has not yet started 

• Active – This schedule has processed the first payment, and is currently running 

• Completed – This schedule has finished processing all its payments. No further payments will be processed 

• Cancelled – This schedule has been cancelled. No further payments will be processed 

Filters 

To find a specific repeat payment schedule, you can filter the table using variables such as creation date, customer name, customer email and reference.

Specific schedule information 

You can view more information about a particular repeat payment schedule by selecting the "View details" button.
This will open a modal that displays an overview of the schedule, along with a list of all processed and scheduled payments and their respective statuses. 

The top section provides an overview of the selected schedule, including:

• Customer name 

• Customer email 

• Reference 

• Card 

• Remaining instalments 

• Frequency 

• Recurring amount 

• Created date 

• Source 

There are 3 methods of creating a repeat payment schedule.
The “source” will show which of these methods were used. 

• VT – This is when the schedule was created on “Take a payment” page via our Virtual terminal.
  If selected, it will open the “Take a payment” page with the MID already selected to the blink page that was used to create the schedule.

• API – This is when the schedule was created via Blinks API.
  If selected, it will open the blink page that was used to create the schedule 

• Repeat button - This is when the schedule was created via the “repeat” button on an existing transaction.
  If selected, it will open the blink page that was used to create the schedule 
  

Next to the schedule “Status” in the top right are 2 action buttons for the schedule. 

• Cancel – This will stop the schedule and cancel any payments that have not yet been processed.
  This does not affect payments that have already been processed.

• Edit – This allows you to update/edit the schedule data, such as the customer name, email and schedule reference.
  You can also update the stored card that is used for the payments
  Please note: All changes made here will update future payments. Any payments that have already been processed will not be updated. 

If these buttons are used, a new “schedule history” button will appear, which stores the original information.
When selected, it will display a modal detailing any changes made and the user who actioned them.  

There is also a “Confirmation email” button which contains a copy of the original email sent to the customer when the schedule was created.
It can be resent to the customer's email. 

Cancelling a schedule 

• Select the “Cancel” button in the top right corner and confirm the choice. 

• The schedule will be updated to a status of “Cancelled”, along with any of the payments that had not been processed yet.
  No payments will be processed from this schedule anymore 

• The “Schedule history” modal information will be updated with this action.  

• The customer will receive an email notifying them that the schedule has been cancelled and no additional payments will be taken.  

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

Editing a schedule 

• Select the “Edit” button in the top right corner 

• Choose the desired field to edit and enter the new value.
  Possible fields to edit are: 

  • Customer name 

  • Customer email 

  • Reference 

  • Recurring amount – This is only available for Fixed schedules. 

  • Card (see below) 

• Select “Save changes” 

• The new details will be displayed immediately, and a record of these changes will be stored in the “Schedule history” modal 

• The customer will receive an email notifying them of these changes 

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

Update/add a new card 

In some scenarios, the customers card may have been stolen or lost, or is otherwise no longer valid or available for use. 

In such cases: 

• Select the “Edit button” in the top right corner 

• Next, select the “Change” button next to the Card value 

• Now enter the new card details and confirm by clicking the “Add new card” button 

• A new Pre-Auth transaction will be processed with a reference of “Card updated”.

  • This transaction will display immediately in the Recent blink transactions page, and on the Blink card transactions page within 15mins. 

• The new details will be displayed immediately, and a record of these changes will be stored in the “Schedule history” modal 

• The customer will receive an email notifying them of this update 

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

Viewing transactions 

When “View details” is selected for a specific repeat payment schedule, a list of the payments is displayed. 

If there are more than 10 payments scheduled, it will display them on pages of 10.

This list will show both processed and future pending payments. 

• Pending payments - These will be listed here with their scheduled dates, along with an “Edit” and “Remove” button.

• Successful processed payments - These will have a “Cancel” or “Refund” button.
  (“Cancel” and “Refund” will both action a refund. They are just named differently due to the stage at which the payment is refunded)

• Declined processed payments - These will have a “Retry” button. 

• Removed/Cancelled payments - These payments cannot have any further actions performed on them

• Pending payments that did not run on their scheduled day – These will have a “Run now” button 

Possible payment statuses: 

• Pending – This payment has not yet been processed 

• Captured – This payment was processed successfully today 

• Accepted – This payment was processed successfully. The acquirer has accepted the payment and will settle the funds in due time. 

• Declined – This payment was processed but failed 

• Refunded – This payment was processed successfully and then refunded 

• Cancelled – The entire schedule was cancelled 

• Removed – This specific payment was removed 

Additional information on transactions  

The “Download CSV” button will export a file containing a list of the payments within this schedule.

This contains an overview of all the payments in this schedule and contains both the processed payments and the scheduled pending payments, with some differences in what data they may show for each. 

 To view more detailed information on the processed payments themselves, select the “View in transaction history” button.

This will redirect to the Blink card transactions page, where the page will be filtered to display all the payments that have been attempted from this schedule, including declined payments and retries.

Each payment can then be viewed in detail by expanding the line, and if desired, a CSV can be downloaded from that page.

Adding a new payment 

• Select the “Add payment” button 

• Choose a date, reference and amount for this payment 

• Select “Add payment” 

• The payment will be displayed in the list immediately 

  • If the payment date is today, it will be processed immediately. 

  • If the payment fails, the decline reason will be displayed 

• The customer will receive an email notifying them of this new payment 

  • If the date was today and the payment was successful, they will receive a receipt for the payment too

  • If the payment failed, both the customer and merchant will receive a “Payment failed” email 

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

Editing a payment 

Payments that have not yet been processed can be edited. 

• Select the “Edit” button on a specific payment 

• Choose which values to edit: “Date”, “Reference” or “Amount” 

• Select “Add payment” 

• The payment will be displayed in the list immediately 

  • If the payment date is today, it will be processed immediately. 

  • If the payment fails, the decline reason will be displayed 

• The customer will receive an email notifying them of the changes made to the schedule 

  • If the date was today and the payment was successful, they will receive a receipt for the payment too

  • If the payment failed, both the customer and merchant will receive a “Payment failed” email 

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

• An “Edited” tag will appear on this payment.
  When selected, it will display the changes made this payment 

Removing a payment 

Payments that have not yet been processed can be removed from the schedule. 

• Select the “Remove” button on a specific payment and confirm the choice 

• The payment will be updated in the list immediately to a status of “Removed” 

• The customer will receive an email notifying them that this payment was removed 

• If the schedule was created via API, a notification will be sent to the webhook URL specified in the schedule creation. 

• This action is also recorded in the “Edited” tag. 

Retrying a failed payment 

When a payment is processed but fails, it will have a “Retry” button displayed next to it. 

There will also be an icon detailing how many attempts have been made. When selected, it will give a brief overview of when the attempts were actioned. 

To retry a payment, select the “Retry” button and confirm the choice.
If the retry is successful, the payment will update to “captured” and the merchant and customer will receive a receipt. 

If the retry fails again, the reason for the decline will be displayed, and a notification email will be sent to the customer and merchant.