📢We've added the ability to sync a program via the API🛠

You can now start the Location sync process programmatically by calling the Update Program endpoint of our API.

You'll need to add a body parameter of { "status" : "syncing" } to start the process. Because syncing only works for live programs, you'll need to use the programId of a live program, and your live API key, when you call the API endpoint.|

curl -X PATCH https://api.fidel.uk/v1/programs/1ed2d0a4-b778-4ea4-b991-b5ede2d4eeaa \
  -H 'content-type: application/json' \
  -H 'fidel-key: sk_live_b2e6a6ab-1a11-47ec-831c-81c2b23fd5b2' \
  -d '{
    "status": "syncing"
  }'

🧪We've added demo data to new test accounts👤

Creating your first test Transaction in the Fidel Dashboard just became easier. All new Fidel accounts now come with all the test data setup you need to create a transaction:

  • A "Demo Program"
  • A "Simple Coffee" Brand
  • 3 UK Locations
  • 1 Visa Card registered
  • 1 Auth Transaction

The "Demo Program" also comes with the new Program properties we added:

  • icon - Emoji to associate with the Program. Uses the :emoji-name: format. Accepts between 4 and 200 characters. The demo data is :wave: 👋.
  • iconBackground - Background color for the program icon. Accepts a HEX CSS string, like #333333. The demo data is #fedcd7.

📢 We’ve added a new webhook event, for location sync statuses 🛍

A location.status event is triggered when there are updates from a card network for a Location in a Program.

In the test environment, this webhook triggers three times for each location upon creating a Location, once for each card scheme, with a location.active event.

In the live environment, this would trigger whenever a location has synced successfully for a card scheme, with a location.active event. Or whenever a location has failed to sync for a card scheme, with a location.failed event.

You can use the Fidel Dashboard or the Webhooks API to register your webhook URL with the new location.status event.

curl -X POST \
  https://api.fidel.uk/v1/programs/06471dbe-a3c7-429e-8a18-16dc97e5cf35/hooks \
  -H 'content-type: application/json' \
  -H 'fidel-key: sk_test_50ea90b6-2a3b-4a56-814d-1bc592ba4d63' \
  -d '{
    "event": "location.status",
    "url": "https://example.com/location-webhook"
  }'

Screenshot 2020-08-18 at 15.27.59.png

To read more about the new location.status webhook event, visit our documentation!

🔗Added endpoints for retrieving and checking cards exist on offers with activation🗂

We've added two new endpoints to our Offers API for retrieving and checking cards exist on offers with activation:

  • /v1/offers/{offerId}/cards/ - Get a list of cards associated with an offer with activation. You can read more about it in the API Reference.
curl -X GET \
  https://api.fidel.uk/v1/offers/0b31ee54-1def-4b46-afca-151f2ed1bce2/cards \
  -H 'Content-Type: application/json' \
  -H 'Fidel-Key: sk_test_50ea90b6-2a3b-4a56-814d-1bc592ba4d63'
  • /v1/offers/{offerId}/cards/{cardId} - Check if a specific card is associated with an offer with activation. You can read more about it in the API Reference.
curl -X GET \
  https://api.fidel.uk/v1/offers/0b31ee54-1def-4b46-afca-151f2ed1bce2/cards/aef3e34e-725f-470a-899a-740ebe4aae5e \
  -H 'content-type: application/json' \
  -H 'fidel-key: sk_test_50ea90b6-2a3b-4a56-814d-1bc592ba4d63'

📱We've updated our Mobile SDKs to support l10n & i18n 🗺

Our Android, iOS and React Native SDKs all got updated to support:

  • localization for French and Swedish.
  • Terms and Conditions update according to the card scheme name (Visa, MasterCard, or Amex).
  • options for programName and termsConditionsUrl. They are mandatory when country is USA or Canada.
  • internationalized Terms and Conditions for the USA, Canada, and the rest of the world.

USA & Canada New T&C: By submitting your card information and checking this box, you authorize {cardScheme} to monitor and share transaction data with Fidel (our service provider) to participate in the {programName} programme. You also acknowledge and agree that Fidel may share certain details of your qualifying transactions with {companyName} to enable your participation in the {programName} programme and for other purposes in accordance with the {companyName} Terms and Conditions, {companyName} privacy policy and Fidel’s Privacy Policy. You may opt-out of transaction monitoring on the linked card at any time by contacting support.

Rest of the World T&C: I authorise {cardScheme} to monitor my payment card to identify transactions that qualify for a reward and for {cardScheme} to share such information with {companyName}, to enable my card-linked offers and target offers that may be of interest to me. For information about {companyName} privacy practices, please see the privacy policy. You may opt-out of transaction monitoring on the payment card you entered at any time by contacting support.

📢 We’ve added a new webhook event, for refunded transactions 💸

A transaction.refund or refund transaction event is triggered when a transaction is refunded. A refunded transaction also triggers a cleared event, with the auth property set to false. The amount on both events is negative.

The Fidel API tries to identify the initial transaction for which the refund was issued, using cardId, locationId, merchantId, amount and datetime. If we can identify an associated initial transaction, the webhook data contains the originalTransactionId. If we can’t identify the initial transaction, the data comes in on both webhooks with a negative amount but no originalTransactionId property.

You can use the Fidel Dashboard or the Webhooks API to register your webhook URL with the new transaction.refund event.

curl -X POST \
  https://api.fidel.uk/v1/programs/06471dbe-a3c7-429e-8a18-16dc97e5cf35/hooks \
  -H 'content-type: application/json' \
  -H 'fidel-key: sk_test_50ea90b6-2a3b-4a56-814d-1bc592ba4d63' \
  -d '{
    "event": "transaction.refund",
    "url": "https://example.com/refund-webhook"
  }'

Screenshot 2020-07-13 at 12.01.19.png

To read more about the new transaction.refund webhook event, visit our documentation!

Transactions in test environment can now be cleared

When completing a credit card transaction, there are two steps: authorisation and clearing.

  1. Authorisation is the step at purchase where the bank confirms that the purchase can be made.

  2. Clearing is the step 24-72 hours later where the money is actually debited and transferred to the merchant's account.

In the Fidel test environment, all transactions are automatically authorised, and appear in the transactions table of the dashboard. You can now manually "clear" the transaction, to mimic the process where the bank completes the transaction:

Screenshot 2020-06-16 at 15.38.24.png

Once you confirm the transaction clearing, it will appears as cleared:

Screenshot 2020-06-16 at 15.39.44.png

And the transaction.clearing webhook will fire, allowing you to test transaction clearing before going to production.

Refund Transaction Matching

Fidel now offers refund transaction matching. If a transaction refund is made at the same location for the same amount as the original transaction, Fidel will match the two transactions.

The original transaction will gain a new field refundTransactionId that points to the refund transaction.

The refund transaction will point to the original transaction with the originalTransactionId field.

Read more here: https://fidel.uk/docs/transactions/#refund-transactions

Custom Headers in Webhooks

You can now add custom headers to your Fidel Webhooks.

You'll see it as a new UI option on our dashboard:

Screenshot 2020-06-08 at 10.36.42.png

We describe the header use in our docs: https://fidel.uk/docs/webhooks

Read how to implement in our API as well! https://reference.fidel.uk/reference#create-webhook-brand

Merchant location onboarding improvement

When you add a location to your card linking program, Fidel must perform a "Location Sync" that validates the location with the card networks before transactions can be accepted. In the past, this process has taken 7-10 business days.

We have completely refactored the merchant location onboarding process. Since this refactor, we are seeing greatly reduced location onboarding times. You can now expect your location onboarding with the card network to take 3-4 business days.