Skip to main content

Required data

  • Only applies for Android SDK

There is data that must be provided when the transaction is confirmed, this is the required information to perform the transaction, Geopagos will explain it and most of this information vary from one market to another.

If you are an aggregator you need implement the aggregator flow in order to obtain the required information to populate the confirm a transaction. For more information see implementation flow.

  • Application key: Is The merchant key identifier.

  • AuthToken: Geopagos team will provide credentials for generate the auth token, this credentials must be stored in the backend in a secure way, it should not be stored on the client application.

  • TimeZone: is the time zone where the transaction is being made.

  • Establishment: represents the ultimate recipient of funds and optionally its parent Aggregator under intermediary when using Aggregator schemes.

    • businessCategoryCode: A business category code, depends on local legislation and represents broad business categories such as hairdresser or supermarket.
    • legalName: The merchant legal operating name.
    • tradeName: The merchant common name as it might appear printed in the Credit Card Statement. Usually the same as it’s might be written on a store front.
    • docType: depends on local legislation. For example, in Argentina it’s “CUIL”, “CUIT” or “DNI”
    • docNumber: The document number as expected by the payment processor.
    • intermediary: Represents the intermediary establishment
    • Address: establishment address:
      • addressLine1: should contain the primary address information.
      • addressLine2: is for additional information such as an apartment, suite or space number.
      • city: address city.
      • countryCode: code according to ISO 3166-1.
      • postalCode: code according to country specification.
      • state: address state.

  • AdditionalCardData: complementary card data:

    • brand: The card brand, one of “VISA”, “MASTER”, “MAESTRO” (this data can be obtained based on the bin of the read card).

    • cardType: The card type, credit or debit.

    • cvv: Card Verification Value. This is optional according the market, will be explained by geopagos upon the integration.

    • Merchant: this field represents the merchant to the payment processor:

      • merchantId: An id assigned to the merchant by the payment processor. Usually numeric.
      • name: This is the name as it will appear at the Credit Card Statement, this is usually assigned by the PaymentProcessor.

    • TerminalId: A terminal id is a logical identifier provided by the payment processor. Depending on the payment processor it could be either a numeric or alphanumeric.

    • TicketNumber: is a numeric sequential value between 0001-9999 generated by the PoS Device. it must be incremented after every successful transaction.