Fixed
Elavon, Stripe, and Bank of America payment metadata
12 months ago
Elavon Converge capture records show ASPNRXID again after the reference stopped appearing on captured payments in mid-July. Stripe credit card charges now carry the same reconciliation metadata as token charges, and Bank of America payment mappings stay aligned for capture and metadata fields processors expect.
- Elavon Converge captured payments include ASPNRXID again. The value was present at authorization but missing after capture, which made it hard to match records in Converge; capture now carries it through.
- Stripe credit card charges include reference, transaction ID, conversation ID, and customer ID in payment metadata, matching token charges. You can tie Stripe activity back to Authvia transactions during reconciliation without custom tagging.
- Card-on-file charges send Permission as Use with CardOnFile when a saved card is used, so repeat charges are less likely to fail or misreport how the card was stored.