Preliminary Note
The Dashboard is an online interface that allows the creditor (merchant) to see and monitor the mandates and transactions that he does with SlimPay.
The Dashboard can be accessed on two different platforms:
- Test platform: https://dashboard.preprod.slimpay.com
- Production platform: https://dashboard.slimpay.com
Please click on the appropriate link, fill your email address and click on “reset password” to receive by email the process to create your password.
Administrator credentials are provided by SlimPay’s Customer Success team. The Administrator can invite his team and assign them predefined roles through the “Team” page.
Status Definition
Different status are displayed in the Dashboard. It allows you to have an updated view of each item and to filter by status.
Orders section
The order section gathers all API calls related to the any action through the Checkout (electronic signature, SDD creation, card payment...).
Status displayed in this section:
STATUS |
DEFINITION |
Running |
An order is in a “running” mode when it is open and in progress |
Aborted by client |
After being “running”, an order becomes “Aborted by client” when the customer gave up the Checkout process before the end |
Aborted by server |
After being “running”, an order becomes “Aborted by server” when an error occurred (blocked payment, processing error) or when the order expired (“Running” during 60+ days) |
Completed |
An order is in a “completed” mode when the customer went to the end of the process and it ended with success |
Authorizations section
The authorization section gathers mandates for SDD payments and card alias for Card payments.
Here are the statuses displayed in this section:
STATUS |
DEFINITION |
Waiting for UMR (for SDD) | A mandate is created without the UMR (Unique Mandate Reference) which is added later on |
Active (for SDD) | A mandate is “active” when it is signed with success |
Revoked (for SDD) | A mandate is “revoked” when:
|
Expired (for SDD) | A mandate expires when not one single payment has been made over a period of 36 months (as of the last SDD). It stops any future payment |
Deleted (for Card payment) | A card alias is deactivated by the creditor (merchant) or SlimPay (card expiration as the most common reason) |
Activated (for Card payment) | Once the card alias is created |
Payments section
The payments section gathers all types of payments: SDD, card payments and Refunds (Reimbursements)
STATUS |
DEFINITION |
To process |
A payment is in “to process” mode when it has been accepted and will be send to the bank. A “to process” payment can be cancelled by the creditor (merchant) via API / Dashboard before execution. For example in the case of a payment plan, upcoming transactions are in “to process” status. |
Processing |
A payment is in “processing” mode when it has been sent to the bank but the payment is subject to confirmation by the bank. |
Processed |
A payment is in “processed” mode when it has been sent to the bank and the bank has accepted the treatment of the payment. It does not mean that the money has already arrived in the creditor (merchant) account. Theoretically if everything goes well, the money arrives at D+1 and the status remains “processed”. In case of an R-transaction (> Rejected) the status can change between J and J+5 for technical reasons (not enough funds, account blocked etc.) and between J and J+13 months in case of opposition by the account holder (consumer's rights). After 13 months the status is final. |
Not processed |
The payment has been cancelled by the creditor (merchant) before having collecting the funds |
Rejected |
The payment is returned as “rejected” by the bank. The payment has been sent to the bank and came back with an error code |
Plans section
The plans section gathers all payments plans (SDD and Card plans)
STATUS |
DEFINITION |
Active |
A plan is “active” when there is at least one payment to come |
Inactive |
A plan is “inactive” when all payment dates have been executed and the plan is finished |