Flash Payments Developer API
Back to Flash PaymentsGraphQL Playground
  • Overview
  • Basics
    • Sending data as JSON
  • Authentication
  • Quote
  • Conversions
    • Query conversions
    • Conversion statuses
  • Balance
    • Statement
  • Recipients
    • Required fields
  • Senders
  • Payments
    • Payment statuses
    • Query payments
    • Send funds
    • Auto receive funds
  • Institutions
  • Withdrawals
    • Withdraw funds
    • Withdrawal statuses
    • Query withdrawals
  • Deposits
    • Deposit statuses
    • Query deposits
    • Refund deposits
  • Sub-clients
    • Create sub-clients
    • Disable, Activate and Update sub-clients
    • Query sub-clients
  • Webhooks
    • Regular webhooks
    • Ad hoc webhooks
  • Reference data
    • Bank information
    • Rejection codes
  • Change log
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Payments

Payment statuses

PreviousPaymentsNextQuery payments

Last updated 3 months ago

Was this helpful?

The GraphQL schema defines statuses like this:

enum PaymentStatus {
  INITIALISING
  OPEN
  CLOSED
  FAILED
  CANCELLED
}

The current status of your payment.

  • INITIALISING - a draft payment. It may or may not have all required information to be executed.

    • Typically never happens via API. Can be created via the under certain circumstances.

  • OPEN - the payment is in progress.

  • CLOSED - means successfully delivered.

  • FAILED - an error has occurred with this payment.

  • CANCELLED - the payment has not completed and has been cancelled.

    • Usually done by Flash Payments operations team.

Important to understand that the Payment.history is a transfer logs and is not related to payment status at all. Sometimes the history may contain half a dozen entries, however your payment will go through only two steps: OPEN and CLOSED.

Flash Payments app