Everest Card — API reference
  • Credit
  • Debit
  • Prepaid
  • Common Methods
  • OAuth2
  • Delivery
Information
Cards
    Card lifecycle
      getBasicCardInformationByPanpostgetDebitCardLogDataListByShadowCardNumberpostgetCreditCardLogDataListByShadowCardNumberpostgetCardByCardNumberpostgetSecureCardByPanpostgetCardByShadowCardNumberpost
Customers and accounts
    Customers
      getAssetByShadowCardNumberpostgetCustomerDetailpostcreateCustomerpostupdateCustomerpost
    Account linking
      accountStatuspost
Transactions
    getCreditTransactionListpostgetPaymentAndCashadvanceInformationByCriteriaspostgetAuthorizationListByBegindateEnddatepostgetDbttransactionByCardrefCustomernumpost
Limits and controls
    Card and customer limits
      changeCustomerLimitDecreasepostchangeCustomerLimitIncreasepost
    Permissions and restrictions
      getCardRestrictionpost
Billing and statements
    Collections and legal follow-up
      createFollowUpByMainCustomerNumberpostaddToLegalFollowUppost
    Debt payment
      getAutoPaymentQueuepost
    Statements and billing
      getDelinquencyInterestAmountpostsetStatementDocumentIdpostsetStatementDocumentOnlypostgetCardStatementCutoffReportpost
Security
    PIN and card security
      isSetCardPinViaSMSControlpostgetClearPanByShadowpostgetCardInfoByClearPanpostgetEncryptDataBlockpostdecryptDataBlockpost
Rewards
    Campaigns and rewards
      executeCampaignTransactionpostgetDebitCardForRewardByBankpost
Platform
    Platform operations
      healthCheckpostrefreshCachepost
    Reference data
      getProductByShadowCardNumberpostgetEmbossReasonSubDefByValidFlagpostgetAvailableEmbossReasonListpostgetMccGroupAllpostgetTrnStatusAllpostgetBinDomesticByBinpostgetApplicableProductspostgetMccDefinitionGroupbyMccMccdescriptionpostgetNetworkTypeDefByValidFlagpostgetResponseCodeDefByValidFlagpostgetResponseReasonCodeDefByValidFlagpostgetTrnCodeDefByValidFlagpostgetTrnCodeMatrixByValidFlagpost
SchemasError codesChannels
powered by Zudoku
Common Methods
Common Methods

Debt payment

Take a payment against card debt, check a card is eligible to be paid down, and cancel a payment that should not have run.


getAutoPaymentQueue

POST
https://sandboxpub.cms.dgpays.com/SandBox
/Integrationcorebanking/Indoor/api/getAutoPaymentQueue

Retrieves a list of scheduled auto payments for credit card customers within a specified date range and pagination limits. The method accepts GetAutoPaymentQueueRequest containing GetAutoPaymentQueueParam with StartRowNo, EndRowNo, and DueDate. The response returns GetAutoPaymentQueueResponse with a list of GetAutoPaymentQueueResult items, including CustomerNumber, MainCardRefNumber, ShadowCardNumber, MaskedCardNumber, PaymentAccount details, DailyPaymentAmount, PaymentTotalCurrent, RemainingAmount, Statement details, PaymentType, and RemainingMinimumPaymentAmount (calculated from the latest statement).

getAutoPaymentQueue › Headers

evrst-ptrnid
​string

Correlation id for this request. Echo it in your own logs to trace the call through the platform.

Default: x_request_id

getAutoPaymentQueue › Request Body

GetAutoPaymentQueueRequest
​object · required

The due date and the row window. The operation dereferences this without a null check, so it must be sent.

getAutoPaymentQueue › Responses

Success.

This operation never leaves the facade: it runs a repository view and converts the rows. Nothing is validated. A due date with no auto-payment instructions is a success with an empty result.

The queue holds only cards whose auto-payment instruction is valid and whose remaining amount is still above zero, so a card that has already paid drops out of the queue rather than appearing with a zero amount. remainingAmount is computed by the view from the statement minimum where the instruction pays the minimum and from the statement total otherwise, less what has already been paid.

Paging is applied over an ordering by customer number ascending, and the row numbers are recomputed on every call, so a queue that changes between calls can skip or repeat rows across pages.

remainingMinimumPaymentAmount is not part of the queue view. The facade fills it with a second query per row, and takes the first row of that query, which is ordered by statement date ascending — so the figure comes from the card's earliest statement in that currency, not from the statement the queue row is for. If that query returns nothing for a card, the whole call fails rather than that one row.

GetAutoPaymentQueueResponse
​array · optional
POST/Integrationcorebanking/Indoor/api/getAutoPaymentQueue
curl https://sandboxpub.cms.dgpays.com/SandBox/Integrationcorebanking/Indoor/api/getAutoPaymentQueue \ --request POST \ --header 'Content-Type: application/json' \ --header 'evrst-ptrnid: x_request_id' \ --header 'Authorization: Bearer <access_token>' \ --data '{ "getAutoPaymentQueueParam": { "dueDate": "2026-10-16T14:30:00Z", "endRowNo": 0, "startRowNo": 0 } }'
Example Request Body
{ "getAutoPaymentQueueParam": { "dueDate": "2026-10-16T14:30:00Z", "endRowNo": 0, "startRowNo": 0 } }
json
application/json
Example Responses
{ "getAutoPaymentQueueResult": [ { "customerNumber": 0, "dailyPaymentAmount": 0, "dueDate": "2026-10-16T14:30:00Z", "dueOptionDate": "2026-10-16T14:30:00Z", "mainCardRefNumber": "mainCardRefNumber", "maskedCardNumber": "maskedCardNumber", "paymentAccountBranchCode": 0, "paymentAccountNumber": 0, "paymentAccountOwnerName": "paymentAccountOwnerName", "paymentAccountSuffix": 0, "paymentTotalCurrent": 0, "paymentType": "paymentType", "remainingMinimumPaymentAmount": 0, "remainingAmount": 0, "shadowCardNumber": "shadowCardNumber", "statementCurrencyCode": "statementCurrencyCode", "statementDate": "2026-10-16T14:30:00Z", "statementMinAmount": 0, "statementTotalAmount": 0 } ] }
json
application/json

Collections and legal follow-upStatements and billing