What is a common use case for the update API?
- A common use case for the update API is updating the Product Key (e.g moving from a 6-month promotion to fully paid).
What happens if I send a second Create Entitlement request, with the same parameters/values as the first, with the entitlement in an PENDING status.
- Bango will respond with a new activationUrl which the customer will be redirected to for sign-up
How many entitlements can a customer have per merchant?
- By default, Bango only allow one entitlement per customer per merchant. If the merchant allows, Bango can increase this.
If the resellers requests Create Entitlement a second time and the entitlement is in an ACTIVE status, Bango will respond BAD_REQUEST. How can I tell the difference between the BAD_REQUEST response in this scenario and other BAD_REQUEST responses.
- If the entitlement is in an ACTIVE status, Bango will respond "Invalid request or the request contains invalid data. Maximum number of subscriptions for user reached" in the 'responseMessage' parameter. If the request to Bango is not correct, Bango will return "
parameter is required" or "
parameter is invalid" in the 'responseMessage'.
Will I be notified if a customer has already signed-up direct with the merchant and can't sign-up with the reseller offer.
- In some cases, the merchant can notify Bango the customer is not eligible to sign-up via the reseller offer, due to already subscribing to the merchant directly. Bango can pass this notificaiton to the reseller using the Notification URL provided in the Create Entitlement request.
Does Bango require Client Certificates?
- No, Bango Resale API does not require Client Certificates. You can view the full security reccomendations here.
Do I have to use echoAPI?
- No, the Echo API is an optional API method which the reseller can use to complete basic connectivty tests to the Bango platform.
Can Bango provide customer experience flows for the merchant?
- Normally the merchant owns the customer experience flows and is responsbile for signing off any reseller customer experience related to the merchant brand.
What is the difference between the Cancellation API and the Revocation API?
- The Cancellation API will request the merchant to 'Cancel at End of Billing Cycle', this is normally at the end of the month. The Revocation API will request the merchant to 'Cancel Immediately', remove the service from the customer with immediate affect. The method use can depend on product or scenario. The technical consultant assigned to the project can help understand the required API method(s)
What is a difference between the customerIdentifier and entitlementId?
- The customer identifier is the identity of the customer, this could be MSISDN, email address, GUID. The Entitlement ID is provided by bango. Entitlement Id is a customer + product + data life cycle combination.
What happens if the activationUrl is expired before the customer is redirect to it?
- The customer will receive an error message on the merchant page. The customer will need to start the activation flow from the beginning.
If a customer cancels their subscription directly with the merchant to move over to reseller billing, will the customer be refunded?
- This logic depends on the merchant, by country. Bango can support the reseller in speaking to the merchant to confirm the direct cancellation logic.
Can the notificationUrl be used for notifications of all API's?
- Yes, Bango will use the notificationUrl provided in the create entitlement call for all future notifications for that entitlement. Example is the confirmation of cancellation, will be sent to the same notificationUrl as activation notification, however the 'Status' parameter will be different.
Should I use the notificationUrl, and what are the common scenarios for using the notificationUrl?
- Yes, the common use cases are listed below:
1. Confirming customer has signed-up and is activated
2. Confirming the customers subscription has been cancelled by the merchant
3. Notifying the merchant has cancelled the subscription