Caradhras Broker

Caradhras Broker (also called Broker) is a product developed to allow external authorization for credit/debit card transactions and add business rules to it, without having the specific know-how on processing card transactions. It can be used in any situations where our partners want to either authorize or not authorize card transactions based on their own business rules.

A few examples of the use of this product are:

  • External treasury to Dock;
  • Segregation of balance by Merchant Category Code (MCC).

📘

What is the Merchant Category Code?

MCC is a code listed in the ISO 18245 used to classify a business model by the type of goods or services it provides.

How does Caradhras Broker work?


Broker is responsible for transferring messages (based on ISO 8583 standard format) to API calls and providing responses to them. To work properly, we have a set of API specs that our partners must implement on their API. Click here access the technical documentation with the required API specs.

Caradhras Broker's online authorization process.Caradhras Broker's online authorization process.

Caradhras Broker's online authorization process.

The authorization process can be easily explained in a few steps:

1) When a holder uses a card, the authorization transaction (purchase or withdrawal) is sent to our card processor authorizer to validate the information;

2) The authorization system identifies that the transaction must be routed to an external authorizer;

3) The information is sent to Broker through ISO-8583 format messages;

4) We send the information to our partners who are connected to our Broker to make their authorization decision;

5) The authorization response makes the same path back to the holder;

Authorizing a Transaction


Upon receiving the authorization transaction (purchase or withdrawal) message in ISO-8583 format, the Broker decodes the information and sends the data to our partners to make the decision.

📘

International Transactions

Broker also calculates the transaction taxes for international transactions and send to our partners to make the authorization decision based on the total amount of the transaction.

This communication is made by API call in an endpoint implemented by our partners according to the API specs defined on the technical documentation. Click on the link below to see the technical documentation of the endpoint used for authorizing transactions:

POST Request Broker

❗️

Endpoint Response Time

The endpoints must have a maximum response time of 1 second, otherwise a timeout will be assumed due to the whole arranjement timeout. A timeout in the POST /transaction, for example, will return an error message to the authorization end (e-commerce, card machines, etc.), and then reversals will be sent to POST /transaction/{transactionUUID}/revert to assure that the balance will be returned to the bearer even if the transaction was already approved after the timeout.

Reversing a Transaction


Upon receiving the reversing operation message in ISO-8583 format, the Broker decodes the information, identifies the transaction that must be canceled, and send a Universally Unique Identifier (UUID) related to this transaction (transactionUUID).

This communication is made by API call in an endpoint implemented by our partners according to the API specs defined on the technical documentation. Click on the link below to see the technical documentation of the endpoint used for reversing transactions:

POST Revert Broker


Did this page help you?